Agent skill · software engineering · alirezarezvani
zero-hallucination-coder
Use before high-stakes or multi-file coding (auth, databases, migrations), or when asked to plan carefully and avoid invented APIs. Runs discuss, map, decompose, execute and verify, checking every import and API exists. Not for trivial edits.
Why this skill is useful
Adds a structured five-phase coding loop that prevents hallucinated code and ensures rigorous planning and execution, which the AI cannot generate on its own.
What it needs
About 8k tokens when loaded. Last updated 2026-08-05. 23,939 stars on the source repository.
What this skill does
Zero-Hallucination Coder A disciplined, senior engineering partner. The goal is code that is correct, grounded, and complete — with zero invented APIs, zero skipped steps, and zero hallucinated behavior. When to invoke (opt-in discipline) This is a deliberate, opt-in pipeline, not the default for every edit. Reach for it when: The task is high-stakes or hard to undo (migrations, schema/auth changes, deployments). It spans existing code across multiple files, or touches external APIs, auth, databases, or state. The user explicitly asks to "plan carefully," "avoid hallucinated code," or "do this rigorously." For a typo, a reformat, a docstring, or a throwaway script, skip the loop — the ceremony costs more than it saves. Anti-hallucination Rules 1-7 (below) still apply everywhere, but the five-phase loop is reserved for work that earns it. Credits & Inspiration This skill is a synthesis of four open-source projects. Their ideas power every phase of the loop below. Project Author What It Contributes --------- -------- --------------------- Ralph @snarktank PRD-driven atomic coding loop — implement one story at a time in fresh context, commit only when quality checks pass GSD Core @open-gsd Context-engineering discipline — Discuss → Plan → Execute → Verify → Ship phase loop, structured memory files, preventing context rot Graphify @safishamsi Knowledge-graph codebase reasoning — explicit KNOWN/INFERRED/UNKNOWN relationship tagging, grounded in real structure not guesses Ponytail @DietrichGebert Lazy senior dev hierarchy — before writing any code, check if it needs to exist at all, producing 80–94% less code Each project also ships its own native tooling (autonomous runners, AST graph builders, lifecycle hooks). This skill bakes their discipline into one loop; install the originals separately only if you want their standalone tooling. --- Before Starting Check for context first: If project-context.md exists in the workspace, read it before asking questions. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills alirezarezvani/zero-hallucination-coder--1d3903