How do I install the Code Quality Gates skill?

Run npx get-skill add tomevault-io/code-quality-gates in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Code Quality Gates safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Code Quality Gates?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Code Quality Gates free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Code Quality Gates?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Code Quality Gates by tomevault-io — Agent Skill

Name: Code Quality Gates
Author: tomevault-io

File contents

SKILL: Code Quality Gates

Purpose: Automated quality checks before/after code changes (PreToolUse, PostToolUse, Stop hooks converted to skill logic) Target: All agents making code changes

Quick Start

When to Use This Skill

Before creating any .md files (documentation gate)
After writing code (formatting, type check)
Before completing work (final audit)

Quick Reference

# PreToolUse: Block .md creation
[[ "$file" == *.md ]] && echo "Use Write tool for .md" && return 1

# PostToolUse: Auto-format + type check
prettier --write "$file" && npx tsc --noEmit

# Stop: Console.log audit
grep -rn "console.log" src/ || true

Quality Gates

Gate 1: Documentation (PreToolUse)

Purpose: Block .md file creation via Bash

Apply: Before Bash commands

echo "$command" | grep -qiE '\.md' && echo "Use Write tool for .md" && return 1

Gate 2: Formatting (PostToolUse)

Purpose: Auto-format after code changes

Apply: After Edit/Write

format_code() {
  case "${1##*.}" in
    js|ts|tsx|json|css|md) prettier --write "$1" ;;
    py) black "$1" ;;
  esac
}

Gate 3: Type Safety (PostToolUse)

Purpose: Verify TypeScript type correctness

Apply: After .ts file changes

[ -f tsconfig.json ] && npx tsc --noEmit

Gate 4: Console Audit (Stop)

Purpose: Flag console.log before completion

Apply: Before work completion

find src -name "*.ts" -o -name "*.js" | xargs grep -n "console.log"

Integration Points

Hook	Function	Agent	Trigger
PreToolUse	Documentation gate	All	Before Bash
PostToolUse	Formatting	Coder	After Edit/Write
PostToolUse	Type check	Coder	After .ts changes
Stop	Console audit	Coder	Before completion

Verification

# Test all gates
echo "# Test" > test.md  # Should warn
echo "const x=1;" > test.js && prettier --write test.js  # Should format
echo "const x: string = 1;" > test.ts && npx tsc --noEmit  # Should error
grep -rn "console.log" src/  # Should find logs

Related Skills

vibe-coding: Code quality standards (≤50 lines/function, ≤200 lines/file)
coding-standards: TypeScript, React, API, testing standards
tdd: Test-driven development (Red-Green-Refactor)

Version: claude-pilot 4.3.0

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: code-quality-gatesdescription: Use automatically before and after code changes. Ensures documentation, formatting, type safety, and audit standards. Use when this capability is needed.---# SKILL: Code Quality Gates> **Purpose**: Automated quality checks before/after code changes (PreToolUse, PostToolUse, Stop hooks converted to skill logic)> **Target**: All agents making code changes---## Quick Start### When to Use This Skill- Before creating any .md files (documentation gate)- After writing code (formatting, type check)- Before completing work (final audit)### Quick Reference```bash# PreToolUse: Block .md creation[[ "$file" == *.md ]] && echo "Use Write tool for .md" && return 1# PostToolUse: Auto-format + type checkprettier --write "$file" && npx tsc --noEmit# Stop: Console.log auditgrep -rn "console.log" src/ || true```---## Quality Gates### Gate 1: Documentation (PreToolUse)**Purpose**: Block .md file creation via Bash**Apply**: Before Bash commands```bashecho "$command" | grep -qiE '\.md' && echo "Use Write tool for .md" && return 1```### Gate 2: Formatting (PostToolUse)**Purpose**: Auto-format after code changes**Apply**: After Edit/Write```bashformat_code() { case "${1##*.}" in js|ts|tsx|json|css|md) prettier --write "$1" ;; py) black "$1" ;; esac}```### Gate 3: Type Safety (PostToolUse)**Purpose**: Verify TypeScript type correctness**Apply**: After .ts file changes```bash[ -f tsconfig.json ] && npx tsc --noEmit```### Gate 4: Console Audit (Stop)**Purpose**: Flag console.log before completion**Apply**: Before work completion```bashfind src -name "*.ts" -o -name "*.js" | xargs grep -n "console.log"```---## Integration Points| Hook | Function | Agent | Trigger ||------|----------|-------|---------|| PreToolUse | Documentation gate | All | Before Bash || PostToolUse | Formatting | Coder | After Edit/Write || PostToolUse | Type check | Coder | After .ts changes || Stop | Console audit | Coder | Before completion |---## Verification```bash# Test all gatesecho "# Test" > test.md # Should warnecho "const x=1;" > test.js && prettier --write test.js # Should formatecho "const x: string = 1;" > test.ts && npx tsc --noEmit # Should errorgrep -rn "console.log" src/ # Should find logs```---## Related Skills- **vibe-coding**: Code quality standards (≤50 lines/function, ≤200 lines/file)- **coding-standards**: TypeScript, React, API, testing standards- **tdd**: Test-driven development (Red-Green-Refactor)---**Version**: claude-pilot 4.3.0---> Converted and distributed by [TomeVault](https://tomevault.io/claim/changoo89) — claim your Tome and manage your conversions.

Frequently asked questions

Code Quality Gates