Stats
Actions
Tags
From audit-fleet
This skill should be used when an audit-fleet lane is producing or validating report format and must enforce deterministic sections plus exact finding keys.
How this skill is triggered — by the user, by Claude, or both
Slash command
/audit-fleet:audit-fleet-output-contractThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use one canonical structure so lane outputs can be merged without manual rework.
Use one canonical structure so lane outputs can be merged without manual rework.
All audit-fleet outputs must preserve this exact section order:
All Findings entries must include these keys exactly:
Severity enum is strict: critical | warning | info.
Use a markdown table with this exact column order:
| finding_id | severity | dimension | evidence | impact | recommendation | effort | owner | dependencies | confidence | acceptance_criteria |
|---|
npx claudepluginhub nsalvacao/nsalvacao-claude-code-plugins --plugin audit-fleetFormats final review deliverables into consistent structures like review reports, PR descriptions, release notes, and incident reports for stakeholder presentation.
Generates professional audit findings in Condition-Criteria-Cause-Effect (CCCE) format with severity levels, management letter comments, remediation recommendations, and risk assessments.
Defines the JSON output format for plan review agents, including schema, severity emojis, and finding body structure.