Menu
Commit changed skill files and close the in-progress issue — writes a traceability commit message referencing the issue number
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | commit |
| description | Commit changed skill files and close the in-progress issue — writes a traceability commit message referencing the issue number |
| argument-hint | [issue-number] |
| allowed-tools | Bash, Read |
| user-invocable | true |
| metadata | {"version":"1.0","created":"2026-04-28T00:00:00.000Z","author":"Ability.ai","changelog":["1.0: Initial version — stages changed skill files, writes a traceability commit referencing the in-progress issue, and closes it"]} |
ℹ️ First, set expectations: before anything else, print one short line with this skill's version and its most recent change — the top entry of
metadata.changelogabove — e.g.commit vX.Y — recent: <summary>. Then proceed.
Stage changed skill files, write a commit message tied to the in-progress issue, and close the issue with a summary. The single action that closes the loop between a GitHub issue and a SKILL.md change.
| Source | Location | Read | Write | Description |
|---|---|---|---|---|
| GitHub Issues | Current repo | Yes | Yes | Close the in-progress issue |
| Git working tree | ./ | Yes | Yes | Stage and commit skill files |
gh CLI authenticatedgh issue list --label "status:in-progress" --state open --json number,title,body,labels --limit 5
If an issue number was passed as $ARGUMENTS, use that instead.
If multiple in-progress issues, ask which one this commit closes.
git status --short
Surface all modified, added, or deleted files. Flag anything that is NOT a SKILL.md or agent configuration file (CLAUDE.md, template.yaml) — confirm the user wants to include it.
If there are no changes at all: report "Nothing to commit. Did /adjust-playbook or /create-playbook run yet?"
Stage all changed agent files:
git add .claude/skills/
git add CLAUDE.md # if modified
If other files were modified, confirm before staging.
Show the staged diff summary:
git diff --cached --stat
Derive the commit message from the issue:
skill:* label: [$SKILL_NAME]: $SHORT_DESCRIPTION (closes #$NUMBER)[agent]: $SHORT_DESCRIPTION (closes #$NUMBER)Examples:
[adjust-playbook]: detect breaking interface changes (closes #14)[work-loop]: route skill issues by label (closes #3)[agent]: update onboarding section in CLAUDE.md (closes #1)Show the message and ask for confirmation or edits.
git commit -m "$(cat <<'EOF'
$COMMIT_MESSAGE
EOF
)"
Add a completion comment:
gh issue comment $NUMBER --body "## Completed
$SUMMARY_FROM_DIFF
Committed: \`$COMMIT_SHA\`
---
*Closed via /commit*"
Update labels and close:
gh issue edit $NUMBER --remove-label "status:in-progress" --add-label "status:done"
gh issue close $NUMBER --reason completed
## Committed and Closed
Commit: $COMMIT_SHA
Issue: #$NUMBER closed — $TITLE
Next: `/backlog` or `/claim` for the next issue.
status:done and closed| Error | Action |
|---|---|
| Nothing staged | Report, ask if /adjust-playbook ran |
| No in-progress issue | Ask for issue number |
| Commit fails | Show error, do not close issue |
| Issue close fails | Report — commit already done, close manually |
Run a remote Trinity agent task in a sequential, bounded loop — a fixed number of iterations or until a stop signal, with optional response chaining. Fires server-side via run_agent_loop (caller can disconnect), then polls and renders progress. The remote, durable counterpart to Claude Code's local /loop. Add `local` to run the same bounded loop natively in this session instead — inline back-to-back iterations, or a hand-off to the built-in /loop when a cadence is given.
Make any agent a system-aware orchestrator — installs /discover-agents (discover the fleet from live Trinity and/or a repo list into a descriptive fleet/system-map.yaml), /compose-system (turn the map into a Trinity SystemManifest and deploy_system), and /orchestrate (route, fan out, and run ephemeral agents via Trinity MCP). Aligns with Trinity's existing SystemManifest; no parallel standard.
Create a new skill or playbook. Guides through requirements gathering and generates the appropriate template based on complexity.
Create an executive chief of staff agent — asks about your tools, team, and priorities, then scaffolds a Trinity-compatible agent for daily briefings, meeting prep, and decision tracking
Create a personal medical-records agent — bootstraps a profile from your existing health documents, then ingests new files, maintains structured memory, tracks lab trends, prepares doctor visits, and runs an evidence-based nutrition + supplement framework
Create a content writer agent — asks about your brand voice, platforms, and topics, then scaffolds a Trinity-compatible ghostwriter agent that writes in your voice