create-commit
Create a commit
Produce a clean, conventional commit message for staged changes and commit them.
Important
- Do not push to remote.
- Create multiple commits one at a time in order.
- Never stage:
.env,*.key,*.pem,*secret*,*credential*,*.p12,*.jks. - Infer commit type: Look for a plan file in
docs/plan/and extract the type (feat, fix, refactor, etc.) from the plan title or metadata. If no plan is found, infer from the diff.
When to use
Use this skill when:
- The user asks to commit staged changes.
- The user asks to "create a commit", "commit this", or similar.
- Work on a task is complete and there are staged changes ready to be committed.
More from verygoodopensource/vgv-wingspan
create
Scaffolds a new project by routing to the right companion plugin's create skill. Use when user says "create a project", "new flutter app", "start a dart package", "scaffold", or asks to set up a new codebase.
4debrief
Produces a structured post-incident analysis — timeline, root cause, and actionable follow-ups — while context is fresh. Use when user says "debrief", "post-mortem", "incident review", or "root cause analysis".
4hotfix
Applies a minimal, targeted fix for emergency bugs — enforces review and testing without brainstorm or planning phases.
4rebase
Rebases the current feature branch onto the base branch (main/master/develop). Use when user says "rebase", "sync branch", or "update branch".
4build
Executes an implementation plan — writes code and tests, runs quality review, and ships a pull request. Use when user says "build this", "implement the plan", "start coding", "execute the plan", or "ship it".
4plan
Turns high-level brainstorming and ideas into well-structured, actionable implementation plans. Use when user says "plan this", "create a plan", "how should we implement", or "write an implementation plan".
4