How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

issue:close - Prompt - OpenSmartRoute

Name: issue:close
Author: jifflee

Prompt file imported from jifflee/eagle-eye (.claude/commands/issue:close.md). Copyright stays with the author.

Close Issue

Close one or more GitHub issues through the repo-workflow agent.

Important

This command routes through the repo-workflow agent to ensure:

Issues are ready to close (linked PRs merged, acceptance criteria met)
Status transitions are valid
Issue hygiene is maintained

Instructions

When this command is invoked:

Invoke the repo-workflow agent using the Task tool with subagent_type: "repo-workflow" and model: "haiku"
Pass the user's request including:
- Issue number(s) to close
- Reason for closing (if provided)
- Whether this is completion vs. won't-fix vs. duplicate
The agent will:
- Verify each issue exists
- Check if issue has linked PRs
- Validate closure is appropriate
- Close the issue(s)
- Update any related labels
- Report back with results

Example Usage

User: /issue:close 42 Agent: Closes issue #42 after validation

User: /issue:close 10 11 12 --reason "Completed in PR #50" Agent: Closes issues #10, #11, #12 with linked PR reference

Validation

The agent will verify before closing:

Issue is in closeable state (not already closed)
If there are linked PRs, they should be merged
If marked as duplicate, original issue exists
Worktree completeness: Check for unpushed work (see Worktree Validation below)
If epic: Check for open children (see Epic Validation below)

Worktree Validation

Before closing an issue, check if a worktree exists with unpushed work:

# Validate worktree is safe to close
./scripts/worktree/worktree-validate-close.sh $ISSUE --json

If unpushed work exists:

⚠️ Issue #69 has unpushed work:

Worktree: ~/repos/my-repo-issue-69
Uncommitted files: 3
Unpushed commits: 5
Risk level: HIGH

Options:
1. Push changes first (recommended)
2. Force close (acknowledge data loss)
3. Cancel close

User must confirm to close an issue with unpushed work.

Force close flag:

/issue:close 69 --force

When --force is provided, the validation warning is bypassed and the user acknowledges potential data loss.

Epic Validation

When closing an issue with the epic label, additional checks are performed:

# Check epic completion status
./scripts/find-parent-issues.sh --epic-status $ISSUE

If open children exist:

⚠️ Epic #45 has open children:

| # | Title | Status |
|---|-------|--------|
| #47 | Fix session timeout | in-progress |
| #48 | Add 2FA | backlog |

2/5 children still open (60% complete)

Options:
1. Close anyway (children remain open)
2. Cancel close
3. View children details

User must confirm to close an epic with open children.

If all children closed:

✓ Epic #45: All 5 children closed (100% complete)
Proceeding with close.

Error Handling

If validation fails:

Report which issue(s) couldn't be closed
Explain the reason (e.g., "PR #50 not yet merged")
Suggest next steps

Token Optimization

This skill has moderate optimization with room for improvement:

Current optimizations:

✅ Routes through repo-workflow agent (delegates heavy lifting)
✅ Simple validation logic (minimal token overhead)

Token usage:

Current: ~1,250 tokens (moderate complexity)
Optimized target: ~725 tokens (with data script)
Potential savings: 42%

Remaining optimizations needed:

❌ No dedicated data script for batch close operations
❌ Issue validation done inline (could be batched)
❌ Multiple sequential gh calls for related checks

Measurement:

Baseline: 1,250 tokens (current implementation)
Target: 725 tokens (with close-issue-data.sh validation script)
See /docs/METRICS_OBSERVABILITY.md for measurement methodology

Optimization strategy: Create ./scripts/issue:close-data.sh to batch validation checks:

Check PR merge status for all issues
Check worktree status for all issues
Check epic/child relationships
Return single JSON with all validation results

Related skills:

/create-issue - Similar pattern, could share optimization approach

Notes

This is a WRITE operation - it modifies the repository
Always routes through repo-workflow agent for governance
Closing updates issue status and may trigger notifications
Worktree check: Warns before closing issues with unpushed worktree work
Epic check: Warns before closing epics with open children
Child issues: Closing a child issue does not affect the parent epic
Force flag: Use --force to bypass worktree validation (data loss warning)

Install issue:close and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

