Skip to content

TsukiNi22/ai-utils / skills/git/git-conventions

git-conventions

Verified

FileKindSize
SKILL.mdskill md8.6 KB
templates/CHANGELOG.mdmarkdown1.0 KB
templates/pull-request.mdmarkdown520 B
templates/release.mdmarkdown402 B

templates/pull-request.md

View on GitHub
> [!NOTE]
> <What this PR brings in 1-3 sentences: the feature/fix, the touched sections.>

### Added
- <New feature/file/method, code in backticks>

### Changed
- **[MAJOR]** <Breaking change, only if any>
- <Modified behavior>

### Fixed
- <Bug fixed, described as the bug that was happening>

### Removed
- <Removed API (with the migration if any)>

### Tests
- <Unit tests added/updated, commands run: `ctest --test-dir build`>

> [!IMPORTANT]
> <Only if needed: what the reviewer must check, migration, follow-up.>
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall