메뉴
Close an issue as status:migrated or status:cancelled with --reason not_planned. Applies label, posts comment, and closes.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | issue-close-migrated |
| description | Close an issue as status:migrated or status:cancelled with --reason not_planned. Applies label, posts comment, and closes. |
| user-invocable | false |
Close issue <N> as migrated (merged into another issue) or cancelled.
Usage:
/issue-close-migrated <N> --type migrated --into <M> — issue N merged into M/issue-close-migrated <N> --type cancelled — issue N cancelled--into <M> is required for --type migrated and prohibited for --type cancelled.
N, TYPE, and (if migrated) INTO from the invocation arguments.N is OPEN: gh issue view N --json state --jq .state. Not OPEN → report and exit 0.--type migrated: verify issue INTO is OPEN. Not OPEN → report and exit 0.Run: bash "$AGENTS_CONFIG_DIR/skills/issue-close-migrated/scripts/pre-flight.sh" "$N" "$TYPE" "$INTO" || { echo "Pre-flight failed — check issue state"; exit 0; }
Run bin/github-issues/close-not-planned.sh:
bash "$AGENTS_CONFIG_DIR/bin/github-issues/close-not-planned.sh" \
--type "$TYPE" $([ "$TYPE" = "migrated" ] && echo "--into $INTO") \
"$N"
The gh issue close inside close-not-planned.sh is a subprocess of the Bash tool command — enforce-issue-close.js (PreToolUse) fires only on the Bash tool command head, not on subprocess calls. No bypass marker is required.
--reason not_planned via close-not-planned.sh. Never use --reason completed for migrated or cancelled issues.gh issue close directly from this skill — use close-not-planned.sh.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.