Agent skill

Completion Gate

by NoobyGains in NoobyGains/godmode

A skill your agent uses when about to declare work done, fixed, or passing, before committing or opening PRs - demands executing verification commands and reading their output before making any…

MITAuto-check passed

Install Completion Gate

skills CLI
$ npx skills add NoobyGains/godmode --skill completion-gate -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install NoobyGains/godmode completion-gate --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/NoobyGains/godmode.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/completion-gate .claude/skills/completion-gate && rm -rf skills-src

Use ~/.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/

Facts

Skill name
completion-gate
GitHub stars
107
Token cost
~1.6k tokens
SKILL.md length
523 words
Files
1
Skills in repo
34
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when about to declare work done, fixed, or passing, before committing or opening PRs - demands executing verification commands and reading their output before making any…

  • About to declare work done
  • SKILL.md covers Overview, The Prime Directive, The Entry Protocol and Verification Requirements, plus 8 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Before committing

What it does

Completion Gate is an agent skill from NoobyGains/godmode. Use when about to declare work done, fixed, or passing, before committing or opening PRs - demands executing verification commands and reading their output before making any success assertions; evidence precedes claims always

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: The AI development framework that thinks before it builds. 36 composable skills for Claude Code, Cursor, Codex, and OpenCode. The licence is MIT.

When your agent uses it

  • About to declare work done
  • Before committing
  • Opening PRs - demands executing verification commands and reading their output before making any success assertions
  • Evidence precedes claims always

Example prompts

  • “/completion-gate”

What it can do on your machine

Read from SKILL.md and the folder at commit 441103a. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Completion Gate loads about 1.6k tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 523 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~60
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k

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.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

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.

SKILL.md

The full file from NoobyGains/godmode at commit 441103a, republished under its MIT licence (© NoobyGains). 523 words, ~1,600 tokens.

