Menu
Fast CodeClone quality snapshot — health, top risks, or one metric, without a full review loop.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Human repository setup readiness — status, plan, apply, and wizard over the CLI (not MCP).
Rank demonstrated architectural problems from one canonical run plus targeted source verification. Read-only; priorities are response-local heuristics, never CodeClone findings.
Inspect structural blast radius before editing — dependents, clone cohort, risk signals, do-not-touch boundaries. Read-only; does not declare intent.
MANDATORY HARD GATE when CodeClone MCP is connected. Before ANY repository file write, obtain edit_allowed=true from start_controlled_change. Before claiming done/verified/ready, finish_controlled_change must accept and clear the intent.
Use CodeClone Engineering Memory through MCP to retrieve scoped evidence before edits and preserve durable incidents, decisions, risks, contradictions, and verification anchors as draft candidates. Memory never grants edit permission; agents propose, humans govern.
Before broad rg/grep, non-trivial planning, unclear scope, contract/schema work, or resuming another agent — call get_implementation_context once to bound the implementation frontier. Then use targeted source reads. Read-only; never grants edit permission.
| name | codeclone-hotspots |
| description | Fast CodeClone quality snapshot — health, top risks, or one metric, without a full review loop. |
Fast quality answer (health, worst hotspots, one metric) — not a full review session.
new/known is NOT patch-local proof — for "did my patch cause this?" use the change-control
before→after verify path.analyze_repository(root=<abs>) → get_production_triage
Cheapest useful path. Stop there unless asked for more.
analyze_repository → check_complexity | check_coupling | check_cohesion | check_dead_code | check_clonesget_report_section(section="metrics") (coverage unclear →
help(topic="coverage"))evaluate_gates(run_id, fail_on_new=, fail_complexity=, …) → for the actual findings,
list_findings(novelty="new", family=…, source_kind="production").Key / easily-misread fields; the real response carries more.
| Field | Meaning |
|---|---|
health.score/grade | 0–100 / A–F; dimensions = per-family |
findings.new/known | baseline-relative — NOT patch-local proof |
new_by_source_kind | new split prod / tests / fixtures (the gate counts production) |
evaluate_gates.would_fail + reasons[] | gate verdict + cause tokens |
check item novelty / clone_type / scope | new vs known / Type-1..4 / production vs tests |
root. No latest run → analyze_repository first.detail_level for lists: summary | normal | full.codeclone-review for a real session.