# Close Issue Close one or more GitHub issues through the repo-workflow agent. ## Important This command routes through the `repo-workflow` agent to ensure: - Issues are ready to close (linked PRs merged, acceptance criteria met) - Status transitions are valid - Issue hygiene is maintained ## Instructions When this command is invoked: 1. **Invoke the repo-workflow agent** using the Task tool with `subagent_type: "repo-workflow"` and `model: "haiku"` 2. **Pass the user's request** including: - Issue number(s) to close - Reason for closing (if provided) - Whether this is completion vs. won't-fix vs. duplicate 3. **The agent will:** - Verify each issue exists - Check if issue has linked PRs - Validate closure is appropriate - Close the issue(s) - Update any related labels - Report back with results ## Example Usage User: `/issue:close 42` Agent: Closes issue #42 after validation User: `/issue:close 10 11 12 --reason "Completed in PR #50"` Agent: Closes issues #10, #11, #12 with linked PR reference ## Validation The agent will verify before closing: - Issue is in closeable state (not already closed) - If there are linked PRs, they should be merged - If marked as duplicate, original issue exists - **Worktree completeness:** Check for unpushed work (see Worktree Validation below) - **If epic:** Check for open children (see Epic Validation below) ### Worktree Validation Before closing an issue, check if a worktree exists with unpushed work: ```bash # Validate worktree is safe to close ./scripts/worktree/worktree-validate-close.sh $ISSUE --json ``` **If unpushed work exists:** ``` ⚠️ Issue #69 has unpushed work: Worktree: ~/repos/my-repo-issue-69 Uncommitted files: 3 Unpushed commits: 5 Risk level: HIGH Options: 1. Push changes first (recommended) 2. Force close (acknowledge data loss) 3. Cancel close ``` **User must confirm to close an issue with unpushed work.** **Force close flag:** ``` /issue:close 69 --force ``` When `--force` is provided, the validation warning is bypassed and the user acknowledges potential data loss. ### Epic Validation When closing an issue with the `epic` label, additional checks are performed: ```bash # Check epic completion status ./scripts/find-parent-issues.sh --epic-status $ISSUE ``` **If open children exist:** ``` ⚠️ Epic #45 has open children: | # | Title | Status | |---|-------|--------| | #47 | Fix session timeout | in-progress | | #48 | Add 2FA | backlog | 2/5 children still open (60% complete) Options: 1. Close anyway (children remain open) 2. Cancel close 3. View children details ``` **User must confirm to close an epic with open children.** **If all children closed:** ``` ✓ Epic #45: All 5 children closed (100% complete) Proceeding with close. ``` ## Error Handling If validation fails: - Report which issue(s) couldn't be closed - Explain the reason (e.g., "PR #50 not yet merged") - Suggest next steps ## Token Optimization This skill has moderate optimization with room for improvement: **Current optimizations:** - ✅ Routes through repo-workflow agent (delegates heavy lifting) - ✅ Simple validation logic (minimal token overhead) **Token usage:** - Current: ~1,250 tokens (moderate complexity) - Optimized target: ~725 tokens (with data script) - Potential savings: **42%** **Remaining optimizations needed:** - ❌ No dedicated data script for batch close operations - ❌ Issue validation done inline (could be batched) - ❌ Multiple sequential `gh` calls for related checks **Measurement:** - Baseline: 1,250 tokens (current implementation) - Target: 725 tokens (with `close-issue-data.sh` validation script) - See `/docs/METRICS_OBSERVABILITY.md` for measurement methodology **Optimization strategy:** Create `./scripts/issue:close-data.sh` to batch validation checks: - Check PR merge status for all issues - Check worktree status for all issues - Check epic/child relationships - Return single JSON with all validation results **Related skills:** - `/create-issue` - Similar pattern, could share optimization approach ## Notes - This is a WRITE operation - it modifies the repository - Always routes through repo-workflow agent for governance - Closing updates issue status and may trigger notifications - **Worktree check:** Warns before closing issues with unpushed worktree work - **Epic check:** Warns before closing epics with open children - **Child issues:** Closing a child issue does not affect the parent epic - **Force flag:** Use `--force` to bypass worktree validation (data loss warning)

