Replace the commiter subagent with a create-commit skill, consistent with the create-pr and create-issue skill patterns. - Remove .opencode/agents/commiter.md - Add .opencode/skills/create-commit/SKILL.md - Update implement-plan.md to use the skill instead of subagent delegation - Document commit body line wrapping at 72 chars in creating-commits memory and skill AI-assisted-by: mimo-v2.5
1.4 KiB
description, agent
| description | agent |
|---|---|
| Execute a ready plan end-to-end — create a GitHub issue, branch issue-NNNN, implement the plan, then commit via the create-commit skill | build |
Implement Plan
This command is run once a plan is ready (for example, from plan mode). Execute the plan already prepared in the current session context — it does not take extra arguments. Follow these steps in order.
1. Create the issue
Use the create-issue skill, following the Creating Issues from Draft Body
flow in mem:workflow/creating-issues. Derive the issue title and body from the
plan. Capture the new issue's number — call it NNNN (needed for the branch
name and the commit reference).
2. Create the branch
Create and switch to a branch named after the issue:
git checkout -b issue-NNNN
(Replace NNNN with the issue number from step 1.)
3. Execute the plan
Implement the prepared plan from the session context. Work methodically, keeping changes focused on what the issue requires. Do not commit — the commit happens in step 4.
4. Commit with the create-commit skill
After the implementation is complete, load the create-commit skill and
follow its workflow to commit the changes. Provide a brief summary of what was
implemented and why, the issue reference (issue-NNNN), and the model name you
are running as so the AI-assisted-by trailer is set correctly.
Do not push. Pushing is handled separately by the user.