Install
$ agentstack add skill-doctormozg-claude-pipelines-audit ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
Autonomous Problem-Locator Pipeline (report-only)
Overview
Orchestrates a multi-lens codebase audit and produces a ranked findings report. Two depth modes:
depth:standard(default) — single-wave parallel researchers across correctness, security, performance, maintainability, and reliability lenses. Quick scan suitable for in-progress work or focused bug hunts. Cap mode:quickpershared/severity-lattice.md.depth:deep— pre-PR multi-wave audit with blast-radius tier gating, evidence-tiered severity caps, trust-boundary STRIDE delta, three blinded adversarial lenses, rollback rehearsal (BLOCKING for missing down-migrations), cognitive-load budget, and persistent ledger append. Cap mode:pre-PR.
No code is modified in either mode. Hand the summary to build, debug, or polish to act on it.
When to Use
- User asks to audit, find bugs, or review the codebase for issues.
- Triggers (standard): "audit", "find bugs", "security review", "check for issues", "code quality scan".
- Triggers (deep): "deep audit", "pre-PR audit", "ship audit", "audit before publishing", "before I open a PR".
- Scope spans multiple files / multiple concern categories.
When NOT to use
- A single known bug — use
debug. - Building new functionality — use
build. - Map-reduce cleanup with no bug hunt — use
cleanup. - You want the findings fixed automatically — this skill does not edit code; pass the summary to
build,debug, orpolishafterwards.
Input
$ARGUMENTS— Optionaldepth:modifier (defaultstandard), scope hint (scope:branch), lens hint ("security review"), or combination. If ambiguous, ask. Never guess.
Scope Parameter
See [skills/shared/scope-parameter.md](../shared/scope-parameter.md) for the canonical scope modes (branch, global, working) and their git commands.
scope:controls files, remaining argument text controls lenses (orthogonal).- Default:
depth:standard→ path-like tokens → scope, no path tokens → roam.depth:deep→ default scopebranch. globalmode additionally excludes test files in this skill.- Bounded scopes (
branch,working, path-list) auto-invokeshared/blast-radius.mdto expand the inspection set with downstream-impacted files.globalskips the auto-invocation.
Core Principles
- Research only. This skill is read-only — it finds and reports, it does not fix.
- Parallel lenses, consolidated output. Diverse lenses find different bug classes; one merged report is the final artifact.
- Severity lattice is shared. Both depth modes produce findings on the same 6-level lattice (
shared/severity-lattice.md) so reports compare cleanly.
Constants
- MAXRESEARCHERS: 5 (standard) | MAXRESEARCHERSWAVEA: 6 (deep) | MAXRESEARCHERSWAVE_B: 3 (deep)
- Severity caps: resolved per
shared/severity-lattice.md—quickmode for standard,pre-PRmode for deep. - TASKDIR:
.mz/task/| LEDGERPATH:.mz/reports/audit_ledger.md(deep mode only) - HOTSPOTLOOKBACKDAYS: 90 (deep mode only — git log lookback for hotspot table; falls back to all-history on shallow clones)
Core Process
Phase Overview
depth:standard (default)
| # | Phase | Reference | Loop? | | --- | ---------------------- | ------------------------ | ----- | | 0 | Setup | inline below | — | | 1 | Scope & Lens Selection | phases/research.md | — | | 2 | Multi-Lens Research | phases/research.md | — | | 3 | Consolidate & Rank | phases/research.md | — | | 4 | Final Report | phases/final_report.md | — |
depth:deep
| # | Phase | Reference | Loop? | | --- | --------------------------------------------------- | ------------------------------- | ----- | | 0 | Setup (+ tooling detect + git hotspots) | inline below | — | | 1 | Scope Intelligence Gate (T0–T3 tiering) | phases/scope_and_tier_deep.md | — | | 2 | Multi-Lens Research (Wave A + Wave B) | phases/research_deep.md | — | | 3 | Consolidate, Evidence-Cap, Rollback, Cognitive-Load | phases/consolidate_deep.md | — | | 4 | Final Report + Ledger Update | phases/final_report_deep.md | — |
Phase 0: Setup
Derive _audit_ (or _deep_audit_ when depth:deep). Apply the resume-check contract in [skills/shared/resume-protocol.md](../shared/resume-protocol.md): if .mz/task//state.md exists with Status: running | failed, present the Resume gate and re-enter per recorded Phase. Otherwise create .mz/task// and write state.md per [skills/shared/state-schema.md](../shared/state-schema.md) — first line MUST be schema_version: 2, followed by Status, Phase, Started, Iteration (review iterations), FilesWritten, and the progress-ledger keys phase_complete: false and what_remains: [], plus skill-specific keys (depth: standard|deep). TaskCreate per phase.
When depth:deep: additionally dispatch pipeline-tooling-detector to detect test/lint commands for informational purposes (no tests are run); write to .mz/task//tooling.md. Phase 1 also computes git hotspot scores (commit counts over the last HOTSPOT_LOOKBACK_DAYS days, bot commits filtered) and records them in scope.md.
Phases 1–4
Route by depth: to the phase files in the table above. Both depth modes stop at the report — neither modifies code. The blinded invariant in depth:deep Phase 2 (Wave B dispatched in a SEPARATE message after Wave A completes) is non-negotiable.
Techniques
Techniques: delegated to phase files — see Phase Overview table above. Reference files: grep references/owasp-top-10-checklist.md for specific OWASP categories — do not load the entire file.
Common Rationalizations
| Rationalization | Rebuttal | | ------------------------------------- | ---------------------------------------------------------------------- | | "severity is subjective, label later" | "unlabeled audits get ignored" | | "one-pass scan is enough" | "multi-lens is the point of an audit; single-lens is a grep" | | "let me just fix this one thing" | "audit is report-only; fixing mid-run destroys the report's integrity" |
Red Flags
- You modified code. This skill does not edit files; if fixes are needed, hand off to
build,debug, orpolish. - Findings were not severity-labeled before writing
summary.md. - A single-lens scan was declared "audit complete".
Verification
Output the final summary.md block: finding counts by severity, files touched (scanned, not modified), lenses run, path to findings.md for the full detail.
Error Handling
- Ambiguous argument: ask before Phase 1. Empty scope / zero findings: report and exit.
- Researcher fails: continue with remaining lenses, flag in the report.
- Write conflict on findings.md: retry once, then escalate.
State Management
Update state.md after each phase with current phase, files scanned, escalation notes. Allows resumption if interrupted.
Maintain the progress ledger on every phase transition: set phase_complete: false on entering a phase and true only once its artifacts are written and its gates pass; refresh what_remains (outstanding work as plain strings) — it MUST be [] when Status: complete. Stamp last_verified whenever a verification gate passes clean. Reading a schema_version: 1 or unversioned state.md upgrades it in place: add the ledger keys, set schema_version: 2, and log the upgrade.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: DoctorMozg
- Source: DoctorMozg/claude-pipelines
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.