kf-g-agent-git-managed-workflow

Work procedure for git-managed files

For changes to git-managed files, proceed in this order: issue, worktree, commit, push, PR.

Reference files

• workflow.md: Procedure from issue to PR
• worktree.md: Branch names and worktree placement

How to proceed with reading

1. workflow.md Read and determine the order of starting work
2. If starting from an issue, worktree.md create a worktree according to
3. commit は kf-g-git-commit-atomic-rules Follow
4. Satisfy the "Completion criteria" below
5. Determine completion using the "Final check" below

Completion criteria

For work that changes git-managed files, complete the following consistently after implementation and verification.

1. Make an atomic commit
2. Push to remote
3. Create a PR
4. Include the PR URL in the response to the user

For work starting from an issue, also record the PR URL in the corresponding issue.

Only for R2 distribution of HTML reports with no file change diffs, do not create a PR.

If the user explicitly prohibits committing or creating a PR, follow that instruction.

Final check

1. For work requiring planning, an issue has been created before creating the worktree
2. Changes are made only within the dedicated worktree, not directly on main
3. Changes are divided into logical units and atomically committed after verification
4. For work with file change diffs, commit, push, and PR creation have been completed
5. The PR URL is included in the response to the user
6. Hook failures before commit / push are --no-verify not avoided with