From imbue-code-guardian
Enables architecture verification gate in .reviewer/settings.local.json by merging jq update setting 'verify_architecture.is_enabled' to true and confirming change.
How this skill is triggered — by the user, by Claude, or both
Slash command
/imbue-code-guardian:reviewer-verify-architecture-enableThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Run this command:
Run this command:
jq -n --argjson existing "$(cat .reviewer/settings.local.json 2>/dev/null || echo '{}')" '$existing * {"verify_architecture": {"is_enabled": true}}' > .reviewer/settings.local.json.tmp && mv .reviewer/settings.local.json.tmp .reviewer/settings.local.json
Then confirm that the architecture verification gate has been enabled.
npx claudepluginhub imbue-ai/code-guardian --plugin imbue-code-guardianRun a read-only verification pass after implementation to check whether completion claims are real, validation actually ran, and obvious edge cases or regressions were missed.
Verifies 8 enhancability gates before commit or release: feature-flag adoption, config externalization, semver-versioned APIs, forward-compat headers, extension-point definition, startup config validation, ambiguity detection, and fan-out discipline.
Runs typecheck, test, and lint gates to verify a diff is review-ready before human review. Also captures UI screenshots for visual proof.