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

Refactor and expand portable LLM workflow skill templates #46

New Issue
Closed
opened 2026-07-02 02:21:15 -05:00 by jcwalker3 · 3 comments
jcwalker3 commented 2026-07-02 02:21:15 -05:00
Owner
Copy Link
Copy Source

This is not a duplicate of #42/#45.
#42/#45 created the initial portable workflow skill.
#46/#47 refines and expands it.
The improvement includes:

  • stricter copy-paste prompt templates
  • clearer Task: directives
  • explicit hard gates/rules
  • required Handoff: sections
  • replacing recover-dirty-worktree.md with:
    • recover-bad-state.md
    • worktree-cleanup.md
  • expanded "Adapting to a project" guidance in SKILL.md
This is not a duplicate of #42/#45. #42/#45 created the initial portable workflow skill. #46/#47 refines and expands it. The improvement includes: * stricter copy-paste prompt templates * clearer `Task:` directives * explicit hard gates/rules * required `Handoff:` sections * replacing `recover-dirty-worktree.md` with: * `recover-bad-state.md` * `worktree-cleanup.md` * expanded "Adapting to a project" guidance in `SKILL.md`
jcwalker3 added the status:in-progress label 2026-07-02 02:21:24 -05:00
sysadmin changed title from Create portable LLM project workflow skill to Refactor and expand portable LLM workflow skill templates 2026-07-02 02:36:22 -05:00
sysadmin reopened this issue 2026-07-02 03:28:44 -05:00
sysadmin removed the status:in-progress label 2026-07-02 03:28:45 -05:00
sysadmin commented 2026-07-02 03:28:45 -05:00
Owner
Copy Link
Copy Source

Reconciliation result: PR #47 is closed-not-merged in Gitea metadata, and current master is not fully equivalent to the intended PR #47 final tree. Master contains the new recover-bad-state.md and worktree-cleanup.md templates, but recover-dirty-worktree.md is still present even though PR #47 intended to delete it. I reopened this issue and removed the stale status:in-progress label. No branches or worktrees were deleted. A corrective follow-up should handle the missing deletion or decide to keep the old template explicitly.

Reconciliation result: PR #47 is closed-not-merged in Gitea metadata, and current master is not fully equivalent to the intended PR #47 final tree. Master contains the new recover-bad-state.md and worktree-cleanup.md templates, but recover-dirty-worktree.md is still present even though PR #47 intended to delete it. I reopened this issue and removed the stale status:in-progress label. No branches or worktrees were deleted. A corrective follow-up should handle the missing deletion or decide to keep the old template explicitly.
jcwalker3 added the status:in-progress label 2026-07-02 03:32:29 -05:00
jcwalker3 commented 2026-07-02 03:32:32 -05:00
Author
Owner
Copy Link
Copy Source

Claimed corrective cleanup. Removing superseded recover-dirty-worktree template that was left behind by the closed-not-merged PR #47 partial landing.

Claimed corrective cleanup. Removing superseded recover-dirty-worktree template that was left behind by the closed-not-merged PR #47 partial landing.
jcwalker3 commented 2026-07-02 04:38:09 -05:00
Author
Owner
Copy Link
Copy Source

Claimed. status:in-progress

Claimed. status:in-progress
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
chore
documentation
Docs / runbooks
 gitea
Gitea MCP workflow
 important
mcp
MCP server / tooling
 mutating
Mutating action; requires gating
 nice-to-have
read-only
Read-only, no mutation
 roadmap
Roadmap / umbrella issue
 security
Security / trust boundary
 status:in-progress
Issue is being worked on
No Label status:in-progress
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#46
Delete Branch "%!s()"

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?