메뉴
Review a change against issue, RFC, branch, and user-request scope. Use when a broad review needs a dedicated scope/completeness pass or when the user asks whether the implementation actually matches the intended surface.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Drafts a GitHub issue title and body using the target repository's issue templates under .github/ISSUE_TEMPLATE. Use when the user asks to create, draft, or file a GitHub issue, bug report, feature request, chore, documentation issue, or RFC proposal, or wants issue text that matches the repo's template.
Drafts implementation plans with TDD, documentation updates, and repository verification commands before coding. Use when the user asks for an implementation plan, /create-plan, or structured pre-implementation design for work in encero workspaces (e.g. Incan, IncQL).
Generate a PR description following the repository's pull request template. Use when the user asks to create, draft, or generate a PR description for a pull request. The skill automatically locates the PR template in the target repository and fills it in based on the git diff.
Detect, triage, de-duplicate, and raise compiler bug reports when an agent encounters a likely compiler defect during implementation, review, testing, or issue work. Use when a task surfaces an ICE, panic, wrong accept/reject behavior, miscompile, lowering/emission bug, diagnostic bug, formatter/LSP/frontend drift, or other likely compiler/tooling defect; pause current work, minimize the repro, decide whether the bug blocks the task or has a valid workaround, check whether it is already reported, and then use create-github-issue to raise the bug.
Run a high-thoroughness end-to-end implementation loop using clean worker worktrees, per-slice planning, implementation, explicit review/fix iteration, orchestrator integration, and final commit/PR drafting. Use when the user explicitly wants a Ralph/Wiggum-style loop, autonomous multi-agent execution, a delegated feature/bugfix carried from confirmed scope through review-ready completion, or RFC-driven implementation that should be reviewed, bumped to In Progress, decomposed into phases, and executed through nested sub-loops. Supports Codex subagents by default and external CLI workers such as OpenCode when explicitly requested and available.
Prepare to work on a GitHub issue or RFC. Use when the user says /start-work, asks to start an issue, begin an RFC implementation, or pick up a task. Creates the branch, gathers context, and checks learnings.
| name | review-scope |
| description | Review a change against issue, RFC, branch, and user-request scope. Use when a broad review needs a dedicated scope/completeness pass or when the user asks whether the implementation actually matches the intended surface. |
/review-scope is a cross-file report-only reviewer for intended scope and delivered behavior.
Own:
Do not own:
Write a slice report at:
.agents/state/review-report.scope.mdDo not write to the canonical .agents/state/review-report.md.
# Review Slice Report
- role: scope
- worker: <agent-id or stable label>
- status: in_progress | clean | blocked
## Scope
- issue / RFC:
- reviewed surfaces:
- ...
## Findings
- [ ] blocker | behavior | docs-generated fiction | workspaces/docs-site/docs/language/reference/project_lifecycle.md:181
Says plain `incan build` remains a valid direct command, but the CLI still requires `<FILE>` outside `--lib`.
## Reviewed Clean Surfaces
- <optional, only for risky or disputed clean calls>
## Notes
- <optional broader scope observation>
Use `Notes` for context, but keep actual concerns in `## Findings` rather than hiding them in prose.
If there are no findings, say so explicitly.