Create portable LLM project workflow skill #42

Closed
opened 2026-07-02 02:01:34 -05:00 by jcwalker3 · 2 comments
Owner

Problem

The Gitea-Tools workflow now includes important operating rules:

  • no repo changes without an issue
  • isolated branch worktrees for every issue
  • no self-review or self-merge
  • canonical Gitea profiles for author/reviewer identities
  • branch/worktree cleanup after PR merge/close
  • fail-closed behavior when identity/worktree/PR state is unsafe

These rules should not live only in one project's runbook. We need a portable skill that can be copied into other projects so every LLM follows the same workflow.

Scope

Create a reusable skill package/document that teaches an LLM how to operate on any project safely using this workflow.

Acceptance criteria

  • A reusable skill exists under skills/llm-project-workflow/.
  • The skill can be copied to another project and still makes sense.
  • It documents issue-first, worktree isolation, no-self-review, profile safety, merge cleanup, and fail-closed behavior.
  • README/runbook link to the skill.
  • No secrets or private config values are included.
  • Full checks pass.

Out of scope

  • Runtime behavior changes.
  • Credential or token changes.
  • Jenkins, Ops, GlitchTip, Release, deploy, rollback, migration, restart, CI trigger, or production behavior.
## Problem The Gitea-Tools workflow now includes important operating rules: - no repo changes without an issue - isolated branch worktrees for every issue - no self-review or self-merge - canonical Gitea profiles for author/reviewer identities - branch/worktree cleanup after PR merge/close - fail-closed behavior when identity/worktree/PR state is unsafe These rules should not live only in one project's runbook. We need a portable skill that can be copied into other projects so every LLM follows the same workflow. ## Scope Create a reusable skill package/document that teaches an LLM how to operate on any project safely using this workflow. ## Acceptance criteria - A reusable skill exists under `skills/llm-project-workflow/`. - The skill can be copied to another project and still makes sense. - It documents issue-first, worktree isolation, no-self-review, profile safety, merge cleanup, and fail-closed behavior. - README/runbook link to the skill. - No secrets or private config values are included. - Full checks pass. ## Out of scope - Runtime behavior changes. - Credential or token changes. - Jenkins, Ops, GlitchTip, Release, deploy, rollback, migration, restart, CI trigger, or production behavior.
jcwalker3 added the status:in-progress label 2026-07-02 02:01:50 -05:00
Author
Owner

Starting implementation.

Planned branch: docs/issue-42-portable-llm-workflow-skill

Scope: add a portable LLM project workflow skill under skills/llm-project-workflow/ and link it from README/runbook docs. No runtime behavior changes.

Starting implementation. Planned branch: `docs/issue-42-portable-llm-workflow-skill` Scope: add a portable LLM project workflow skill under `skills/llm-project-workflow/` and link it from README/runbook docs. No runtime behavior changes.
Author
Owner

Implementation PR opened: #45

Validation performed:

  • git diff --check
  • git diff --cached --check
  • /Users/jasonwalker/Development/Gitea-Tools/venv/bin/python -m pytest tests/ -q (287 passed)

Docs/skill-only change; no runtime or credential behavior changed. Awaiting eligible reviewer/merger.

Implementation PR opened: https://gitea.prgs.cc/Scaled-Tech-Consulting/Gitea-Tools/pulls/45 Validation performed: - `git diff --check` - `git diff --cached --check` - `/Users/jasonwalker/Development/Gitea-Tools/venv/bin/python -m pytest tests/ -q` (`287 passed`) Docs/skill-only change; no runtime or credential behavior changed. Awaiting eligible reviewer/merger.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Scaled-Tech-Consulting/Gitea-Tools#42