enforcing-review-separation
Use when artifact, code, finding, provider, or release approval requires independent review across principal, role, team, or trust-domain boundaries.
Profile →npx skills add casioreview20-glitch/forge-os --skill enforcing-review-separation --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Enforcing Review Separation ## Core principle Resolve producer, resolver, evaluator, closer, and signer trust domains. Bind the authorized reviewer and evidence set to the reviewed subject. The runtime owns deterministic scope, coverage, policy, and evidence checks; the agent owns only the judgment that cannot be reduced safely to code. ## Do not activate when - A0 prototype policy explicitly pe
What does the enforcing-review-separation skill do?
Use when artifact, code, finding, provider, or release approval requires independent review across principal, role, team, or trust-domain boundaries.
How do I install it?
Run `npx skills add casioreview20-glitch/forge-os --skill enforcing-review-separation --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From casioreview20-glitch/forge-os, a repository with 11 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.