ariffazil/arifos/postcheck-verifier
Claude Code and agent skill by ariffazil/arifos
- community
Checking that the SKILL.md file is still in the repository.
Proves actions worked in reality — not just exit code 0, not just logs — by validating actual observable outcomes in the system
Install
npx vskill@latest install ariffazil/arifos/postcheck-verifierSKILL.md
postcheck-verifier
P0 — Reality-Proven Outcome Verification Seal: DITEMPA BUKAN DIBERI · 2026-03-27
Purpose
Every agent reports success too easily. exit code 0 means the command ran, not that the goal was achieved. The postcheck-verifier exists because:
"The map is not the territory. The exit code is not the outcome."
The opencode catastrophe is a textbook example: every git command returned success, every merge reported completion, and the final state was catastrophic destruction. Success was assumed from the command's return code, not from the system's actual state.
Why this is P0: Closing this gap adds an estimated +20% to AGI readiness (the single largest jump in the P0 set). postcheck-verifier is what separates a tool-using automaton from an AGI agent.
The Verification Hierarchy
Not all verification is equal. Use the right level:
| Level | What It Proves | Example | |
|---|---|---|---|
| L0 — Exit Code | Command ran | grep found something | |
| L1 — Output Check | Output matches expectation | docker ps shows running container | |
| L2 — State Probe | System state changed as intended | HTTP endpoint responds correctly | |
| L3 — Functional Test | The feature actually works | User can log in, API returns correct data | |
| L4 — Reality Proof | The change achieved the goal in the real world | The system does what Arif asked |
Minimum standard for arifOS: L2 for routine ops. L3 for code changes. L4 for sovereign decisions.
Verification Protocol
After Every Action — Run This
L3 — Functional Test Template
L4 — Reality Proof (The Gold Standard)
Verification Matrix by Action Type
| Action Type | Minimum L | Required Check | Rollback If | |
|---|---|---|---|---|
git push / git merge | L2 | git fetch && git log origin/main shows commits | Yes | |
docker start/restart | L2 | docker ps shows running + health endpoint responds | Yes | |
docker compose up -d | L3 | All critical services respond to health probe | Yes | |
pip install / uv add | L2 | python -c "import pkg" succeeds | Yes | |
| Code change | L3 | pytest passes (or equivalent functional test) | Yes | |
| File edit / write | L1 | File exists + content check | Yes | |
| Service restart | L2 | Service responds + logs show clean start | Yes | |
| Production config change | L4 | Real-world behavior matches expectation | Yes | |
| Irreversible (migration, delete) | L4 | Full reality proof + Arif veto | Always ask first |
What "Verified" Means in arifOS
| Claim | Reality | |
|---|---|---|
| "Git push succeeded" | ✅ Remote has the commits. Check with git fetch && git log origin/main | |
| "Container is running" | ✅ docker ps shows it AND the health endpoint responds | |
| "Server started" | ✅ curl localhost:PORT/health returns 200 | |
| "Database migrated" | ✅ New schema query returns expected rows AND app queries work | |
| "Config deployed" | ✅ Running process shows new config values, not old ones | |
| "Test passed" | ✅ pytest exit 0 AND test count increased OR specific tests pass |
What "verified" does NOT mean:
exit code 0alonegrepfound the string in a log- A file was created
- A command printed "success"
Anti-Patterns This Closes
- Exit code theater — "it returned 0 so it worked" (the opencode disease)
- Log theater — "the log says it started" but the service died 5 seconds later
- Creation verification — a file existing doesn't mean its contents are correct
- Single-point verification — checked only one indicator when the system has multiple dependencies
- No rollback plan — verified success but had no way to undo if the verification was wrong
Constitutional Alignment
| Floor | How Enforced | |
|---|---|---|
| F1 Amanah | Reversibility path checked before verification; rollback ready | |
| F2 Truth ≥0.99 | L4 reality proof required for sovereign claims; no assumption | |
| F4 ΔS ≤0 | Verification output is precise, no ambiguity in results | |
| F7 Humility [0.03–0.05] | Uncertainty declared when verification is L2 only (not L4) |
postcheck-verifier — Forged 2026-03-27 · DITEMPA BUKAN DIBERI · Reality Over Assumption 🔐
Security
- Security scanPassed, 100 of 100Pattern checks on the skill's files.
- Model reviewNot runA model review is scheduled for the next rescan.
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/postcheck-verifier/SKILL.md
Popularity
- Repository stars
- 51
- Repository forks
- 9
- 7-day trend score
- 20
Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/ariffazil/arifos/postcheck-verifier)