
from superclaude-plusplus13
Run project-specific verification rules that check business logic, architecture patterns, and naming conventions beyond linters.
This skill runs project-specific audit rules (markdown-based) that validate business logic, architecture patterns, and naming conventions which standard linters/test suites miss. It can collect relevant changed files, run scripted checks, AI-evaluate results against pass criteria, and produce a readable audit report with PASS/FAIL/WARN classifications.
Use this when you need an automated quality gate that enforces architectural decisions, naming conventions, or domain-specific checks during CI or code review, or to bootstrap rule sets for new projects. Invoke via /audit or /audit manage to run or manage rules.
references/ directory with examples and rule-format guidance..claude/audit-rules/*.md, execute checks, and report results.Best used with Claude Code / SuperClaude-style Claude Code frameworks and any agent that can execute shell scripts and parse markdown-based rules (Claude Code, SpoonOS-style agents).
Project-specific verification rules skill that runs custom audit checks beyond what linters catch. Well-structured with clear RUN/MANAGE modes, auto-exempt file patterns, and smart project-type detection for bootstrapping. No scripts bundled — relies on the agent interpreting markdown rule files. No security concerns; uses only standard git commands.
Clean skill with good structure. Tied to the SuperClaude/Claude Code ecosystem which limits portability. The audit rule concept is valuable and well-documented. Auto-detection of project type for bootstrapping is a nice touch.
Session Save / Context Persistence
Persist session context and create checkpoints: save learnings, summaries, and project state for cross-session continuity.
Project Manager (PM) Agent
An always-active orchestration agent that analyzes requests, auto-delegates to sub-agents, and runs PDCA-style project workflows across MCP tools.