Turns a coding request into a specification the model can actually work from, rather than a general description that comes back not compiling.
What it actually does: allowed-tools, Bash(git add, ), Bash(git status, ), Bash(git commit, ), Bash(git push, ), Bash(gh pr create, ) description, Commit and push everything then open a PR request to main --- Context - Current git status, !
--- allowed-tools: Bash(git add:*), Bash(git status:*), Bash(git commit:*), Bash(git push:*), Bash(gh pr create:*) description: Commit and push everything then open a PR request to main --- ## Context - Current git status: !`git status` - Current git diff (staged and unstaged changes): !`git diff HEAD` - Current branch: !`git branch --show-current` - Recent commits: !`git log --oneline -10` ## Your task 1. Review the existing changes and then create a git commit following the conventional commit format. If you think there are more than one distinct change you can create multiple commits. If there are no outstanding changes proceed to 2. 2. Push all commits. 3. Open a PR to main following the conventional formats.
--- allowed-tools: Bash(git add:*), Bash(git status:*), Bash(git commit:*), Bash(git push:*), Bash(gh pr create:*) description: Commit and push everything then open a PR request to main --- ## Context - Current git status: !`git status` - Current git diff (staged and unstaged changes): !`git diff HEAD` - Current branch: !`git branch --show-current` - Recent commits: !`git log --oneline -10` ## Your task 1. Review the existing changes and then create a git commit following the conventional commit format. If you think there are more than one distinct change you can create multiple commits. If there are no outstanding changes proceed to 2. 2. Push all commits. 3. Open a PR to main following the conventional formats.