一键导入
git-helper
Generate clear, conventional commit messages and manage Git workflows
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Generate clear, conventional commit messages and manage Git workflows
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Comprehensive code review focusing on quality, security, and best practices
Generate comprehensive documentation for code, APIs, and projects
Internationalization and localization assistance for multi-language applications
Identify code smells and suggest refactoring improvements
Generate comprehensive test cases following TDD principles
| name | git-helper |
| description | Generate clear, conventional commit messages and manage Git workflows |
| allowed-tools | ["Bash","Read","Grep"] |
| origin | bundled |
| version | 1.0.0 |
Generate clear, conventional commit messages and assist with Git workflows following best practices.
<type>(<scope>): <subject>
<body>
<footer>
Good Commit Messages:
feat(auth): add JWT token refresh mechanism
Implement automatic token refresh when access token expires.
Tokens are refreshed 5 minutes before expiration to prevent
authentication failures during active sessions.
- Add RefreshTokenService
- Update AuthMiddleware to handle token refresh
- Add unit tests for refresh logic
Closes #123
fix(api): prevent SQL injection in user search
Replace string concatenation with parameterized queries
in UserRepository.search() method.
BREAKING CHANGE: search() now requires SearchParams object
instead of raw string query.
refactor(utils): extract retry logic into separate module
Move retry logic from multiple services into shared
RetryHelper utility to reduce code duplication.
Bad Commit Messages:
update stuff
fix bug
WIP
- or * for listsBREAKING CHANGE: descriptionCloses #123, Fixes #456Co-authored-by: Name <email>git status
git diff
git add -p # Interactive staging
git add specific-file.ts
npm test
# or language-specific test command
npm run lint
# or language-specific linter
Good: One logical change per commit
git commit -m "feat(auth): add login endpoint"
git commit -m "test(auth): add login endpoint tests"
git commit -m "docs(auth): document login API"
Bad: Multiple unrelated changes
git commit -m "add login, fix bug in profile, update README"
# Fix commit message
git commit --amend -m "new message"
# Add forgotten files
git add forgotten-file.ts
git commit --amend --no-edit
# Clean up last 3 commits
git rebase -i HEAD~3
# Options: pick, reword, squash, fixup, drop
# Save work in progress
git stash save "WIP: feature description"
# List stashes
git stash list
# Apply stash
git stash pop
# Apply specific commit to current branch
git cherry-pick <commit-hash>
Format: <type>/<short-description>
Examples:
feat/user-authenticationfix/login-validation-bugrefactor/database-layerdocs/api-documentationgit checkout main
git pull
git checkout feature-branch
git rebase main
git rebase -i main
git push origin feature-branch
# or if rebased
git push --force-with-lease origin feature-branch
## Description
Brief description of changes
## Changes
- Change 1
- Change 2
- Change 3
## Testing
- [ ] Unit tests added/updated
- [ ] Integration tests pass
- [ ] Manual testing completed
## Related Issues
Closes #123
Analyze changes
git diff --stagedDetermine type
featfixrefactorIdentify scope
Write subject
Add body if needed