MarioEpkOne

Audit Implementation — Security skill for Claude Code

Security community

POST-IMPLEMENTATION AUDIT — analyzes what the implementing agent did wrong and why, proposes specific changes to CLAUDE.md / impl.md / impl-plan.md for approval, and appends new patterns to learnings.

How to install Audit Implementation

Installs to ~/.claude/skills/marioepkone-pipelineiq-audit-implementation/SKILL.md

Terminal
mkdir -p ~/.claude/skills/marioepkone-pipelineiq-audit-implementation && curl -fsSL https://raw.githubusercontent.com/MarioEpkOne/PipelineIQ/HEAD/commands/audit-implementation.md -o ~/.claude/skills/marioepkone-pipelineiq-audit-implementation/SKILL.md

Restart Claude Code, or start a new session, for it to be picked up.

What Audit Implementation does

POST-IMPLEMENTATION AUDIT — analyzes what the implementing agent did wrong and why, proposes specific changes to CLAUDE.md / impl.md / impl-plan.md for approval, and appends new patterns to learnings.md.

The user's request is: $ARGUMENTS

Purpose

This skill is a process autopsy, not a QA check. The goal is to understand *why* failures happened so the skills and rules can be improved for future implementations. Run this after every /impl. For auditing whether an implementation *plan* conform

Alternatives in Security

  • Memory Self Review — Mine recent agent history (claude-mem + usage stats) for recurring failures and repeated patterns, audit MEMOR 297 ★
  • Tool Approval Security Filter — You are a security filter for Claude Code tool execution 163 ★
  • Spec Check — Audit GWT acceptance test specs for implementation leakage 149 ★

Full documentation available on GitHub

View Source Repository