์Šคํ‚ฌ quality-gates
๐Ÿ›ก๏ธ

quality-gates

์•ˆ์ „ โš™๏ธ ์™ธ๋ถ€ ๋ช…๋ น์–ด

Run quality checks before commits

๋˜ํ•œ ๋‹ค์Œ์—์„œ ์‚ฌ์šฉํ•  ์ˆ˜ ์žˆ์Šต๋‹ˆ๋‹ค: Barnhardt-Enterprises-Inc,ArieGoldkin

Manual code quality checks slow down development and allow bugs to slip through. This skill automatically runs linting, type checking, tests, and security audits before every commit or deployment.

์ง€์›: Claude Codex Code(CC)
๐Ÿ“Š 70 ์ ์ ˆํ•จ
1

์Šคํ‚ฌ ZIP ๋‹ค์šด๋กœ๋“œ

2

Claude์—์„œ ์—…๋กœ๋“œ

์„ค์ • โ†’ ๊ธฐ๋Šฅ โ†’ ์Šคํ‚ฌ โ†’ ์Šคํ‚ฌ ์—…๋กœ๋“œ๋กœ ์ด๋™

3

ํ† ๊ธ€์„ ์ผœ๊ณ  ์‚ฌ์šฉ ์‹œ์ž‘

ํ…Œ์ŠคํŠธํ•ด ๋ณด๊ธฐ

"quality-gates" ์‚ฌ์šฉ ์ค‘์ž…๋‹ˆ๋‹ค. Run quality gates before my commit

์˜ˆ์ƒ ๊ฒฐ๊ณผ:

  • Quality Gate Results: 5/6 Passed
  • Lint: PASS (0 errors, 2 warnings)
  • Type Check: PASS (0 errors)
  • Tests: PASS (124 passed, 0 failed, 87% coverage)
  • Build: PASS (build completed successfully)
  • Security Audit: PASS (no critical vulnerabilities)
  • Secrets Check: PASS (no secrets detected in staged files)
  • Ready to commit!

"quality-gates" ์‚ฌ์šฉ ์ค‘์ž…๋‹ˆ๋‹ค. Run security audit on my dependencies

์˜ˆ์ƒ ๊ฒฐ๊ณผ:

  • Security Audit Results: 3 vulnerabilities found
  • Critical: 0 | High: 1 | Moderate: 2
  • High: Prototype pollution in lodash < 4.17.21
  • Run 'npm audit fix' to resolve
  • Recommendation: Update lodash to latest version

๋ณด์•ˆ ๊ฐ์‚ฌ

์•ˆ์ „
v5 โ€ข 1/16/2026

This is a documentation-only skill file (SKILL.md) that defines quality assurance workflows. All command executions are standard development tools (npm, eslint, vitest) running locally. The heuristic finding is a false positive - this skill DEFENDS against credential leaks by checking git diffs for secrets, not exfiltrating credentials. No malicious intent present.

2
์Šค์บ”๋œ ํŒŒ์ผ
662
๋ถ„์„๋œ ์ค„ ์ˆ˜
1
๋ฐœ๊ฒฌ ์‚ฌํ•ญ
5
์ด ๊ฐ์‚ฌ ์ˆ˜

์œ„ํ—˜ ์š”์ธ

โš™๏ธ ์™ธ๋ถ€ ๋ช…๋ น์–ด (5)
SKILL.md:58-65 SKILL.md:94-101 SKILL.md:128-135 SKILL.md:166-169 SKILL.md:190-193
๊ฐ์‚ฌ์ž: claude ๊ฐ์‚ฌ ์ด๋ ฅ ๋ณด๊ธฐ โ†’

ํ’ˆ์งˆ ์ ์ˆ˜

38
์•„ํ‚คํ…์ฒ˜
100
์œ ์ง€๋ณด์ˆ˜์„ฑ
85
์ฝ˜ํ…์ธ 
30
์ปค๋ฎค๋‹ˆํ‹ฐ
100
๋ณด์•ˆ
83
์‚ฌ์–‘ ์ค€์ˆ˜

๋งŒ๋“ค ์ˆ˜ ์žˆ๋Š” ๊ฒƒ

Pre-commit quality checks

Run automated checks before every commit to catch issues early and maintain consistent code quality.

Pre-deploy validation

Verify build success, security compliance, and test coverage before deploying to production.

Quality standards enforcement

Define and enforce team-wide quality gates that all contributors must pass before merging.

์ด ํ”„๋กฌํ”„ํŠธ๋ฅผ ์‚ฌ์šฉํ•ด ๋ณด์„ธ์š”

Quick lint check 
Run quality gates for linting only on the changed files in this commit.
Full pre-commit check 
Run all pre-commit quality gates including linting, type checking, and tests.
Security audit 
Run security audit to check for vulnerabilities in dependencies and suggest fixes.
Pre-deploy validation 
Run comprehensive pre-deploy quality gates: lint, typecheck, tests, build verification, and security audit.

๋ชจ๋ฒ” ์‚ฌ๋ก€

  • Configure quality gates in package.json with lint, typecheck, and test scripts for consistent execution
  • Use Husky or similar git hooks to prevent bypassing quality gates accidentally
  • Set realistic coverage thresholds that encourage improvement without blocking development

ํ”ผํ•˜๊ธฐ

  • Skipping quality gates for quick fixes that eventually become technical debt
  • Setting coverage thresholds too high causing developers to write tests for the sake of metrics
  • Ignoring lint warnings as they accumulate and create noise that hides real issues

์ž์ฃผ ๋ฌป๋Š” ์งˆ๋ฌธ

Which tools does this skill support?
Supports ESLint, Biome for linting; tsc for TypeScript; Vitest, Jest, and Node.js native tests; npm/pnpm audit for security.
How long do quality gates take?
Pre-commit gates take under 30 seconds. Pre-push gates take up to 2 minutes. Pre-deploy gates take up to 5 minutes.
Can I skip gates for emergency fixes?
Yes, use git commit --no-verify to bypass hooks, but this is for emergencies only.
Is my code sent to external services?
No. All checks run locally using your installed tools. npm audit may check remote vulnerability databases.
What happens if a gate fails?
Gates run sequentially and stop at the first failure. The skill provides specific file locations and commands to fix issues.
How is this different from Husky?
Husky runs existing scripts as git hooks. This skill orchestrates which gates to run and provides intelligent feedback and fixes.

๊ฐœ๋ฐœ์ž ์„ธ๋ถ€ ์ •๋ณด

์ž‘์„ฑ์ž

AI-Vibe-Prompts

๋ผ์ด์„ ์Šค

MIT

๋ฆฌํฌ์ง€ํ† ๋ฆฌ

https://github.com/Atman36/AI-Vibe-Prompts/tree/main/.claude/skills/core/quality-gates

์ฐธ์กฐ

main

ํŒŒ์ผ ๊ตฌ์กฐ

๐Ÿ“„ SKILL.md