메뉴
Configures CLAUDE.md and .github/copilot-instructions.md for a project, creating or updating them to point to a shared AGENTS.md file. Handles multiple scenarios depending on which files already exist. Usage: /init-claude
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Monitors a given PR for merge/close/approval/new owner comments, blocking until one of those occurs, then reports the outcome. Tracks each owner comment's open/addressed lifecycle with :eyes:/:+1: reactions on the comment itself, but leaves deciding how to address a comment to the caller. Usage: /auto-monitor-pr <pr_number>
Autonomously runs the full pipeline (new issue → plan → fix → monitor) for a queue of issue IDs, one at a time, forever — waiting for new IDs to be pushed onto the queue whenever it runs dry — with no user interaction except when a PR is closed without merging. Usage: /auto-fix-all <id1> <id2> ...
Autonomously implements a planned issue with no user interaction. Discovers the specialist agents involved in the plan, dispatches them in parallel, reviews and re-dispatches until correct, then opens or marks ready a pull request. Usage: /auto-fix-issue <id> or /auto-fix-issue #<id>
Discusses and refines an existing GitHub issue through an iterative dialogue, optionally spawning specialist agents to deepen understanding, then saves a structured markdown issue file and, on confirmation, kicks off planning on a committed branch. Usage: /discuss-issue #19
Resolves the PR for an issue's currently checked-out branch, then monitors it for merge/close/approval/new owner comments, blocking until one of those occurs. Used by auto-fix-all. Usage: /auto-monitor-issue-pr <id>
Creates a implementation plan for a given issue. Reads the issue file, analyzes the codebase, asks clarifying questions, and writes a structured plan in the plans folder. Usage: /plan-issue 99 or /plan-issue #99
| name | init-claude |
| description | Configures CLAUDE.md and .github/copilot-instructions.md for a project, creating or updating them to point to a shared AGENTS.md file. Handles multiple scenarios depending on which files already exist. Usage: /init-claude |
You are helping the user initialize or update the Claude and Copilot configuration files for the current project.
Read and follow setup_templates.md.
Check which of these files exist in the current working directory:
AGENTS.mdCLAUDE.md.github/copilot-instructions.mdBased on what exists, read and follow the appropriate scenario file:
| AGENTS.md | CLAUDE.md | copilot-instructions.md | Scenario file |
|---|---|---|---|
| absent | absent | absent | scenario_new.md |
| absent | present | absent | scenario_claude_only.md |
| absent | absent | present | scenario_copilot_only.md |
| present | absent | absent | scenario_agents_only.md |
| absent | present | present | scenario_both_no_agents.md |
| present | present | absent | scenario_agents_claude.md |
| present | absent | present | scenario_agents_copilot.md |
| present | present | present | scenario_all_present.md |
If the detected scenario is marked as "not yet defined", inform the user:
This scenario is not yet implemented. Please open an issue or contribute a scenario file.
Then stop.
After the scenario completes successfully, read and follow setup_docs_structure.md.
After the documentation structure is created, read and follow setup_folder_structure.md.
After the folder structure document is created, read and follow setup_architecture.md.
After the architecture document is created, read and follow setup_contributing.md.
After the contributing guide is created, read and follow setup_agents.md.
After the agents are set up, read and follow setup_ci_monitoring.md.