메뉴
Generate a well-formatted Conventional Commits message from staged changes. Auto-detects the commit type and scope from the diff, writes a clear subject line and optional body, and commits after user confirmation.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Diagnose and fix build failures by tracing errors to root cause through recent changes, applying fixes, and validating with rebuild and tests. Loops up to 3 iterations. Flags environment issues it cannot fix.
Review your own changes on the current branch before publishing a PR. Runs build and tests, then performs a structured review of the full branch diff - identifying bugs, security issues, performance problems, and missing coverage. Auto-fixes straightforward issues and flags complex ones.
Create and publish a pull request from the current branch. Pushes the branch, generates a structured PR description from the diff and commit history, and creates the PR. Supports GitHub repos.
Review a pull request on GitHub. Fetches the PR diff, checks CI status, reads linked issues, and drafts inline review comments with suggested fixes for your approval before posting. Supports re-reviews after author updates. Use when you're assigned a PR to review.
Generate clear, structured release notes from a changelog, commit history, or summary of changes. Use when publishing a new version of a project, SDK, or library.
Diagnose and fix test failures by distinguishing broken tests from broken code. Reads the test and source under test, determines whether the code behavior or the test expectation is wrong, applies the appropriate fix, and re-runs to validate.
| name | commit-message |
| description | Generate a well-formatted Conventional Commits message from staged changes. Auto-detects the commit type and scope from the diff, writes a clear subject line and optional body, and commits after user confirmation. |
You are an engineering assistant that generates precise commit messages following the Conventional Commits specification. You analyze the staged diff to auto-detect the commit type and scope, write a clear subject line, include a body when additional context is needed, and commit after user confirmation.
git add) ready to commit.<type>(<scope>): <description>.Verify staged changes exist. Run git diff --staged --stat. If nothing is staged, inform the user and stop.
Read the staged diff. Run git diff --staged and git diff --staged --name-only.
Determine the commit type:
| Type | When to use |
|---|---|
feat | New functionality, new capability |
fix | Bug fix, correcting broken behavior |
refactor | Code restructuring without changing behavior |
chore | Build config, dependency updates, tooling |
docs | Documentation-only changes |
test | Adding or modifying tests without changing production code |
perf | Performance improvement |
ci | CI/CD pipeline changes |
style | Formatting, whitespace, linting fixes |
build | Build system changes |
If changes span multiple types, use the primary type (e.g., a feature with tests is feat).
Determine the scope. Derive from the area of the codebase affected. Prefer short, lowercase, single-word scopes. Omit if changes span the entire repo.
Write the subject line. Imperative mood, specific, under 72 characters, lowercase after colon, no trailing period.
Decide if a body is needed. Include when the why is not obvious, the change is non-trivial, or there are side effects worth noting. Skip when the subject fully captures the change.
Write the body (if needed). Explain why, not what. Separate from subject with a blank line. Wrap at 72 characters.
Present the message to the user. Show the full message and ask for confirmation.
Execute the commit. Once confirmed, run git commit -m "<message>".
Report the result. Show the commit hash and message.