Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From cortexloop
Snapshots current findings as accepted debt or diffs against a baseline so CI gates only on new Critical/High issues. Supports accept and diff subcommands.
How this command is triggered — by the user, by Claude, or both
Slash command
/cortexloop:cortexloop-baselineThe summary Claude sees in its command listing — used to decide when to auto-load this command
# /cortexloop-baseline Manage **technical debt baseline** so CodeCortexLoop only fails on **new** findings in CI. ## When to use - **First time on a legacy repo** — too many existing issues? Run accept to snapshot current debt. - **Every PR after that** — run diff; CI gates only on **new** Critical/High findings. ## Flow ### 1. Run analysis first Run `/cortexloop` or `/cortexloop-pre-pr` in **Report** or **CI** mode to produce `docs/cortexloop/report.json`. ### 2. Choose action Ask the user: - **Accept baseline** — snapshot all current open findings as accepted debt - **Diff agains...
Manage technical debt baseline so CodeCortexLoop only fails on new findings in CI.
Run /cortexloop or /cortexloop-pre-pr in Report or CI mode to produce docs/cortexloop/report.json.
Ask the user:
From project root:
Accept (first time):
node scripts/baseline.mjs accept docs/cortexloop/report.json
Diff (subsequent runs):
node scripts/baseline.mjs diff docs/cortexloop/report.json
Outputs:
.cortexloop/baseline.json — accepted fingerprints.cortexloop/baseline-diff.json — new / fixed / remainingnode scripts/baseline.mjs diff docs/cortexloop/report.json
node scripts/ci-gate.mjs docs/cortexloop/report.json --baseline
Only new Critical/High findings fail the gate. Remaining baseline debt is ignored.
Load rules/baseline-policy.mdc for fingerprint semantics and ratchet behavior.
After diff, summarize for the user:
| Bucket | Meaning |
|---|---|
| new | Introduced since baseline — must fix or update baseline |
| fixed | Was in baseline, no longer present — progress! |
| remaining | Still open from baseline — tracked debt |
npx claudepluginhub whitequeen306/code-cortex-loop --plugin cortexloop/bug-analysisRuns proactive bug analysis on the current branch using static analysis tools and semantic analyzers, then synthesizes results into an actionable bug report with incremental analysis support.
/pr-review-fix-loopRuns iterative PR review and autofix loop: reviews code, fixes issues above criticality threshold with auto-detected test/lint commands, repeats until clean. Supports Ruby, Node, Python, Go, Rust.
/drift-scanRuns drift sensors across the codebase to detect dead code, large files, stale todos, outdated deps, doc-code mismatch, and missing test files. Supports --only, --threshold-lines, --format flags.
/resolveValidates code review issues, classifies them as FIX or TECH_DEBT by risk, and implements fixes for low-risk issues. Also supports multi-worktree auto-discovery.
/review-workflow-phases-1-4Runs phases 1-4 of PR/MR review workflow: establishes scope from artifacts and backlog, validates versions across files, detects slop, analyzes code, outputs review.
/extreme-code-quality-reviewPerforms an extremely strict maintainability audit of the current branch vs a base branch. Flags violations of code-judo, 1k-line rule, and spaghetti growth using a detailed rubric.