Menu
Use when completing tasks or features to request code review
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | arc-requesting-review |
| description | Use when completing tasks or features to request code review |
Mandatory:
Optional:
Review frequency by workflow:
Get git SHAs:
BASE_SHA=$(git rev-parse HEAD~1)
HEAD_SHA=$(git rev-parse HEAD)
Dispatch code-reviewer subagent (arcforge:code-reviewer) using the template at arc-requesting-review/code-reviewer.md (this skill's directory) and fill placeholders:
Required placeholders:
{WHAT_WAS_IMPLEMENTED}{PLAN_OR_REQUIREMENTS}{BASE_SHA}{HEAD_SHA}{DESCRIPTION}[Just completed Task 2: Add verification function]
BASE_SHA=$(git rev-parse HEAD~1)
HEAD_SHA=$(git rev-parse HEAD)
[Dispatch code-reviewer]
WHAT_WAS_IMPLEMENTED: Verification and repair functions
PLAN_OR_REQUIREMENTS: Task 2 from docs/tasks/verify-index-tasks.md
BASE_SHA: a7981ec
HEAD_SHA: 3df7661
DESCRIPTION: Added verifyIndex() and repairIndex() with 4 issue types
[Reviewer feedback]
Important: Missing progress reporting
Minor: Magic number for reporting interval
[Fix Important, note Minor, then continue]
When reviewer feedback arrives:
arc-receiving-review to process feedback with technical rigorarc-verifying → arc-finishing (Step 0 discriminates on .arcforge-epic)Use when running autonomous unattended loops — cross-session execution of DAG tasks without human intervention
Use when converting design documents to structured specs, when spec quality is below threshold, or when requirements need formal acceptance criteria
Use when you need to verify work is complete before making completion claims
Use when maintaining ArcForge itself by creating, editing, or verifying ArcForge skills before deployment
Use when optional learning is enabled and observations should become reviewable candidates, inactive drafts, and explicitly activated artifacts.
Use when user asks about behavioral patterns, requests instinct status, or wants to confirm/contradict a detected pattern