implement-worktree
Implements an approved Markdown plan inside the current script-created git worktree, verifies the result, commits the implementation, and writes a handoff summary for audit.
- License 许可
- MIT
- 最近更新
- 2026-09-24
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- implement-worktree
- description
- Implements an approved Markdown plan inside the current script-created git worktree, verifies the result, commits the implementation, and writes a handoff summary for audit.
03 SKILL.md 正文
Implement Worktree
Use this skill inside a feature worktree that has already been created by the workflow script. The script owns branch creation, worktree creation, merge, and cleanup. This skill owns implementation behavior inside the current worktree.
Required Input
- Path to the approved plan file.
- Current shell location must be the feature worktree, not the primary
maincheckout.
If the plan path is missing or the current checkout is main, stop before editing and report the problem.
Safety Rules
- Do not create, switch, merge, delete, rebase, or clean up worktrees.
- Do not edit the primary/main checkout.
- Do not push.
- Do not read, write, or diff
scratchpad.md. - Preserve user changes you did not make.
- Keep edits scoped to the approved plan.
Workflow
- Confirm the current branch and worktree:
git worktree list
git branch --show-current
git status --short
Stop before editing if the current branch is main or if the current path is the primary main checkout.
-
Read the plan completely. Restate the implementation scope, non-goals, assumptions, and expected verification.
-
Implement the plan in the current worktree only. Follow this repository's
AGENTS.mdand any relevant skills. -
Run focused tests or checks appropriate to the changed files. If a relevant check cannot be run, record the reason clearly.
-
Commit all intended implementation changes:
git status --short
git add <changed-files>
git commit -m "Implement plan"
git status --short
Do not include scratchpad.md or workflow handoff artifacts. The workflow merge only receives committed branch changes; uncommitted or unstaged files left in the worktree will not be included in the squash/no-ff integration merge.
- Write
.<harness>/handoff/implementation-summary.mdwith:- Plan path
- Worktree path
- Branch name
- Commit SHA, or a clear note if no commit was created
- Changed files
- Behavior changes
- Tests/checks run and results
- Skipped checks and why
- Implementation decisions and tradeoffs
- Assumptions, blockers, residual risks, or follow-up work
Output Standard
The summary must be detailed enough for a context-cleared audit agent to verify the work without relying on chat history. Treat the summary as a handoff artifact, not a final response substitute.
04 同仓库更多 Skills
example-skill
Replace this with your skill description
example-skill
Replace this with your skill description
publish-polish
Final audit and polish workflow for converting a personal Python project into a publication-ready open-source GitHub repository. Checks security and privacy (including git history), code quality, documentation, packaging metadata, and repo hygiene, then produces a structured readiness report with prioritized findings. Invoke before making a private repo public or before a first release.
optimize-repo-skills
Audits a repository's harness skills against the actual codebase, proposes conservative skill updates, and after explicit approval updates, creates, or removes repo-specific skills.
merge-conflict-resolver
Resolves merge conflicts inside a temporary integration worktree created by the workflow script, preserves approved plan intent and latest base behavior, and writes a conflict-resolution summary without committing.
cleanup-dead-code
Dead Code Cleanup for Python (using Vulture)