القائمة
Use when the task is fully bounded with no open decisions — rename, refactor, extract, multi-var/multi-file change, API shape already known, config nudge, copy update, trivial targeted bugfix
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when the user provides a GitHub PR link with a "deep review" trigger inside a locally cloned repo, to perform a thorough multi-dimensional code review grounded in ARCS DAG context, AGENTS.md conventions, and optional codegraph coupling analysis, then post findings as inline GitHub review comments under explicit user gate
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Use when initializing a new ARCS project — bootstrapping a repo into the DAG with metadata, docs, and structural knowledge entries. Covers gather → present summary → init → codegraph ingestion → fan-out analysis across typed sub-agents.
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Use when implementing any feature or bugfix, before writing implementation code
Use when you have a spec or requirements for a multi-step task, before touching code
| name | quick-dev |
| description | Use when the task is fully bounded with no open decisions — rename, refactor, extract, multi-var/multi-file change, API shape already known, config nudge, copy update, trivial targeted bugfix |
Task is fully bounded — no open decisions, success criteria derivable without asking.
flowchart TD
A[Orient: arcs brief --lean --json] --> K[Knowledge: arcs knowledge search slug keywords]
K --> B{Fully bounded?}
B -->|Yes| C[Execute change directly]
B -->|No| D[Escalate to code-agent or brainstorming]
C --> E[Verify scoped: tsc --noEmit + lint + tests for touched files]
E --> F[Done — commit only when asked]
arcs knowledge search <slug> "<keywords>" --lean --json
Check for patterns, gotchas, and lessons before implementing. Skip only if the change is purely mechanical (rename, config nudge).
If a "bounded" change surfaced a non-obvious gotcha along the way, capture it before finishing: arcs knowledge upsert <slug> "<title>" --kind=gotcha --summary="<the trap in 1-2 sentences>" --keywords="<k1,k2>" --source-files="<path,...>" --json. Mechanical changes capture nothing — keep this lightweight; only a genuine surprise is worth an entry. Upsert is idempotent by title.
the-ladder before writing code — climb the rungs (stdlib / native platform / installed dep before new code) and mark deliberate simplifications with // SHORTCUT: commentsIf hidden complexity surfaces mid-task — pause immediately, state the issue, offer to switch to code-agent or brainstorming. Do not silently expand scope.
If self-confidence drops below 80% (open decision, unverified assumption, sibling pattern unclear), escalate to code-agent — quick-dev does not permit exploration loops; code-agent does.
code-agentbrainstorming