메뉴
Comprehensive commit workflow that builds projects, runs tests, linters, and formatters, then creates semantic commits following organizational standards. Use when committing code changes to ensure quality, consistency, and proper commit message formatting.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Drive performance optimizations through a disciplined measure-optimize-measure cycle. Write benchmarks first, optimize with data, and validate improvements empirically. Use when building performance-critical code paths, lock-free structures, or when performance requirements are quantified.
Prevent false sharing in concurrent Rust code by aligning data structures to cache-line boundaries. Critical for lock-free data structures and multi-threaded hot paths. Use when building multi-threaded code with shared atomics or lock-free structures.
Document decisions, challenges, and solutions immediately after completing each phase. Captures context that would be lost later, creates invaluable reference for future work. Use for complex projects with non-obvious design decisions or any project taking more than 1 week.
Test and validate after each component/phase instead of waiting until the end. Catches bugs early when they're cheap to fix, prevents cascade failures. Use when building complex systems with multiple components where components depend on each other.
Measure sub-microsecond latencies using architecture-specific timestamp counters (TSC) and wait-free histograms. Essential for real-time systems, HFT, and latency-sensitive applications. Use when sub-microsecond latency requirements exist or when P99/P95 percentile analysis matters.
Layer different test types (unit, property, concurrency, stress, benchmark) to catch different bug classes. Each level catches what others miss. Use for complex systems, concurrent/parallel code, or performance-critical applications.
| name | commit |
| description | Comprehensive commit workflow that builds projects, runs tests, linters, and formatters, then creates semantic commits following organizational standards. Use when committing code changes to ensure quality, consistency, and proper commit message formatting. |
| license | Complete terms in LICENSE.txt |
This skill provides a comprehensive commit workflow that ensures code quality before committing. It automatically detects the repository type, builds the project, runs tests, executes linters and formatters, and then creates properly formatted semantic commits following organizational standards.
The commit process involves detecting the repository type, running quality checks, and creating semantic commits:
Identify Project Type:
package.json, tsconfig.json, yarn.lock, package-lock.jsonrequirements.txt, pyproject.toml, setup.py, Pipfilego.mod, go.sumCargo.toml, Cargo.lockpom.xmlbuild.gradle, build.gradle.ktsGemfile, RakefileCheck for Build Tools:
package.jsonTest Frameworks:
Linters:
Formatters:
Load 📋 Quality Checks Guide for comprehensive quality check strategies.
Node.js/TypeScript:
# Check for build script
npm run build
# or
yarn build
# or
pnpm build
Python:
# Check if build is needed (usually not for pure Python)
python setup.py build
# or
pip install -e .
Go:
go build ./...
Rust:
cargo build
General:
Execute Test Suites:
# Node.js
npm test
# or
yarn test
# or
pnpm test
# Python
pytest
# or
python -m pytest
# or
python -m unittest
# Go
go test ./...
# Rust
cargo test
Test Requirements:
Execute Linters:
# ESLint
npm run lint
# or
npx eslint .
# Python
pylint .
# or
flake8 .
# or
ruff check .
# Go
golangci-lint run
# Rust
cargo clippy
Linter Requirements:
Execute Formatters:
# Prettier
npm run format
# or
npx prettier --write .
# Python Black
black .
# or
ruff format .
# Go
gofmt -w .
# Rust
cargo fmt
Formatter Requirements:
Load 📝 Semantic Commits Guide for complete commit message standards.
Detect Change Types:
Change Categories:
Semantic Commit Format:
<type>(<scope>): <subject>
<body>
<footer>
Components:
Message Requirements:
Create Commit:
git commit -m "type(scope): subject" -m "body" -m "footer"
Verification:
Check Commit:
Commit Summary:
# 1. Detect: package.json exists
# 2. Build: npm run build
# 3. Test: npm test
# 4. Lint: npm run lint
# 5. Format: npm run format
# 6. Commit: git commit with semantic message
# 1. Detect: requirements.txt or pyproject.toml
# 2. Build: (usually skip for pure Python)
# 3. Test: pytest
# 4. Lint: ruff check . or flake8 .
# 5. Format: ruff format . or black .
# 6. Commit: git commit with semantic message
# 1. Detect: go.mod exists
# 2. Build: go build ./...
# 3. Test: go test ./...
# 4. Lint: golangci-lint run
# 5. Format: gofmt -w .
# 6. Commit: git commit with semantic message
Priority Order:
Common Files:
package.json → Node.jsgo.mod → GoCargo.toml → Rustrequirements.txt / pyproject.toml → Pythonpom.xml → Maven (Java)build.gradle → Gradle (Java)Gemfile → RubyNode.js:
npm run buildyarn buildpnpm buildtsc --build (TypeScript)Python:
python setup.py build (if setup.py exists)pip install -e . (development install)Go:
go build ./...go build -o bin/app ./cmd/appRust:
cargo buildcargo build --releaseNode.js:
npm testyarn testpnpm testnpm run test:unitnpm run test:integrationPython:
pytestpython -m pytestpython -m unittesttoxGo:
go test ./...go test -v ./...go test -race ./...Rust:
cargo testcargo test --all-featuresNode.js:
npm run lintnpx eslint .npx tslint .Python:
ruff check .flake8 .pylint .mypy .Go:
golangci-lint rungolint ./...staticcheck ./...Rust:
cargo clippycargo clippy -- -D warningsNode.js:
npm run formatnpx prettier --write .npx eslint --fix .Python:
ruff format .black .autopep8 --in-place --recursive .Go:
gofmt -w .goimports -w .Rust:
cargo fmtStrategy:
Strategy:
Strategy:
Strategy:
Check for Existing Hooks:
Handle Staging:
Git Options:
--no-verify flag (skip hooks)--amend flag--no-edit flagLoad these resources as needed during commit operations:
📝 Semantic Commits Guide - Complete guide on semantic commit message format including:
📋 Quality Checks Guide - Comprehensive guide on running quality checks including:
✅ Best Practices Guide - Complete best practices for commit workflow including:
Skill Version: 1.0 Last Updated: 2025-01-06 Maintained By: Arda Development Team Dependencies: Git, project-specific build/test/lint/format tools