메뉴
pre-commit hooks setup and validation. Use when installing hooks, configuring frontend/infrastructure/python project types, or migrating to pre-commit.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/laurigates/claude-plugins --skill configure-pre-commit명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
Install, configure and troubleshoot MCP servers. Use when adding/enabling servers, editing .mcp.json, fixing OAuth, or when a server runs stale code after an upstream fix.
FinOps snapshot — org billing, workflow stats, cache usage. Use when you want a high-level view of CI spending or workflow health before diving deeper.
GitHub Actions billing, workflow efficiency, and waste analysis at org or repo level. Use when investigating CI/CD costs, wasted runs, or optimizing triggers.
SKILL.md 표시 중
SOC 직업 분류 기준
| created | "2025-12-16T00:00:00.000Z" |
| modified | "2026-07-05T00:00:00.000Z" |
| reviewed | "2026-07-05T00:00:00.000Z" |
| description | pre-commit hooks setup and validation. Use when installing hooks, configuring frontend/infrastructure/python project types, or migrating to pre-commit. |
| allowed-tools | Glob, Grep, Read, Write, Edit, Bash, AskUserQuestion, TodoWrite, WebSearch, WebFetch |
| args | [--check-only] [--fix] [--type <frontend|infrastructure|python>] |
| argument-hint | [--check-only] [--fix] [--type <frontend|infrastructure|python>] |
| name | configure-pre-commit |
Check and configure pre-commit hooks against project standards.
| Use this skill when... | Use another approach when... |
|---|---|
| Setting up or validating pre-commit hooks | Project doesn't use pre-commit framework (use git hooks directly) |
| Checking compliance with project standards | Just running hooks manually (use pre-commit run command) |
| Installing project-type-specific hooks | Hooks are already properly configured |
| Migrating to pre-commit framework | Simple project with no quality checks needed |
| Updating hook configurations for detected tools | Need to disable pre-commit entirely |
find . -maxdepth 1 -name \'.pre-commit-config.yaml\'find . -maxdepth 1 -name \'.project-standards.yaml\'find . -maxdepth 1 -name '.project-standards.yaml' -exec grep -m1 "^project_type:" {} +find . -maxdepth 2 \( -name '*.tf' -o -type d -name 'terraform' \) -print -quitfind . -maxdepth 2 -type d -name 'helm' -print -quitfind . -maxdepth 1 -name \'package.json\'find . -maxdepth 1 -name \'pyproject.toml\'Parse from $ARGUMENTS:
--check-only: Report status without offering fixes--fix: Apply all fixes automatically without prompting--type <type>: Override project type detection (frontend, infrastructure, python)Execute this pre-commit compliance check:
.project-standards.yaml for project_type field if it existsterraform/, helm/, , or filesargocd/*.tfpackage.json with vue/react dependenciespyproject.toml or requirements.txt--type flag override if provided.pre-commit-config.yaml is missing: report FAIL, offer to create from templateCRITICAL: Before flagging outdated hooks, verify latest releases using WebSearch or WebFetch:
Compare existing configuration against the project standards in REFERENCE.md:
Required Base Hooks (All Projects):
pre-commit-hooks v5.0.0+ with: trailing-whitespace, end-of-file-fixer, check-yaml, check-json, check-merge-conflict, check-added-large-filesconventional-pre-commit v4.3.0+ with commit-msg stageFrontend-specific:
biome (pre-commit) v0.4.0+helmlint (if helm/ directory exists)Infrastructure-specific:
tflint, helmlint (gruntwork v0.1.29+)actionlint v1.7.7+helm-docs v1.14.2+gitleaks v8.22.1+Python-specific:
ruff-pre-commit v0.8.4+ (ruff, ruff-format)gitleaks v8.22.1+Print a report in this format:
Pre-commit Compliance Report
================================
Project Type: [type] ([detected|override])
Config File: .pre-commit-config.yaml ([found|missing])
Hook Status:
[hook-name] [version] [PASS|WARN|FAIL] ([details])
Outdated Hooks:
- [hook]: [current] -> [standard]
Overall: [N] issues found
If --fix flag is set or user confirms:
rev: values to standard versionsdefault_install_hook_types with pre-commit and commit-msgAfter modification, run pre-commit install --install-hooks to install hooks.
Update or create .project-standards.yaml:
standards_version: "2025.1"
project_type: "[detected]"
last_configured: "[timestamp]"
components:
pre-commit: "2025.1"
| Context | Command |
|---|---|
| Check if pre-commit installed | command -v pre-commit >/dev/null 2>&1 && echo "installed" || echo "missing" |
| Validate config syntax | pre-commit validate-config .pre-commit-config.yaml 2>&1 |
| List configured hooks | grep -E '^\s+- id:' .pre-commit-config.yaml 2>/dev/null | sed 's/.*id:[[:space:]]*//' |
| Check hook versions | pre-commit autoupdate --freeze 2>&1 |
| Quick compliance check | /configure:pre-commit --check-only |
| Auto-fix configuration | /configure:pre-commit --fix |
| Flag | Description |
|---|---|
--check-only | Report status without offering fixes |
--fix | Apply all fixes automatically without prompting |
--type <type> | Override project type detection (frontend, infrastructure, python) |
/configure:all - Run all compliance checks/configure:status - Quick compliance overview