Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From sanctum
Resolves GitHub/GitLab/Bitbucket issues via parallel subagent tasks, dependency analysis, code review gates between batches, and single consolidated PR.
npx claudepluginhub athola/claude-night-market --plugin sanctumHow this skill is triggered — by the user, by Claude, or both
Slash command
/sanctum:do-issueThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
- [Key Features](#key-features)
Executes GitHub issues by reading content with read-github-issue, delegating tasks to frontend-implementer or general-purpose-assistant sub-agents, running tests/lint, committing on worktree, and creating PRs via commit-push and create-pr.
Grooms all open GitHub issues with subagents for clarity then loops implementation: branch, research, swarm code, test, commit, merge PRs until backlog cleared.
Guides technical evaluation of code review feedback: read fully, restate for understanding, verify against codebase, respond with reasoning or pushback before implementing.
Share bugs, ideas, or general feedback.
Retrieves issue content from the detected git platform (GitHub, GitLab, or Bitbucket) and uses subagent-driven-development to systematically address requirements, executing tasks in parallel where dependencies allow.
Platform detection is automatic via the leyline:git-platform SessionStart hook. Check session context for git_platform: to determine which CLI to use.
| Phase | Description | Module |
|---|---|---|
| 1. Discovery | Parse input, fetch issues, extract requirements | issue-discovery |
| 2. Planning | Analyze dependencies, create task breakdown | task-planning |
| 3. Execution | Dispatch parallel subagents for independent tasks | parallel-execution |
| 4. Quality | Code review gates between task batches | quality-gates |
| 5-6. Completion | Sequential tasks, final review, issue updates | completion |
do-issue:discovery-completedo-issue:tasks-planneddo-issue:parallel-batch-completedo-issue:review-passeddo-issue:sequential-completedo-issue:issues-updatedUse the platform detected in session context (git_platform:). See Skill(leyline:git-platform) for full mapping.
| Operation | GitHub (gh) | GitLab (glab) |
|---|---|---|
| Fetch issue | gh issue view <N> --json title,body,labels,comments | glab issue view <N> |
| Comment | gh issue comment <N> --body "msg" | glab issue note <N> --message "msg" |
| Close | gh issue close <N> --comment "reason" | glab issue close <N> |
| Search | gh issue list --search "query" | glab issue list --search "query" |
Verification: Run the command with --help flag to verify availability.
Agent teams is the default parallel execution backend for do-issue. Teammates coordinate via filesystem-based messaging, enabling real-time communication when shared files or dependencies are discovered mid-implementation.
Automatic downgrade: For single issues with --scope minor, agent teams is skipped (Task tool or inline execution is used instead). Use --no-agent-teams to force Task tool dispatch for any invocation.
Requires: Claude Code 2.1.32+, tmux, CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1. If prerequisites are missing, silently falls back to Task tool dispatch.
# Agent teams configuration
fix_issue:
agent_teams:
enabled: true # on by default; --no-agent-teams to disable
max_teammates: 4 # limit concurrent workers
model: sonnet # teammate model (lead uses current model)
auto_downgrade: true # skip agent teams for --scope minor
See modules/parallel-execution.md for detailed agent teams patterns.
fix_issue:
parallel_execution: true
max_parallel_subagents: 3
review_between_batches: true
auto_close_issues: false
commit_per_task: true
Verification: Run the command with --help flag to verify availability.