commit-push-close
commit-push-close
Three-step ship for one GitHub-issue iteration (with an inline create-if-missing step for the issue):
- Resolve or create the GitHub issue.
- Commit the diff with a structured message (prefix chosen by issue state).
- Push to the current branch.
- Close the GitHub issue with a comment explaining how to test it.
Prefix selection
The subject prefix depends on the linked issue's state label:
| Issue state | Prefix |
|---|---|
ready-for-human |
HITL: |
ready-for-agent |
AKF: |
| neither | ask the user which to use |
| no linked issue | create one inline (see Inline issue creation) — the user picks the state label during creation, which fixes the prefix |
More from devarfeen/agent-skills-kit
release-notes
Generate clear, PM-friendly release notes and session summaries from git commits, feature work, or current development changes.
19agents-md
Generate or update AGENTS.md for a repository or VS Code workspace, create CLAUDE.md and GEMINI.md shims, build a project matrix with stable project codes, and reference CONTEXT.md / ADRs as required domain context.
13feature-prompt
Use when the user wants to turn a feature idea, change request, or rough requirement into a precise feature-development prompt for one or more codebase projects.
12feature-discovery
Use when the user asks to investigate, audit, trace, or explain how a feature, issue, module, workflow, API, config, or behavior works across one or more codebase projects.
11commit-push-pr
Ship one iteration of work on a GitHub issue as a pull request — stage and commit with a structured message, push the current branch, and open a PR that uses `Closes #N` to auto-close the linked issue on merge. If no GitHub issue can be located, the skill creates one inline before committing. The commit subject prefix is chosen by the issue's state label (`HITL:` for `ready-for-human`, `AKF:` for `ready-for-agent`). Use when the user says "commit, push, and open a PR", "ship this as a PR", "PR this issue", or otherwise wants to wrap up issue work as a reviewable PR rather than a direct close.
5ubiquitous-language
Use when the user wants to create or update a DDD-style ubiquitous language glossary, define domain terms, resolve ambiguous terminology, harden naming, or write UBIQUITOUS_LANGUAGE.md from the current conversation and codebase context.
5