Quality Scan
diegosouzapw/OmniRoute
Runs a scoped, read-only quality scan on a repository candidate and reports exact evidence, failures and frozen debt, without treating a static scan as release acceptance.
A skill your agent uses when running claudikins-kernel:verify, checking implementation quality, deciding pass/fail verdicts, or enforcing cross-command gates — requires actual evidence of code…
$ npx skills add povvo/claudikins-kernel --skill strict-enforcement -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install povvo/claudikins-kernel strict-enforcement --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/povvo/claudikins-kernel.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/strict-enforcement .claude/skills/strict-enforcement && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "strict-enforcement" agent skill from https://github.com/povvo/claudikins-kernel/tree/main/skills/strict-enforcement into .claude/skills/strict-enforcement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "strict-enforcement", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/povvo/claudikins-kernel/tree/main/skills/strict-enforcementType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add povvo/claudikins-kernel --skill strict-enforcement -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install povvo/claudikins-kernel strict-enforcement --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/povvo/claudikins-kernel.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/strict-enforcement .agents/skills/strict-enforcement && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "strict-enforcement" agent skill from https://github.com/povvo/claudikins-kernel/tree/main/skills/strict-enforcement into .agents/skills/strict-enforcement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "strict-enforcement", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add povvo/claudikins-kernel --skill strict-enforcement -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install povvo/claudikins-kernel strict-enforcement --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/povvo/claudikins-kernel.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/strict-enforcement .cursor/skills/strict-enforcement && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "strict-enforcement" agent skill from https://github.com/povvo/claudikins-kernel/tree/main/skills/strict-enforcement into .cursor/skills/strict-enforcement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "strict-enforcement", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/povvo/claudikins-kernel.git --path skills/strict-enforcement--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add povvo/claudikins-kernel --skill strict-enforcement -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install povvo/claudikins-kernel strict-enforcement --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/povvo/claudikins-kernel.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/strict-enforcement .gemini/skills/strict-enforcement && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "strict-enforcement" agent skill from https://github.com/povvo/claudikins-kernel/tree/main/skills/strict-enforcement into .gemini/skills/strict-enforcement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "strict-enforcement", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install povvo/claudikins-kernel strict-enforcementInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add povvo/claudikins-kernel --skill strict-enforcement -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/povvo/claudikins-kernel.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/strict-enforcement .github/skills/strict-enforcement && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "strict-enforcement" agent skill from https://github.com/povvo/claudikins-kernel/tree/main/skills/strict-enforcement into .github/skills/strict-enforcement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "strict-enforcement", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add povvo/claudikins-kernel --skill strict-enforcement -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install povvo/claudikins-kernel strict-enforcement --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/povvo/claudikins-kernel.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/strict-enforcement .opencode/skills/strict-enforcement && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "strict-enforcement" agent skill from https://github.com/povvo/claudikins-kernel/tree/main/skills/strict-enforcement into .opencode/skills/strict-enforcement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "strict-enforcement", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
strict-enforcementA skill your agent uses when running claudikins-kernel:verify, checking implementation quality, deciding pass/fail verdicts, or enforcing cross-command gates — requires actual evidence of code…
Strict Enforcement is an agent skill from povvo/claudikins-kernel. Use when running claudikins-kernel:verify, checking implementation quality, deciding pass/fail verdicts, or enforcing cross-command gates — requires actual evidence of code working, not just passing tests
Its SKILL.md is about 2.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 11 other files, including reference files (for example `references/advanced-verification.md`, `references/agent-integration.md` and `references/cynic-rollback.md`).
It sits in Testing & QA. It works with npm. The repository describes itself as: SRE thinking applied to Claude Code, based on Boris Cherny's Q&A. It enforces a strict 4-stage pipeline with gates between each step. You literally cannot skip verification. You… The licence is MIT.
5 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 8b626a4. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
ReadGrepGlobBashWebFetchSkillmcp__plugin_claudikins-tool-executor_tool-executor__search_toolsmcp__plugin_claudikins-tool-executor_tool-executor__get_tool_schemamcp__plugin_claudikins-tool-executor_tool-executor__execute_codeFrom allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
npmcargojqFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Strict Enforcement loads about 2.7k tokens when it runs, and up to ~23k if it reads all its reference files. Until then it costs about 56 tokens; SKILL.md has 779 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
allowed-tools: Read, Grep, Glob, Bash, WebFetch, Skill, mcp__plugin_claudikins-tool-executor_tool-executor__search_Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from povvo/claudikins-kernel at commit 8b626a4, republished under its MIT licence (© povvo). 779 words, ~2,725 tokens.
.claude/skills/strict-enforcement/SKILL.md (or your agent's skills folder). This skill also uses 10 other files; get the full folder from GitHub.Use this skill when you need to:
claudikins-kernel:verify command"Evidence before assertions. Always." - Verification philosophy
Never claim code works without seeing it work. Tests passing is not enough. Claude must SEE the output.
Run the automated checks first. Fast feedback.
| Check | Command Pattern | What It Catches |
|---|---|---|
| Tests | npm test / pytest / cargo test | Logic errors, regressions |
| Lint | npm run lint / ruff / clippy | Style issues, common bugs |
| Types | tsc / mypy / cargo check | Type mismatches, interface drift |
| Build | npm run build / cargo build | Compilation errors, bundling issues |
Flaky Test Detection (C-12):
Test fails?
├── Re-run failed tests
├── Pass 2nd time?
│ └── Yes → STOP: [Accept flakiness] [Fix tests] [Abort]
└── Fail 2nd time?
├── Run isolated
└── Still fail? → STOP: [Fix] [Skip] [Abort]This is the feedback loop that makes Claude's code actually work.
| Project Type | Verification Method | Evidence |
|---|---|---|
| Web app | Start server, screenshot, test flows | Screenshots, console logs |
| API | Curl endpoints, check responses | Status codes, response bodies |
| CLI | Run commands, capture output | stdout, stderr, exit codes |
| Library | Run examples, check results | Output values, test coverage |
| Service | Check logs, verify health endpoint | Log patterns, health responses |
Fallback Hierarchy (A-3):
If primary method unavailable, fall back:
Timeout: 30 seconds per verification method (CMD-30).
After verification passes, optionally run cynic for polish.
Prerequisites:
cynic Rules:
If tests fail after simplification:
See cynic-rollback.md for recovery patterns.
If stuck during verification:
Is mcp__claudikins-klaus available? (E-16)
├── No →
│ Offer: [Manual review] [Ask Claude differently] (E-17)
│ Fallback: [Accept with uncertainty] [Max retries, abort] (E-18)
└── Yes →
Spawn klaus via SubagentStop hookThe final gate. Present comprehensive evidence.
Verification Report
-------------------
Tests: ✓ 47/47 passed
Lint: ✓ 0 issues
Types: ✓ 0 errors
Build: ✓ success
Evidence:
- Screenshot: .claude/evidence/login-flow.png
- API test: POST /api/auth → 200 OK
- CLI test: mycli --help → exit 0
[Ready to Ship] [Needs Work] [Accept with Caveats]Human decides. If approved, set unlock_ship = true.
Agents under pressure find excuses. These are all violations:
| Excuse | Reality |
|---|---|
| "Tests pass, that's good enough" | Tests aren't enough. SEE it working. Screenshots, curl, output. |
| "I'll verify after shipping" | Verify BEFORE ship. That's the whole point. |
| "The type checker caught everything" | Types don't catch runtime issues. Get evidence. |
| "Screenshot failed but it probably works" | "Probably" isn't evidence. Fix the screenshot or use fallback. |
| "Human checkpoint is just a formality" | Human checkpoint is the gate. No auto-shipping. |
| "Code review is enough for this change" | Code review is last resort fallback. Try harder. |
| "Tests are flaky, I'll ignore the failure" | Flaky tests hide real failures. Fix or explicitly accept with caveat. |
| "Exit code 2 is too strict" | Exit code 2 exists to block bad ships. Pass properly. |
All of these mean: Get evidence. Human decides. No shortcuts.
If you're thinking any of these, you're about to violate the methodology:
All of these mean: STOP. Get evidence. Present to human. Let them decide.
The verify-gate.sh hook enforces the gate:
# Both conditions MUST be true
ALL_PASSED=$(jq -r '.all_checks_passed' "$STATE")
HUMAN_APPROVED=$(jq -r '.human_checkpoint.decision' "$STATE")
if [ "$ALL_PASSED" != "true" ]; then
exit 2 # Blocks claudikins-kernel:ship
fi
if [ "$HUMAN_APPROVED" != "ready_to_ship" ]; then
exit 2 # Blocks claudikins-kernel:ship
fiFile Manifest (C-6):
At verification completion, generate SHA256 hashes of all source files:
find . \( -name '*.ts' -o -name '*.py' -o -name '*.rs' \) \
| xargs sha256sum > .claude/verify-manifest.txtThis lets claudikins-kernel:ship detect if code was modified after verification.
claudikins-kernel:verify requires claudikins-kernel:execute to have completed:
if [ ! -f "$EXECUTE_STATE" ]; then
echo "ERROR: claudikins-kernel:execute has not been run"
exit 2
fiThis enforces the claudikins-kernel:outline → claudikins-kernel:execute → claudikins-kernel:verify → claudikins-kernel:ship flow.
| Agent | Role | When |
|---|---|---|
| catastrophiser | See code working | Phase 2: Output verification |
| cynic | Polish pass | Phase 3: Simplification (optional) |
Both agents run with context: fork and background: true.
See agent-integration.md for coordination patterns.
{
"session_id": "verify-2026-01-16-1100",
"execute_session_id": "execute-2026-01-16-1030",
"branch": "execute/task-1-auth-middleware",
"phases": {
"test_suite": { "status": "PASS", "count": 47 },
"lint": { "status": "PASS", "issues": 0 },
"type_check": { "status": "PASS", "errors": 0 },
"output_verification": { "status": "PASS", "agent": "catastrophiser" },
"code_simplification": { "status": "PASS", "agent": "cynic" }
},
"all_checks_passed": true,
"human_checkpoint": {
"decision": "ready_to_ship",
"caveats": []
},
"unlock_ship": true,
"verified_manifest": "sha256:...",
"verified_commit_sha": "abc123..."
}Don't do these:
| Situation | Reference |
|---|---|
| Tests hang or timeout | test-timeout-handling.md |
| Auto-fix breaks code | lint-fix-validation.md |
| Primary verification fails | verification-method-fallback.md |
| Type-check results unclear | type-check-confidence.md |
| cynic breaks tests | cynic-rollback.md |
| Large project state | verify-state-compression.md |
Full documentation in this skill's references/ folder:
© povvo, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 10 other files (references) in skills/strict-enforcement of povvo/claudikins-kernel.
Open the folder on GitHubat commit 8b626a4
Strict Enforcement next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Strict Enforcement this skillpovvo/claudikins-kernel | 128 | — | ~2.7k | Automated safety check: Notes | MIT | |
| Quality Scandiegosouzapw/OmniRoute | 75k | — | ~748 | Automated safety check: Pass | MIT | |
| Testingwellwelwel/poku | 1.2k | — | ~1k | Automated safety check: Pass | MIT | |
| Actions CI Tuningmizchi/skills | 360 | — | ~2.6k | Automated safety check: Pass | None | |
| CI Triageandymai/brepjs | 115 | — | ~3.8k | Automated safety check: Pass | Apache-2.0 | |
| OpenHarness End-to-End EvalsHKUDS/OpenHarness | 16k | 1 repos | ~2.1k | Automated safety check: Notes | MIT |
diegosouzapw/OmniRoute
Runs a scoped, read-only quality scan on a repository candidate and reports exact evidence, failures and frozen debt, without treating a static scan as release acceptance.
wellwelwel/poku
Testing deep-dive for poku covering test structure, commands, patterns, fixtures, utils, Docker compatibility, and coverage.
mizchi/skills
A skill your agent uses when auditing or improving GitHub Actions workflows for a project.
andymai/brepjs
This skill should be used when a brepjs GitHub Actions job is red or behaving oddly on github.com (a remote CI run, not a local pre-commit/pre-push hook) — "CI failed", "ci-pass is failing", "npm ci…
HKUDS/OpenHarness
Validates OpenHarness features by running real multi-turn agent loops with live LLM calls against an unfamiliar codebase, checking actual tool execution.
QwenLM/qwen-code
Guides end-to-end testing of the Qwen Code CLI in headless mode with real model calls, MCP test servers and inspection of raw API traffic.
povvo/claudikins-kernel
A skill your agent uses when running claudikins-kernel:outline, brainstorming implementation approaches, gathering requirements iteratively, structuring complex technical plans, or facing analysis…
povvo/claudikins-kernel
A skill your agent uses when running claudikins-kernel:execute, decomposing plans into tasks, setting up two-stage review, deciding batch sizes, or handling stuck agents — enforces isolation…
povvo/claudikins-kernel
A skill your agent uses when running claudikins-kernel:ship, preparing PRs, writing changelogs, deciding merge strategy, or handling CI failures — enforces GRFP-style iterative approval, code…
Works with
Categories
A skill your agent uses when running claudikins-kernel:verify, checking implementation quality, deciding pass/fail verdicts, or enforcing cross-command gates — requires actual evidence of code…. Strict Enforcement is an agent skill from povvo/claudikins-kernel.
Strict Enforcement fits situations like: running claudikins-kernel:verify; checking implementation quality; deciding pass/fail verdicts; enforcing cross-command gates — requires actual evidence of code working.
Run `npx skills add povvo/claudikins-kernel --skill strict-enforcement -a claude-code`. Or copy the skill folder (skills/strict-enforcement in povvo/claudikins-kernel) into .claude/skills/strict-enforcement in your project. Claude Code loads it when a task matches its description.
Run `npx skills add povvo/claudikins-kernel --skill strict-enforcement -a codex`. Or copy the skill folder (skills/strict-enforcement in povvo/claudikins-kernel) into .agents/skills/strict-enforcement in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add povvo/claudikins-kernel --skill strict-enforcement -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/strict-enforcement, .gemini/skills/strict-enforcement, .github/skills/strict-enforcement and .opencode/skills/strict-enforcement in your project.
Going by SKILL.md and its folder, Strict Enforcement needs the command-line tools its instructions call (npm, cargo and jq). Its frontmatter pre-approves these tools: Read, Grep, Glob, Bash, WebFetch, Skill, mcp__plugin_claudikins-tool-executor_tool-executor__search_tools, mcp__plugin_claudikins-tool-executor_tool-executor__get_tool_schema, mcp__plugin_claudikins-tool-executor_tool-executor__execute_code.
SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
Strict Enforcement is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.7k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 20k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Strict Enforcement: Quality Scan (diegosouzapw/OmniRoute, 75k stars), Testing (wellwelwel/poku, 1.2k stars), Actions CI Tuning (mizchi/skills, 360 stars) and CI Triage (andymai/brepjs, 115 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
povvo (a GitHub user) maintains it in povvo/claudikins-kernel, which has 128 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on April 22, 2026.
Source: povvo/claudikins-kernel on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.