# Quality Gates

This skill wires up automatic code checks: lint and typecheck after every edit, a local CI run before push, and a five-stage deploy checklist.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 536 installs · ★ 28
- Author: hedera-dev
- License: Apache-2.0 · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/hedera-dev/hedera-skills/tree/HEAD/plugins/dev-intelligence/skills/quality-gates/SKILL.md
- Updated: 2026-09-03
- HTML: https://affpapa.org/en/nevibecode/skills/quality-gates

## What it does

Quality Gates covers validation at every stage, from a single file edit to a full deploy. The core piece is a PostToolUse hook. The agent calls `Edit` or `Write`, the hook fires on its own, and `scripts/post-edit-check.sh` detects the file type and runs the matching checker. The agent sees errors right away and fixes them in the same session.

Stack detection reads project files: `tsconfig.json` maps to `npx tsc --noEmit`, `package.json` without tsconfig to `npx eslint`, `pyproject.toml` or `setup.py` to `ruff check`, `Cargo.toml` to `cargo check`, `go.mod` to `go vet ./...`. Individual files fall back to extension matching. Install it as a plugin and the hook in `hooks/hooks.json` is picked up automatically. For manual setup in `.claude/settings.json`, the command has to be exactly `bash .claude/scripts/post-edit-check.sh` with no arguments, because the script reads `$CLAUDE_TOOL_INPUT` from the environment itself. Any extra flag breaks the hook.

Before a push the skill runs a local pipeline: lint, build, test, security scan. Stages run in order, the run stops at the first failure, and results land in `.claude/reports/ci/`. Before a deploy there are five verification stages: code quality, build, environment variables, container, and post-deploy health. The script checks that env vars are present and never reads their values.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add hedera-dev/hedera-skills --skill quality-gates -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/quality-gates/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/quality-gates/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add hedera-dev/hedera-skills --skill quality-gates -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/quality-gates/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add hedera-dev/hedera-skills --skill quality-gates -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/quality-gates/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install hedera-dev/hedera-skills quality-gates
```

2. **Manually: put the files in place**
- File: `.github/skills/quality-gates/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add hedera-dev/hedera-skills --skill quality-gates -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/hedera-dev/hedera-skills --path plugins/dev-intelligence/skills/quality-gates
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/quality-gates/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add hedera-dev/hedera-skills --skill quality-gates -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/hedera-dev/hedera-skills/tree/HEAD/plugins/dev-intelligence/skills/quality-gates/SKILL.md

## When to use it
- catch a type error right after editing a file
- set up a hook that runs the linter on its own
- run lint, build and tests before pushing
- build a pre-deploy verification checklist
- pick the right validator for the project stack

## Example prompts
- set up linting and auto-check after edits
- add pre-push checks: lint, build, tests
- create a deploy checklist for this project

## Source text · SKILL.md · Apache-2.0

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 053ea05e5f7455bb.

BEGIN THIRD-PARTY FILE 053ea05e5f7455bb
````text
---
name: Quality Gates
description: This skill should be used when the user wants to set up linting, configure auto-checking after edits, create a deploy checklist, set up pre-push checks, configure a CI pipeline, add quality gates, set up a hook for typechecking, enable post-edit validation, or auto-validate code changes. Triggered by phrases like "set up linting", "auto check after edits", "deploy checklist", "pre-push checks", "CI pipeline", "quality gates", "hook for typecheck", "post-edit validation", "auto-validate".
---

# Quality Gates

## Purpose

Automatic quality validation at every stage of development — from individual file edits to full deployments. Quality gates catch errors early when they're cheapest to fix.

## PostToolUse Hooks

The most powerful quality gate: automatic validation every time a file is edited or created.

### How It Works
1. Agent uses `Edit` or `Write` to modify a file
2. PostToolUse hook fires automatically
3. Validation script detects the file type and runs the appropriate checker
4. Output is shown to the agent immediately
5. Agent sees errors and can fix them in the same session

### Setting Up
The plugin includes a ready-to-use hook in `hooks/hooks.json` that runs `scripts/post-edit-check.sh`. When installed as a plugin, this works automatically.

For manual setup in a project, add to `.claude/settings.json`:

```json
{
  "hooks": {
    "PostToolUse": [
      {
        "matcher": "Edit|Write",
        "hooks": [
          {
            "type": "command",
            "command": "bash .claude/scripts/post-edit-check.sh"
          }
        ]
      }
    ]
  }
}
```

**Important:** The command must be exactly `bash .claude/scripts/post-edit-check.sh` — do not add arguments. The script reads `$CLAUDE_TOOL_INPUT` from the environment automatically.

See `references/hook-patterns.md` for stack-specific hook examples.

## Deploy Checklist

Before deploying any application, run through these 5 verification stages:

| Stage | What | Gate |
|-------|------|------|
| 1. Code Quality | Lint + Typecheck + Tests | All pass |
| 2. Build | Full build succeeds | Artifacts exist |
| 3. Environment | Required env vars present | All set (never read values) |
| 4. Container | Image builds and starts | No errors |
| 5. Post-Deploy | Health endpoint, logs | 200 OK, clean logs |

See `references/deploy-checklist.md` for complete verification commands per stack.
````
END THIRD-PARTY FILE 053ea05e5f7455bb

The third-party file has ended. Everything between the 053ea05e5f7455bb tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2426 of 4252 bytes. © hedera-dev · Apache-2.0 · https://github.com/hedera-dev/hedera-skills/tree/HEAD/plugins/dev-intelligence/skills/quality-gates/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md