{ "prompt": "# Close Issue\n\nClose one or more GitHub issues through the repo-workflow agent.\n\n## Important\n\nThis command routes through the `repo-workflow` agent to ensure:\n- Issues are ready to close (linked PRs merged, acceptance criteria met)\n- Status transitions are valid\n- Issue hygiene is maintained\n\n## Instructions\n\nWhen this command is invoked:\n\n1. **Invoke the repo-workflow agent** using the Task tool with `subagent_type: \"repo-workflow\"` and `model: \"haiku\"`\n\n2. **Pass the user's request** including:\n - Issue number(s) to close\n - Reason for closing (if provided)\n - Whether this is completion vs. won't-fix vs. duplicate\n\n3. **The agent will:**\n - Verify each issue exists\n - Check if issue has linked PRs\n - Validate closure is appropriate\n - Close the issue(s)\n - Update any related labels\n - Report back with results\n\n## Example Usage\n\nUser: `/issue:close 42`\nAgent: Closes issue #42 after validation\n\nUser: `/issue:close 10 11 12 --reason \"Completed in PR #50\"`\nAgent: Closes issues #10, #11, #12 with linked PR reference\n\n## Validation\n\nThe agent will verify before closing:\n- Issue is in closeable state (not already closed)\n- If there are linked PRs, they should be merged\n- If marked as duplicate, original issue exists\n- **Worktree completeness:** Check for unpushed work (see Worktree Validation below)\n- **If epic:** Check for open children (see Epic Validation below)\n\n### Worktree Validation\n\nBefore closing an issue, check if a worktree exists with unpushed work:\n\n```bash\n# Validate worktree is safe to close\n./scripts/worktree/worktree-validate-close.sh $ISSUE --json\n```\n\n**If unpushed work exists:**\n```\n⚠️ Issue #69 has unpushed work:\n\nWorktree: ~/repos/my-repo-issue-69\nUncommitted files: 3\nUnpushed commits: 5\nRisk level: HIGH\n\nOptions:\n1. Push changes first (recommended)\n2. Force close (acknowledge data loss)\n3. Cancel close\n```\n\n**User must confirm to close an issue with unpushed work.**\n\n**Force close flag:**\n```\n/issue:close 69 --force\n```\n\nWhen `--force` is provided, the validation warning is bypassed and the user acknowledges potential data loss.\n\n### Epic Validation\n\nWhen closing an issue with the `epic` label, additional checks are performed:\n\n```bash\n# Check epic completion status\n./scripts/find-parent-issues.sh --epic-status $ISSUE\n```\n\n**If open children exist:**\n```\n⚠️ Epic #45 has open children:\n\n| # | Title | Status |\n|---|-------|--------|\n| #47 | Fix session timeout | in-progress |\n| #48 | Add 2FA | backlog |\n\n2/5 children still open (60% complete)\n\nOptions:\n1. Close anyway (children remain open)\n2. Cancel close\n3. View children details\n```\n\n**User must confirm to close an epic with open children.**\n\n**If all children closed:**\n```\n✓ Epic #45: All 5 children closed (100% complete)\nProceeding with close.\n```\n\n## Error Handling\n\nIf validation fails:\n- Report which issue(s) couldn't be closed\n- Explain the reason (e.g., \"PR #50 not yet merged\")\n- Suggest next steps\n\n## Token Optimization\n\nThis skill has moderate optimization with room for improvement:\n\n**Current optimizations:**\n- ✅ Routes through repo-workflow agent (delegates heavy lifting)\n- ✅ Simple validation logic (minimal token overhead)\n\n**Token usage:**\n- Current: ~1,250 tokens (moderate complexity)\n- Optimized target: ~725 tokens (with data script)\n- Potential savings: **42%**\n\n**Remaining optimizations needed:**\n- ❌ No dedicated data script for batch close operations\n- ❌ Issue validation done inline (could be batched)\n- ❌ Multiple sequential `gh` calls for related checks\n\n**Measurement:**\n- Baseline: 1,250 tokens (current implementation)\n- Target: 725 tokens (with `close-issue-data.sh` validation script)\n- See `/docs/METRICS_OBSERVABILITY.md` for measurement methodology\n\n**Optimization strategy:**\nCreate `./scripts/issue:close-data.sh` to batch validation checks:\n- Check PR merge status for all issues\n- Check worktree status for all issues\n- Check epic/child relationships\n- Return single JSON with all validation results\n\n**Related skills:**\n- `/create-issue` - Similar pattern, could share optimization approach\n\n## Notes\n\n- This is a WRITE operation - it modifies the repository\n- Always routes through repo-workflow agent for governance\n- Closing updates issue status and may trigger notifications\n- **Worktree check:** Warns before closing issues with unpushed worktree work\n- **Epic check:** Warns before closing epics with open children\n- **Child issues:** Closing a child issue does not affect the parent epic\n- **Force flag:** Use `--force` to bypass worktree validation (data loss warning)", "variables": [], "notes": "Close GitHub issue(s) using the repo-workflow agent (validates before closing)", "metadata": { "source": { "provider": "github-claude-commands", "repository": "https://github.com/jifflee/eagle-eye", "path": ".claude/commands/issue:close.md", "ref": "4da572bac83949ced9fa455d5470b3477d95ce24", "url": "https://github.com/jifflee/eagle-eye/blob/4da572bac83949ced9fa455d5470b3477d95ce24/.claude/commands/issue:close.md", "key": "jifflee/eagle-eye/.claude/commands/issue:close.md" } } }

issue:close

About

Close Issue

Important

Instructions

Example Usage

Validation

Worktree Validation

Epic Validation

Error Handling

Token Optimization

Notes

Install issue:close and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews