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 pr-audit-template
Given a ranked-findings list from waste-analyze, render a standardized PR follow-up body + N issue bodies (default 3) using a handlebars-style template. Each issue is actionable — names the wasteful pattern, quantifies impact, and suggests a concrete fix or workflow change.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pr-audit-template:pr-audit-bodyThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
- After waste-analyze produces ranked findings for a merged PR
SCAFFOLD ONLY — implementation lands in OAUDIT4.
# Audit follow-up: PR #<merged-pr>
**Session ID:** <session-uuid>
**Merged at:** <iso-timestamp>
**Total tool calls during PR work:** <count>
**Total wall-clock minutes:** <duration>
**Throughput:** <calls/min>
## Top <N> findings
[N rows from waste-analyze ranked output]
## Linked issues
- <#issue-1> — <finding-1 title>
- <#issue-2> — <finding-2 title>
- <#issue-3> — <finding-3 title>
## Next iteration
[Concrete proposal: workflow change / new skill / lint rule / etc.]
# <finding title>
**Source PR:** #<merged-pr>
**Pattern:** <heuristic name from waste-analyze>
**Impact score:** <score>
**Wasted tool calls:** <count>
**Wasted seconds:** <seconds>
## Evidence
[Specific call signatures + timestamps from transcript-parse]
## Proposed fix
[Concrete change — usually a hook, lint, or skill update]
plugins/platform-engineering/skills/citations-tests-outcomes/SKILL.mdnpx claudepluginhub subagentceo/knowledge-engineering --plugin pr-audit-templateGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.
Dispatches multiple subagents concurrently for independent tasks without shared state. Use when facing 2+ unrelated failures or subsystems that can be investigated in parallel.