메뉴
Enforces Conventional Commits 1.0.0 for all git commit messages. Use this skill whenever the user asks to commit changes, create a commit, or save progress to git. Ensures commit messages follow the conventional format with proper type, scope, and description.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Measure and quantify performance with profilers and flame graphs. Use this skill whenever the user wants to profile code, find hot spots or bottlenecks, generate a flame graph, benchmark code, or measure whether an optimization actually helped — including when the user just says something is "slow" and wants to know why. Covers FlameGraph (perf, sample), language-native profilers (go pprof, cargo flamegraph, py-spy), hyperfine, and differential flame graphs for before/after comparison.
Reconstruct git commit history on a development branch. Resets messy commits back to a clean diff against the base branch, then guides the user to rebuild logically coherent, minimal commits one by one. Use this skill when the user wants to clean up commits, reorganize history, split commits, squash and recommit, or tidy up before a PR. Provides a more controllable alternative to interactive rebase.
Design test cases following Kent Beck and t-wada principles. Use this skill when the user asks what to test, wants to design test cases, needs a test strategy, or wants to identify edge cases and boundary conditions for a feature. Focuses on behavior-driven testing with the 0-1-N rule.
Determines the next version number following Semantic Versioning 2.0.0. Use this skill when the user asks to determine the next version, bump the version, prepare a release, or create a version tag. Analyzes commit history with Conventional Commits to recommend the appropriate MAJOR, MINOR, or PATCH bump.
Analyze and create a refactoring plan for codebases grown through vibe coding. Use this skill when the user wants to clean up, reorganize, or redesign code that has been built incrementally and become messy. Also use when the user mentions technical debt, legacy code cleanup, code reorganization, or wants to restructure a project without breaking existing behavior. This skill produces a plan — it does not execute changes itself.
Architecture and design consultation for applications. Use this skill when discussing system architecture, design patterns, tech stack decisions, API design, or module structure. Covers Unix/Linux Philosophy for CLI tools and Twelve-Factor App for web applications and microservices.
| name | commit |
| description | Enforces Conventional Commits 1.0.0 for all git commit messages. Use this skill whenever the user asks to commit changes, create a commit, or save progress to git. Ensures commit messages follow the conventional format with proper type, scope, and description. |
All commit messages follow the Conventional Commits 1.0.0 specification:
<type>[optional scope]: <description>
[optional body]
[optional footer(s)]
feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert! after type/scope, or add a BREAKING CHANGE: footerEach commit represents a single logical change. Never combine unrelated features, fixes, or refactoring in one commit — recommend splitting instead. Atomic commits enable git bisect, clean reverts, and reviewable history.
Determine the scope from the staged changes:
git log --oneline -20 to learn the repository's existing scope conventions.git diff --cached --name-only and map staged files to a scope following those conventions (typically the top-level directory, module, or component name).When asked to commit changes:
git diff --cached --name-only to see staged files