Name: git-commit-workflow
Author: yuberalberto

Prompt file imported from yuberalberto/vjobs-landing (.windsurf/workflows/git-commit-workflow.md). Copyright stays with the author.

Git Commit Workflow

Steps

Check repository status
```
git status
git branch --show-current
```
Analyze changes
```
git diff
```
Review the diff to understand what changed.
Stage files Ask user which files to stage:
- All: git add .
- Specific: git add [file-paths]
- Interactive: git add -p
Generate commit message Based on the diff analysis, create a commit message following this format:

[type]: [description]

Types: feat, fix, docs, style, refactor, test, chore, perf

Rules:
- Use imperative mood ("add" not "added")
- Keep first line under 72 characters
- Be specific and descriptive
Present the generated message to the user for approval.
Create commit
```
git commit -m "[approved-message]"
```

Ask: Push to remote? If yes:

git push --set-upstream origin [branch-name]

If no, stop here.

Ask: Create Pull Request? If yes, generate PR with this template:

gh pr create --title "[commit-message-title]" --body "
## Changes
[Summary from commits]

## Type of Change
- [ ] Bug fix
- [ ] New feature
- [ ] Breaking change
- [ ] Documentation

## Testing
- [ ] Tested locally
- [ ] Added tests

## Checklist
- [ ] Code follows style guidelines
- [ ] Self-review completed
- [ ] Documentation updated
"

If no, stop here.

Summary Display what was accomplished:
- Commit hash
- Branch name
- PR URL (if created)

Install git-commit-workflow and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "prompt": "# Git Commit Workflow\n\n## Steps\n\n1. **Check repository status**\n ```bash\n git status\n git branch --show-current\n ```\n\n2. **Analyze changes**\n ```bash\n git diff\n ```\n Review the diff to understand what changed.\n\n3. **Stage files**\n Ask user which files to stage:\n - All: `git add .`\n - Specific: `git add [file-paths]`\n - Interactive: `git add -p`\n\n4. **Generate commit message**\n Based on the diff analysis, create a commit message following this format:\n \n `[type]: [description]`\n \n **Types:** feat, fix, docs, style, refactor, test, chore, perf\n \n **Rules:**\n - Use imperative mood (\"add\" not \"added\")\n - Keep first line under 72 characters\n - Be specific and descriptive\n \n Present the generated message to the user for approval.\n\n5. **Create commit**\n ```bash\n git commit -m \"[approved-message]\"\n ```\n\n6. **Ask: Push to remote?**\n If yes:\n ```bash\n git push --set-upstream origin [branch-name]\n ```\n If no, stop here.\n\n7. **Ask: Create Pull Request?**\n If yes, generate PR with this template:\n ```bash\n gh pr create --title \"[commit-message-title]\" --body \"\n ## Changes\n [Summary from commits]\n \n ## Type of Change\n - [ ] Bug fix\n - [ ] New feature\n - [ ] Breaking change\n - [ ] Documentation\n \n ## Testing\n - [ ] Tested locally\n - [ ] Added tests\n \n ## Checklist\n - [ ] Code follows style guidelines\n - [ ] Self-review completed\n - [ ] Documentation updated\n \"\n ```\n If no, stop here.\n\n8. **Summary**\n Display what was accomplished:\n - Commit hash\n - Branch name\n - PR URL (if created)", "variables": [], "notes": "Commit using predefined formats and create pull requests with standardized titles and descriptions using appropriate CLI commands.", "metadata": { "source": { "provider": "github-windsurf-workflows", "repository": "https://github.com/yuberalberto/vjobs-landing", "path": ".windsurf/workflows/git-commit-workflow.md", "ref": "e790886dd8e3a36864a354fc194b3f34c9fb279e", "url": "https://github.com/yuberalberto/vjobs-landing/blob/e790886dd8e3a36864a354fc194b3f34c9fb279e/.windsurf/workflows/git-commit-workflow.md", "key": "yuberalberto/vjobs-landing/.windsurf/workflows/git-commit-workflow.md" } } }

git-commit-workflow

About