Menu
Deep-dive a tool or repo in .references/. Documents purpose, usage, novel patterns, and distills learnings into steering/skills. Use when onboarding a new reference repo or tool.
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
Dispatch Codex to review all unreviewed repository work, then verify its correlated findings ticket or clean result. Use when requesting an independent Codex review, auditing all changes, checking work since the last review, or waiting for Codex findings. Trigger: dispatch codex review, independent review, review all changes, check codex findings, run review agent.
Always-on: when a project has tickets, work the frontier (first unblocked open ticket), mark done, update plan status.
Incremental and full-history repository review with resumable adoption batches. Use when reviewing new work, initializing review tracking, reviewing all work to date, resuming historical review, inspecting unreviewed commits, or reviewing changed tickets. Trigger: review new work, adopt repository, review all history, resume review, review marker, unreviewed commits.
End-of-session handoff that captures current state for the next session. Use when ending a work session, switching context, or before a long break.
Consolidate project artifacts — promote scratch to memory, deduplicate memory, process decisions, organize scripts, update steering/skills accuracy. Use periodically or when the project feels cluttered.
Run and interpret crew-research evals — run.sh flags, scores.jsonl fields, activation TPR/FPR verdicts, resuming interrupted runs. Use when running evals, reading eval results, diagnosing a failing definition, or resuming a dead run. Trigger: run the evals, eval results, scores.jsonl, activation test, TPR, delta threshold, resume the run, skip-completed, known gap.
| name | study-reference |
| description | Deep-dive a tool or repo in .references/. Documents purpose, usage, novel patterns, and distills learnings into steering/skills. Use when onboarding a new reference repo or tool. |
| metadata | {"type":"process","invocation":"user-only","practice":null} |
Analyze a tool or third-party repo and extract actionable knowledge from it.
Check if .memory/{name}-reference.md already exists with a studied_at frontmatter field. If it does, skip — already studied. If the file exists but has no frontmatter (legacy/partial), re-study.
Dispatch a subagent to explore the repo/tool and write a reference doc to .memory/:
Output: .memory/{name}-reference.md
---
studied_at: {ISO 8601 timestamp}
source: .references/{name}
---
Analyze along these dimensions:
Review the reference doc and identify what should become project guidance:
Present candidates and wait for approval before applying.
For each approved candidate:
docs: study {name} — {what was learned}