Scaled-Tech-Consulting/Gitea-Tools
2
0
Fork 0
Code Issues 17 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

Refactor and expand portable LLM workflow templates #47

Closed
jcwalker3 wants to merge 0 commits from docs/issue-46-portable-llm-workflow-skill into master
pull from: docs/issue-46-portable-llm-workflow-skill
merge into: Scaled-Tech-Consulting:master
Conversation 2 Commits - Files Changed -
jcwalker3 commented 2026-07-02 02:26:51 -05:00
Owner
Copy Link
Copy Source

Closes #46.

Base work from #42/#45 already exists on master. This PR improves that skill; it does not create it from scratch.

Files changed

  • skills/llm-project-workflow/SKILL.md
  • skills/llm-project-workflow/templates/start-issue.md
  • skills/llm-project-workflow/templates/review-pr.md
  • skills/llm-project-workflow/templates/merge-pr.md
  • skills/llm-project-workflow/templates/recover-bad-state.md (New)
  • skills/llm-project-workflow/templates/worktree-cleanup.md (New)
  • skills/llm-project-workflow/templates/recover-dirty-worktree.md (Deleted)
  • README.md
  • docs/llm-workflow-runbooks.md

Why deleting recover-dirty-worktree.md is intentional

The old recover-dirty-worktree.md template was too generic. It has been replaced by two specialized templates:

  1. worktree-cleanup.md: A strict, safe workflow for cleaning up branch worktrees after a merge is successfully confirmed.
  2. recover-bad-state.md: Focused strictly on recovering from ambiguous git states.

Safety

This is a docs-only / skill-only change. No runtime behavior changed. No secrets are included.

Closes #46. Base work from #42/#45 already exists on `master`. This PR improves that skill; it does not create it from scratch. ### Files changed - `skills/llm-project-workflow/SKILL.md` - `skills/llm-project-workflow/templates/start-issue.md` - `skills/llm-project-workflow/templates/review-pr.md` - `skills/llm-project-workflow/templates/merge-pr.md` - `skills/llm-project-workflow/templates/recover-bad-state.md` (New) - `skills/llm-project-workflow/templates/worktree-cleanup.md` (New) - `skills/llm-project-workflow/templates/recover-dirty-worktree.md` (Deleted) - `README.md` - `docs/llm-workflow-runbooks.md` ### Why deleting recover-dirty-worktree.md is intentional The old `recover-dirty-worktree.md` template was too generic. It has been replaced by two specialized templates: 1. `worktree-cleanup.md`: A strict, safe workflow for cleaning up branch worktrees after a merge is successfully confirmed. 2. `recover-bad-state.md`: Focused strictly on recovering from ambiguous git states. ### Safety This is a docs-only / skill-only change. No runtime behavior changed. No secrets are included.
sysadmin changed title from docs: portable llm-project-workflow skill + templates (#46) to Refactor and expand portable LLM workflow templates 2026-07-02 02:36:22 -05:00
jcwalker3 added 1 commit 2026-07-02 03:07:16 -05:00
docs: add portable llm-project-workflow skill + templates (#46) 00ec883014 
Extract the project's operating rules into a reusable, project-agnostic skill
so any repo can adopt the same safe LLM workflow.

- skills/llm-project-workflow/SKILL.md: issue-first; isolated branch worktrees
  (main checkout = orchestration only); distinct author/reviewer identities and
  profile safety (secrets by reference only; stop if authenticated user == PR
  author); branch naming; start/review/merge/cleanup workflows; fail-closed
  cases; recovery patterns; and an "Adapting to a project" table for the
  forge-specific names.
- templates/: copy/paste prompts for start-issue, review-pr, merge-pr,
  recover-bad-state, worktree-cleanup.
- Link the skill from README.md and docs/llm-workflow-runbooks.md (the runbook
  is framed as the Gitea-specific application of the portable skill).

Docs-only; no code, no secrets, safe placeholder examples only. No change to
MCP runtime, Gitea API, credential storage, or worktree helpers.

Checks: full suite 287 passed / 0 failures; git diff --check clean; secret scan
of skills/ clean.

Closes #46. Refs #38, #39.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
jcwalker3 force-pushed docs/issue-46-portable-llm-workflow-skill from d1d2bc2505 to 00ec883014 2026-07-02 03:07:16 -05:00 Compare
jcwalker3 closed this pull request 2026-07-02 03:07:26 -05:00
jcwalker3 deleted branch docs/issue-46-portable-llm-workflow-skill 2026-07-02 03:07:26 -05:00
sysadmin commented 2026-07-02 03:10:54 -05:00
Owner
Copy Link
Copy Source

Blocked: PR #47 is no longer open, so I cannot merge it through the requested reviewer/merger workflow. Gitea currently reports , , , and no . I also observed issue #46 is closed but still has . Remote has advanced to with a #46-related commit, but because PR #47 itself is closed-not-merged in Gitea, I am stopping without merge or cleanup.

Blocked: PR #47 is no longer open, so I cannot merge it through the requested reviewer/merger workflow. Gitea currently reports , , , and no . I also observed issue #46 is closed but still has . Remote has advanced to with a #46-related commit, but because PR #47 itself is closed-not-merged in Gitea, I am stopping without merge or cleanup.
sysadmin commented 2026-07-02 03:11:20 -05:00
Owner
Copy Link
Copy Source

Correction to my prior blocker comment: PR #47 is no longer open, so I cannot merge it through the requested reviewer/merger workflow. Gitea currently reports state=closed, merged=false, merged_at=None, and no merge_commit_sha. Issue #46 is closed but still has the status:in-progress label. Remote prgs/master has advanced to commit 00ec883 with a #46-related commit, but because PR #47 itself is closed-not-merged in Gitea, I am stopping without merge or cleanup.

Correction to my prior blocker comment: PR #47 is no longer open, so I cannot merge it through the requested reviewer/merger workflow. Gitea currently reports state=closed, merged=false, merged_at=None, and no merge_commit_sha. Issue #46 is closed but still has the status:in-progress label. Remote prgs/master has advanced to commit 00ec883 with a #46-related commit, but because PR #47 itself is closed-not-merged in Gitea, I am stopping without merge or cleanup.

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
architecture
Architecture / structural design
 bug
chore
design
Design / investigation, no implementation
 documentation
Docs / runbooks
 gitea
Gitea MCP workflow
 glitchtip
GlitchTip integration
 important
integration
Integration testing
 jenkins
Jenkins integration
 labels
Label taxonomy management
 mcp
MCP server / tooling
 mutating
Mutating action; requires gating
 nice-to-have
portability
Cross-platform / portability
 read-only
Read-only, no mutation
 refactor
Code refactor / restructure
 release
Release / versioning
 reliability
Reliability / failure handling
 roadmap
Roadmap / umbrella issue
 security
Security / trust boundary
 status:in-progress
Issue is being worked on
 testing
Tests / test coverage
 tracker
Issue tracker hygiene / meta
 workflow
Cross-tool workflow
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
jcwalker3 sysadmin
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Scaled-Tech-Consulting/Gitea-Tools#47
Delete Branch "docs/issue-46-portable-llm-workflow-skill"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?