riqor-verification-gate
Skill4 starsChanged 3 months agoMITView on GitHub
Use when completing tasks, making changes, or claiming work is done in any codebase monitored by Riqor to enforce empirical verification before completion.
In this repository15 other files it gives its agents.
- .codex/AGENTS.mdAGENTS.md
- agency-application-security-engineerSkill
- agency-multi-agent-systems-architectSkill
- agency-performance-benchmarkerSkill
- agency-privacy-engineerSkill
- agency-secrets-credential-hygiene-engineerSkill
- agency-test-automation-engineerSkill
- agent-kernel-evolveSkill
- architecture-guardianSkill
- code-reviewSkill
- riqor-agent-orchestratorSkill
- riqor-code-intelligenceSkill
- riqor-session-continuitySkill
- riqor-conventionsSkill
- riqor-conventionsSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Never claim a task is resolved, fixed, or passing based on code edits alone.
- Very specific: line 17
If status is verification-pending, a workspace mutation was performed and MUST be verified before finishing.
- Very specific: line 20
Run relevant test suites: bun test, npm test, or specific test files.
- Very specific: line 21
Run type checking: tsc --noEmit or build scripts.
- Distinctive: line 22
Check status & logs: verify exit code 0.
- Distinctive: line 30
Only state completion after all verification steps exit cleanly with zero errors.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Riqor Verification Gate
Core Rule
Never claim a task is resolved, fixed, or passing based on code edits alone. Empirical runtime evidence is required before any completion claim.
Execution Flow
- Check Session Status:
If status isriqor terminal statusverification-pending, a workspace mutation was performed and MUST be verified before finishing. - Execute Targeted Verification:
- Run relevant test suites:
bun test,npm test, or specific test files. - Run type checking:
tsc --noEmitor build scripts. - Check status & logs: verify exit code 0.
- Run relevant test suites:
- Verify Health:
riqor doctor --json - Claim Completion: Only state completion after all verification steps exit cleanly with zero errors.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

