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 Thesmos Governance
Analyse the repo's structure (routes, API auth gaps, large files, boundary risks) into .thesmos/report.json — run before a review on a repo that hasn't been scanned yet, or when the report looks stale.
How this skill is triggered — by the user, by Claude, or both
Slash command
/thesmos-governance:scanThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Run `npx thesmos-governance scan` in the project root via the Bash tool.
Run npx thesmos-governance scan in the project root via the Bash tool.
This writes .thesmos/report.json — a structural snapshot (pages, API routes,
large files, client/server boundary risks) that review/validate/ci and
the MCP server's repo-intelligence tools read from. It does not itself report
governance findings — for that, run the review skill after scanning.
Report back: whether the scan succeeded, and a one-line summary of what
.thesmos/report.json now contains (route count, large-file count, any
boundary risks flagged).
npx claudepluginhub holley-studio/thesmos-governance --plugin thesmos-governanceGuides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.
Forks private projects, strips secrets/internal references, verifies cleanliness, and packages them with CLAUDE.md, README, and setup.sh for safe public release.