Prompt file imported from NikiforovAll/github-copilot-rules (.github/prompts/commit.prompt.md). Copyright stays with the author.

Commit

Name: commit
Author: NikiforovAll

Create well-formatted commits with conventional commit messages.

Process

Check for staged changes (git status)
If no staged changes, review and stage appropriate files
Run pre-commit checks (unless --no-verify)
Analyze changes to determine commit type
Generate descriptive commit message
Include scope if applicable: type(scope): description
Add body for complex changes explaining why
Execute commit

Commit Types

Emoji	Type	Description
✨	feat	New features
🐛	fix	Bug fixes
📝	docs	Documentation changes
♻️	refactor	Code restructuring without changing functionality
🎨	style	Code formatting, missing semicolons, etc.
⚡️	perf	Performance improvements
✅	test	Adding or correcting tests
🧑‍💻	chore	Tooling, configuration, maintenance
🚧	wip	Work in progress
🔥	remove	Removing code or files
🚑	hotfix	Critical fixes
🔒	security	Security improvements

Format

<emoji> <type>(<optional scope>): <description>

<optional body>

<optional footer>

Best Practices

Keep commits atomic and focused
Write in imperative mood ("Add feature" not "Added feature")
Explain why, not just what
Reference issues/PRs when relevant
Split unrelated changes into separate commits

Usage

/commit - Standard commit with pre-commit checks
/commit --no-verify - Skip pre-commit checks

Examples

✨ feat(auth): add OAuth2 login support

Implements Google and GitHub OAuth providers.
Closes #123

🐛 fix(api): prevent null pointer in user validation

The error occurred when email field was undefined.

♻️ refactor: simplify database connection pooling

# Commit Create well-formatted commits with conventional commit messages. ## Process 1. Check for staged changes (`git status`) 2. If no staged changes, review and stage appropriate files 3. Run pre-commit checks (unless --no-verify) 4. Analyze changes to determine commit type 5. Generate descriptive commit message 6. Include scope if applicable: `type(scope): description` 7. Add body for complex changes explaining why 8. Execute commit ## Commit Types | Emoji | Type | Description | | ------ | -------- | ------------------------------------------------- | | ✨ | feat | New features | | 🐛 | fix | Bug fixes | | 📝 | docs | Documentation changes | | ♻️ | refactor | Code restructuring without changing functionality | | 🎨 | style | Code formatting, missing semicolons, etc. | | ⚡️ | perf | Performance improvements | | ✅ | test | Adding or correcting tests | | 🧑‍💻 | chore | Tooling, configuration, maintenance | | 🚧 | wip | Work in progress | | 🔥 | remove | Removing code or files | | 🚑 | hotfix | Critical fixes | | 🔒 | security | Security improvements | ## Format ``` <emoji> <type>(<optional scope>): <description> <optional body> <optional footer> ``` ## Best Practices - Keep commits atomic and focused - Write in imperative mood ("Add feature" not "Added feature") - Explain why, not just what - Reference issues/PRs when relevant - Split unrelated changes into separate commits ## Usage - `/commit` - Standard commit with pre-commit checks - `/commit --no-verify` - Skip pre-commit checks ## Examples ``` ✨ feat(auth): add OAuth2 login support Implements Google and GitHub OAuth providers. Closes #123 ``` ``` 🐛 fix(api): prevent null pointer in user validation The error occurred when email field was undefined. ``` ``` ♻️ refactor: simplify database connection pooling ```

{ "prompt": "# Commit\n\nCreate well-formatted commits with conventional commit messages.\n\n## Process\n\n1. Check for staged changes (`git status`)\n2. If no staged changes, review and stage appropriate files\n3. Run pre-commit checks (unless --no-verify)\n4. Analyze changes to determine commit type\n5. Generate descriptive commit message\n6. Include scope if applicable: `type(scope): description`\n7. Add body for complex changes explaining why\n8. Execute commit\n\n## Commit Types\n\n| Emoji | Type | Description |\n| ------ | -------- | ------------------------------------------------- |\n| ✨ | feat | New features |\n| 🐛 | fix | Bug fixes |\n| 📝 | docs | Documentation changes |\n| ♻️ | refactor | Code restructuring without changing functionality |\n| 🎨 | style | Code formatting, missing semicolons, etc. |\n| ⚡️ | perf | Performance improvements |\n| ✅ | test | Adding or correcting tests |\n| 🧑‍💻 | chore | Tooling, configuration, maintenance |\n| 🚧 | wip | Work in progress |\n| 🔥 | remove | Removing code or files |\n| 🚑 | hotfix | Critical fixes |\n| 🔒 | security | Security improvements |\n\n## Format\n\n```\n<emoji> <type>(<optional scope>): <description>\n\n<optional body>\n\n<optional footer>\n```\n\n## Best Practices\n\n- Keep commits atomic and focused\n- Write in imperative mood (\"Add feature\" not \"Added feature\")\n- Explain why, not just what\n- Reference issues/PRs when relevant\n- Split unrelated changes into separate commits\n\n## Usage\n\n- `/commit` - Standard commit with pre-commit checks\n- `/commit --no-verify` - Skip pre-commit checks\n\n## Examples\n\n```\n✨ feat(auth): add OAuth2 login support\n\nImplements Google and GitHub OAuth providers.\nCloses #123\n```\n\n```\n🐛 fix(api): prevent null pointer in user validation\n\nThe error occurred when email field was undefined.\n```\n\n```\n♻️ refactor: simplify database connection pooling\n```", "variables": [], "notes": "Create a git commit with conventional commit format and emoji Arguments: Optional flags like --no-verify to skip pre-commit hooks.", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/NikiforovAll/github-copilot-rules", "path": ".github/prompts/commit.prompt.md", "ref": "f3fb825e0ce34dbefc1a3db19b2e81c102a47c4c", "url": "https://github.com/NikiforovAll/github-copilot-rules/blob/f3fb825e0ce34dbefc1a3db19b2e81c102a47c4c/.github/prompts/commit.prompt.md", "key": "NikiforovAll/github-copilot-rules/.github/prompts/commit.prompt.md" } } }

commit

About

Commit

Process

Commit Types

Format

Best Practices

Usage

Examples

Use it

Manifest

Reviews