Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/gittower/git-flow-next --skill commit명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
Run the full release process end-to-end - prep, tag, CI verification, Homebrew tap, WinGet verification, and website sync
Handle a small fix or maintenance task locally end-to-end — no PR, but full review gates and a confirmed local merge into main
Fully solve a small issue end-to-end — resolve, publish the PR, run two Copilot review rounds, address them, and merge when confident. Escalates to the user on anything uncertain.
SOC 직업 분류 기준
SKILL.md 표시 중
| name | commit |
| description | Create a commit following COMMIT_GUIDELINES.md |
| argument-hint | ["optional message hint"] |
| allowed-tools | Bash, Read, Grep |
Create a well-formatted commit following the project's COMMIT_GUIDELINES.md.
Read COMMIT_GUIDELINES.md for all formatting rules, commit types, and conventions
Check Status
git status to see staged and unstaged changesgit diff --cached to see what will be committedgit add -AAnalyze Changes
Write Commit Message per COMMIT_GUIDELINES.md rules
Create Commit using HEREDOC format for proper formatting:
git commit -m "$(cat <<'EOF'
<type>(<scope>): <subject>
<body>
<footer>
EOF
)"
Verify — run git log -1 to check the message
Choose the type based on the purpose of the change, not the file type:
| Type | Use when... | Example |
|---|---|---|
| feat | Adding new user-facing functionality | New CLI command, new flag, new config option |
| fix | Fixing a user-facing bug | Incorrect merge behavior, wrong exit code |
| refactor | Restructuring code without behavior change | Extract helper, rename internal function |
| test | Adding/fixing tests (even if fixing a bug in a test) | New test case, fix flaky test |
| docs | Changing user-facing documentation content | Update README, manpage, ARCHITECTURE.md |
| ci | Changing CI/CD, automation, review tooling, GitHub config | Workflows, Copilot/Claude instructions, skills, .github/ config |
| build | Changing build system or dependencies | go.mod, build scripts, Makefile |
| style | Code formatting only, no logic change | go fmt, whitespace fixes |
| chore | Maintenance that doesn't fit above | Update .gitignore, tool config |
.md files are not always docs — a Markdown file that configures tool behavior (e.g., Copilot instructions, Claude skills, review criteria) is ci, not docsfix is for user-facing bugs only — fixing a CI workflow is ci, fixing a test is test, fixing a build script is buildtest covers test fixes too — use test: not fix: when correcting test codeWhen a guideline specifies a hard line wrap limit, write the text as continuous flowing prose first, then hard wrap at the specified character limit, filling each line as close to the limit as possible.
git commit -m "$(cat <<'EOF'
feat(finish): Add squash merge strategy
Implements --squash flag for finish command that performs a squash merge
instead of a regular merge, creating a single commit with all branch
changes on the target branch.
- Add squash option to merge strategy enum
- Update finish command to handle squash flag
- Add configuration support for default squash behavior
Resolves #42
EOF
)"