ee0f4bd5d9
- Add comprehensive built-in commands reference (40+ commands) - Document argument handling ($ARGUMENTS, $1, $2, etc.) - Add bash execution syntax (! prefix) and file references (@ prefix) - Update frontmatter to official fields (allowed-tools, argument-hint, model, etc.) - Add Plugin Commands and MCP Slash Commands sections - Add SlashCommand Tool documentation for programmatic invocation - Add Skills vs Slash Commands comparison table - Create commit.md example with bash execution and context - Update existing examples to use official frontmatter format - Add OpenSpec proposal for change tracking
27 lines
763 B
Markdown
27 lines
763 B
Markdown
---
|
|
description: Clean up code, stage changes, and prepare a pull request
|
|
allowed-tools: Bash(git add:*), Bash(git status:*), Bash(git diff:*), Bash(npm test:*), Bash(npm run lint:*)
|
|
---
|
|
|
|
# Pull Request Preparation Checklist
|
|
|
|
Before creating a PR, execute these steps:
|
|
|
|
1. Run linting: `prettier --write .`
|
|
2. Run tests: `npm test`
|
|
3. Review git diff: `git diff HEAD`
|
|
4. Stage changes: `git add .`
|
|
5. Create commit message following conventional commits:
|
|
- `fix:` for bug fixes
|
|
- `feat:` for new features
|
|
- `docs:` for documentation
|
|
- `refactor:` for code restructuring
|
|
- `test:` for test additions
|
|
- `chore:` for maintenance
|
|
|
|
6. Generate PR summary including:
|
|
- What changed
|
|
- Why it changed
|
|
- Testing performed
|
|
- Potential impacts
|