Menu
Sync the target repo's labels and create/link its Projects v2 board to make it ready for GitHub Issues.
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
Conduct a decision-tree interview with the user to lock in requirements, motivation, scope, and non-goals before planning.
Stage 3 of three-stage planning pipeline. Produce a file-level implementation plan via detail-planner/detail-reviewer loop, then get user approval. Inputs are confirmed intent (<session-id>-intent.md) and outline (<session-id>-outline.md) from prior stages.
Edit source code for the current task. Delegates editing and lint/typecheck/self-repair to a subagent.
Plan and write test cases with high reasoning effort. Test iteration runs in a subagent to minimize confirmations.
Explore the codebase to understand existing patterns, constraints, and relevant files before planning.
Investigate git history, docs/history.md, and GitHub issue/PR timeline since the relevant issue opened, to surface changes that may invalidate the issue's premises.
| name | issue-setup |
| description | Sync the target repo's labels and create/link its Projects v2 board to make it ready for GitHub Issues. |
| user-invocable | true |
Initialize a target repo for GitHub Issues: sync its label set and create/link a Projects v2 board.
agents/.github/labels.yml) and initialize its Projects v2 board.AGENTS_CONFIG_DIR must be set.gh must be authenticated with the project scope; if absent, tell the user to run gh auth refresh -s project and stop.bin/is-github-dotcom-remote against the target repo; on rc=1, exit 0 with a notice.IS-1. Confirm the target repo via AskUserQuestion:
current: use the CWD repo (resolve via gh repo view).other: prompt for an OWNER/REPO string.IS-2. Sync labels (no confirmation — automatic): run run-issue-setup.sh --step labels --repo "$TARGET_REPO".
IS-3. Check the project: run run-issue-setup.sh --step check-project --repo "$TARGET_REPO" → rc=0 present / rc=1 absent.
IS-4. When the project is absent, AskUserQuestion:
create: run run-issue-setup.sh --step ensure-project --repo "$TARGET_REPO".skip: notify the user that a manual link is required, then exit 0.IS-5. Report the outcome to the user.
Backend script path: $AGENTS_CONFIG_DIR/skills/issue-setup/scripts/run-issue-setup.sh.