From camouf
Validate the current project for AI-generated code mistakes: function name drift, phantom imports, field mismatches, contract violations, and architectural issues. Use this skill BEFORE committing code, after generating new files, or when you suspect cross-file inconsistencies. Invokes `camouf_validate` via MCP.
How this skill is triggered — by the user, by Claude, or both
Slash command
/camouf:validateThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You have access to the `camouf_validate` MCP tool. Use it to scan the current project
You have access to the camouf_validate MCP tool. Use it to scan the current project
for architecture violations and AI-generated code mistakes.
camouf_validate with no arguments to scan the full projectruleId: which rule detected the issue (e.g., function-signature-matching)severity: error, warning, or infofile and line: exact locationmessage: human-readable explanationsuggestion: how to fix itgetUser() but the canonical function is getUserById()")| Rule ID | What it catches |
|---|---|
function-signature-matching | Function renamed by AI (e.g., getUser vs getUserById) |
contract-mismatch | API call doesn't match OpenAPI/GraphQL schema |
ai-hallucinated-imports | Import from a file or module that doesn't exist |
phantom-type-references | Using a type that was never defined |
inconsistent-casing | Mixed camelCase / snake_case in the same project |
orphaned-functions | Functions defined but never called |
circular-dependencies | Circular import chains |
layer-dependencies | Frontend importing from backend, etc. |
If camouf returns:
function-signature-matching ERROR in client/user.ts:42
Called: getUser(userId)
Defined: getUserById(id) in shared/api.ts:15
Similarity: 75%
Explain: "You're calling getUser(userId) but the actual exported function is getUserById(id). This is a common AI context-loss error — the AI generated a plausible but incorrect function name. Fix: rename getUser to getUserById."
npx claudepluginhub theemilz/camouf-claude-pluginReviews code against project rules and reference files, flagging violations in correctness, security, reliability, architecture, dead code, complexity, and conventions.
Validates architectural layer boundaries and detects dependency violations using configurable constraint rules. Provides hard enforcement for pull request approval and refactoring.