Download SKILL.mdSave it as .claude/skills/completion-gate/SKILL.md (or your agent's skills folder).
name
completion-gate
description
Use when about to declare work done, fixed, or passing, before committing or opening PRs - demands executing verification commands and reading their output before making any success assertions; evidence precedes claims always

Completion Gate

Overview

Declaring work complete without verification is dishonesty, not efficiency.

Core principle: Evidence precedes assertions, always.

No exceptions. No workarounds. No shortcuts.

The Prime Directive

NO COMPLETION ASSERTIONS WITHOUT FRESH VERIFICATION OUTPUT

If the verification command has not been executed in this message, you cannot assert it passes.

The Entry Protocol

BEFORE asserting any status or expressing confidence:

1. IDENTIFY: Which command substantiates this assertion?
2. EXECUTE: Run the FULL command (fresh, complete)
3. INSPECT: Read every line of output, check exit code, tally failures
4. CONFIRM: Does the output support the assertion?
   - If NO: Report actual status with evidence
   - If YES: State the assertion WITH supporting evidence
5. ONLY THEN: Make the assertion

Skipping any step = fabrication, not verification

Verification Requirements

AssertionDemandsInsufficient
Tests passTest runner output showing 0 failuresPrior run, "should pass"
Linter cleanLinter output showing 0 errorsPartial scan, extrapolation
Build succeedsBuild command with exit code 0Linter passing, log fragments
Bug resolvedOriginal symptom tested and passesCode modified, assumed fixed
Regression test validRed-green cycle confirmedSingle green pass
Agent finishedVCS diff showing actual changesAgent self-reported "done"
Specification metLine-by-line requirement checklistTests passing alone

Guardrails - HALT

  • Using hedging language: "should", "probably", "seems to"
  • Expressing premature satisfaction ("Done!", "Perfect!", "All good!")
  • About to commit/push/open PR without verification
  • Trusting an agent's self-reported success
  • Relying on partial or stale verification
  • Thinking "just this one time"
  • Fatigued and wanting to wrap up
  • ANY phrasing that implies success without having run verification

Cognitive Traps

RationalizationTruth
"Should work now"EXECUTE the verification
"I'm confident"Confidence is not evidence
"Just this once"No exceptions
"Linter passed"Linter is not the compiler
"Agent reported success"Verify independently
"I'm tired"Fatigue is not justification
"Partial check is enough"Partial proof is no proof
"Different wording so rule doesn't apply"Intent over technicality

Verification Patterns

Tests:

CORRECT: [Run test command] [Output: 34/34 pass] "All tests pass"
WRONG: "Should pass now" / "Looks correct"

Regression tests (Red-Green cycle):

CORRECT: Write -> Run (pass) -> Revert fix -> Run (MUST FAIL) -> Restore -> Run (pass)
WRONG: "I've written a regression test" (without red-green confirmation)

Build:

CORRECT: [Run build] [Output: exit 0] "Build passes"
WRONG: "Linter passed" (linter does not validate compilation)

Specification compliance:

CORRECT: Re-read plan -> Create checklist -> Verify each item -> Report gaps or completion
WRONG: "Tests pass, phase done"

Agent delegation:

CORRECT: Agent reports done -> Check VCS diff -> Verify changes -> Report actual state
WRONG: Trust agent report at face value

Verifying Configuration Changes

When testing changes to configuration, providers, feature flags, or environment settings:

Do not merely confirm the operation succeeded. Confirm the output reflects the intended change.

The Silent Fallback Problem

An operation can succeed because some valid configuration exists, even if it is not the configuration you intended to apply.

ChangeInsufficientRequired
Switch LLM providerHTTP 200Response body contains expected model identifier
Toggle feature flagNo errorsFeature behavior observably active
Change environmentDeployment succeedsLogs/variables reference the new environment
Set credentialsAuthentication succeedsAuthenticated identity is the correct one
Show full SKILL.md (184 more words)Show less
Configuration Verification Sequence
BEFORE asserting a configuration change works:

1. IDENTIFY: What should be DIFFERENT after this change?
2. LOCATE: Where is that difference observable?
3. EXECUTE: Command that exposes the observable difference
4. CONFIRM: Output contains the expected difference
5. ONLY THEN: Assert the configuration change works

Warning signs:
  - "Request succeeded" without inspecting content
  - Checking status code but ignoring response body
  - Confirming no errors but lacking positive confirmation

Verifying UI Work

When asserting UI work is complete:

AssertionDemandsInsufficient
Component matches designVisual comparison against UX reference"It looks right to me"
Responsive design worksTested at mobile, tablet, desktop breakpointsDesktop-only check
Accessibility passesScreen reader test + keyboard navigation + contrast check"I added aria labels"
Design tokens appliedSpacing/colors/typography match token values"I used the right classes"

Why This Matters

From accumulated failure patterns:

  • your human partner said "I don't believe you" — trust shattered
  • Undefined functions shipped — immediate crash
  • Missing requirements shipped — incomplete features
  • Time wasted on false completion -> redirect -> rework
  • Violates: "Honesty is a core value. If you lie, you'll be replaced."

When to Apply

ALWAYS before:

  • ANY variation of success or completion claims
  • ANY expression of satisfaction
  • ANY positive statement about work state
  • Committing, PR creation, task completion
  • Transitioning to the next task
  • Delegating to agents

Rule applies to:

  • Exact phrases
  • Paraphrases and synonyms
  • Implications of success
  • ANY communication suggesting completion or correctness

The Bottom Line

There are no shortcuts for verification.

Execute the command. Read the output. THEN state the result.

This is non-negotiable.

© NoobyGains, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/completion-gate of NoobyGains/godmode.

Open the folder on GitHubat commit 441103a

Compare with similar skills

Completion Gate 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.

Completion Gate compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Completion Gate this skillNoobyGains/godmode107—~1.6kAutomated safety check: PassMIT
Verification Before CompletionjnMetaCode/superpowers-zh8.3k—~443Automated safety check: PassMIT
Fixalirezarezvani/claude-skills28k1 repos~765Automated safety check: PassMIT
Orch Fix Defectaffaan-m/ECC275k1 repos~414Automated safety check: PassMIT
Gate Testsvercel/next.js143k—~2.7kAutomated safety check: PassMIT
Verification Before Completionforyourhealth111-pixel/Vibe-Skills3.6k—~1.1kAutomated safety check: PassApache-2.0

Similar skills

  • Verification Before Completion

    jnMetaCode/superpowers-zh

    Chinese-language rule that bars an agent from claiming work is done, fixed or passing until it has run a verification command and read the output.

    8.3k GitHub stars~443 tokensUpdated 4 days ago
    Agent WorkflowsAuto-check passed
  • Fix

    alirezarezvani/claude-skills

    Fix failing or flaky Playwright tests. An agent skill from alirezarezvani/claude-skills.

    28k GitHub starsUsed in 1 repo~765 tokens
    Testing & QAAuto-check passed
  • Orch Fix Defect

    affaan-m/ECC

    Orchestrate fixing a bug — reproduce it as a failing regression test, fix to green, review, and gated commit — by delegating each phase to the matching ECC agent.

    275k GitHub starsUsed in 1 repo~414 tokens
    Testing & QAAuto-check passed
  • Gate Tests

    vercel/next.js

    Official

    How to use the @gate / @force-gate test directives instead of it.skip or fake-green skip patterns.

    143k GitHub stars~2.7k tokensUpdated today
    Auto-check passed
  • Verification Before Completion

    foryourhealth111-pixel/Vibe-Skills

    Completion-evidence route used before claiming work is complete, fixed, passing, committed, or PR-ready.

    3.6k GitHub stars~1.1k tokensUpdated 1 mo ago
    Agent WorkflowsAuto-check passed
  • Delivery Gate

    affaan-m/ECC

    Stop hook that blocks Claude from finishing until quality checks pass.

    275k GitHub stars~1.3k tokensUpdated 3 days ago
    Auto-check passed

More from NoobyGains/godmode

All 34 skills in this repo
  • Activation

    NoobyGains/godmode

    A skill your agent uses when starting any conversation - establishes how to locate and invoke skills, mandating Skill tool usage before ANY response including clarifying questions

    107 GitHub stars~2.4k tokensUpdated 7 mo ago
    Auto-check passed
  • Agent Messaging

    NoobyGains/godmode

    A skill your agent uses when dispatching subagents, composing prompts for teammates, structuring handoff reports, or managing context boundaries between agents.

    107 GitHub stars~3k tokensUpdated 7 mo ago
    Auto-check passed
  • Codebase Research

    NoobyGains/godmode

    A skill your agent uses when building ANY feature within an existing project - search the current codebase for existing patterns, conventions, similar implementations, and established approaches…

    107 GitHub stars~3.2k tokensUpdated 7 mo ago
    Auto-check: notes
  • Comprehension Check

    NoobyGains/godmode

    A skill your agent uses when implementing any substantial feature, multi-file modification, or architectural change - produces a plain-language walkthrough of every alteration so the developer can…

    107 GitHub stars~1.5k tokensUpdated 7 mo ago
    Auto-check passed
  • Delegated Execution

    NoobyGains/godmode

    A skill your agent uses when executing implementation plans with independent tasks in the current session

    107 GitHub stars~2.4k tokensUpdated 7 mo ago
    Auto-check passed
  • Deployment Advisor

    NoobyGains/godmode

    A skill your agent uses when making technology, hosting, or infrastructure decisions — recommends services, databases, and deployment strategies based on project requirements and what the user…

    107 GitHub stars~4k tokensUpdated 7 mo ago
    Auto-check: notes

Questions about Completion Gate

What does Completion Gate do?

A skill your agent uses when about to declare work done, fixed, or passing, before committing or opening PRs - demands executing verification commands and reading their output before making any…. Completion Gate is an agent skill from NoobyGains/godmode.

When should I use Completion Gate?

Completion Gate fits situations like: about to declare work done; before committing; opening PRs - demands executing verification commands and reading their output before making any success assertions; evidence precedes claims always.

How do I install Completion Gate in Claude Code?

Run `npx skills add NoobyGains/godmode --skill completion-gate -a claude-code`. Or copy the skill folder (skills/completion-gate in NoobyGains/godmode) into .claude/skills/completion-gate in your project. Claude Code loads it when a task matches its description.

How do I install Completion Gate in Codex?

Run `npx skills add NoobyGains/godmode --skill completion-gate -a codex`. Or copy the skill folder (skills/completion-gate in NoobyGains/godmode) into .agents/skills/completion-gate in your project. Codex loads it when a task matches its description.

Can I use Completion Gate in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add NoobyGains/godmode --skill completion-gate -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/completion-gate, .gemini/skills/completion-gate, .github/skills/completion-gate and .opencode/skills/completion-gate in your project.

What does Completion Gate need to run?

SKILL.md names no scripts, command-line tools or credentials: Completion Gate is instructions for the agent only.

Does Completion Gate access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Completion Gate safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Completion Gate use?

Completion Gate is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Completion Gate use?

About 1.6k tokens (SKILL.md is roughly 6.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Completion Gate?

Skills that share tags, products or a category with Completion Gate: Verification Before Completion (jnMetaCode/superpowers-zh, 8.3k stars), Fix (alirezarezvani/claude-skills, 28k stars), Orch Fix Defect (affaan-m/ECC, 275k stars) and Gate Tests (vercel/next.js, 143k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Completion Gate?

NoobyGains (a GitHub user) maintains it in NoobyGains/godmode, which has 107 GitHub stars. The repository holds 34 skills in this directory. The repository was last updated on March 9, 2026.

Source: NoobyGains/godmode on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.