Menu
GitHub issue lifecycle management with worktree isolation
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Set up a repo-local just task runner with a root Justfile, optional .just/ helper scripts, and curated help, build, fmt, lint, test, and ci recipes. Use when a repo needs just, a Justfile, .just helpers, or when the user mentions task automation, "just build", "just lint", "just fmt", or dropping in a just system.
Create or harden CLIs intended primarily for AI or system consumption and secondarily for humans. Use when designing or implementing a JSON-first CLI with an MCP-ready contract seam, where every command supports machine output, errors are typed and actionable, mutating commands are auditable via corresponding read commands, and external integrations need simulator-backed testing. Do not use for human-first shell utilities, one-off scripts, or text-only CLIs.
Design stateful simulators for AI-facing CLIs that integrate with devices, networks, services, or databases. Use when a CLI needs realistic simulator-backed testing, configurable fault injection, persistent state, and a swappable adapter boundary so the same business logic runs against live and simulated backends. Do not use for shallow mocks, stateless test doubles, or CLIs with no external integration.
Critically review an existing CLI, MCP wrapper, or CLI plan for AI-first contract quality. Use when evaluating whether a CLI is JSON-first, has an MCP-ready contract seam without JSON reshaping, auditably models state changes, uses stateful simulator-backed testing for external integrations, and returns typed actionable errors. Do not use for general style review or human-first shell UX review.
Run CI quality gates with optional auto-fix and PR creation.
Run Codex tasks via the ai_cli Task Tool runner.
| name | sc-managing-github-issues |
| version | 0.12.0 |
| description | GitHub issue lifecycle management with worktree isolation |
| entry_point | /sc-github-issue |
Manage GitHub issues from listing to fixing to PR creation with clean worktree isolation.
/sc-github-issue - Main entry point for all issue operationssc-github-issue-intake - List and fetch issue detailssc-github-issue-mutate - Create and update issuessc-github-issue-fix - Implement fixes in isolated worktreessc-github-issue-pr - Create pull requests--list [--repo owner/repo] - List open issues--create - Create issue interactively--update <id> - Update issue fields--fix --issue <id/url> [--yolo] - Full fix workflow: fetch → confirm → worktree → implement → test → commit → push → PRgh) version 2.0 or higherConfiguration via manifest options (defaults shown):
options:
base-branch:
type: string
default: "main"
branch-pattern:
type: string
default: "fix-issue-{number}"
auto-pr:
type: boolean
default: true
Users can override in .claude/config.yaml:
packages:
sc-github-issue:
base-branch: develop
branch-pattern: "hotfix/{number}"
auto-pr: false
github:
test_command: "npm test"
pr_template: |
## Summary
Fixes #{issue_number}
All agents return fenced JSON with v0.4 minimal envelope:
{
"success": true|false,
"data": { /* operation results */ },
"error": null|{
"code": "ERROR.CODE",
"message": "Human readable message",
"recoverable": true|false,
"suggested_action": "What to do next"
}
}
gh CLI auth checks--yolo)The --fix workflow creates isolated worktrees via the sc-git-worktree skill:
sc-worktree-create agent creates fix-issue-{number} worktree/sc-git-worktree --cleanup after PR mergeThis ensures the main working directory remains clean during fix implementation.
references/github-issue-apis.md - GitHub CLI patternsreferences/github-issue-checklists.md - Workflow checklists