Menú
Close the current issue without a git commit — adds summary comment and marks done. Use /commit instead when skill files changed.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
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
| name | close |
| description | Close the current issue without a git commit — adds summary comment and marks done. Use /commit instead when skill files changed. |
| argument-hint | "summary of what was done" |
| 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 — closes the current in-progress issue with a summary comment, no git commit"]} |
ℹ️ 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.close vX.Y — recent: <summary>. Then proceed.
Complete the current in-progress issue with a summary comment. For issues where skill files were modified, use /commit instead — it closes the issue and creates a git commit in one step.
| Source | Location | Read | Write | Description |
|---|---|---|---|---|
| GitHub Issues | Current repo | Yes | Yes | Close issue |
| GitHub Labels | status:* | Yes | Yes | Update status |
git status --short
If SKILL.md files appear in the output, warn:
"There are modified skill files (
git status). Run/commitinstead to create a git commit alongside closing this issue."
Let user confirm they want to close without committing.
gh issue list --label "status:in-progress" --state open --json number,title --limit 5
If multiple in-progress, ask which to close. If none, report "No issue currently in progress."
If $ARGUMENTS is provided, use it as the summary. Otherwise ask:
"What was accomplished? Brief summary for the closing comment."
gh issue comment $NUMBER --body "## Completed
$SUMMARY
---
*Closed via /close*"
gh issue edit $NUMBER --remove-label "status:in-progress" --add-label "status:done"
gh issue close $NUMBER --reason completed
## Closed: #$NUMBER — $TITLE
$SUMMARY
Next: `/backlog` to see remaining work, or `/claim` for the next issue.
| Error | Action |
|---|---|
| No in-progress work | Report and suggest /claim |
| Multiple in-progress | List them, ask which to close |
| Modified skill files | Recommend /commit before closing |