Menu
How to create and name git branches
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use to create a pull request with detailed summary and description
Create a git worktree for an own or someone else's branch, symlink local-only files (.env, .tmux-sessionizer), optionally install or symlink node_modules, and open it in tmux
Use this when you need to do a full workflow -- create a JIRA ticket, create a branch, create a PR, push changes
Review code changes for quality and best practices. Use when reviewing pull requests, examining code changes, or providing feedback on code quality. Covers security, performance, testing, and design review.
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Use when asked to "simplify code", "clean up code", "refactor for clarity", "improve readability", or review recently modified code for elegance. Focuses on project-specific best practices.
Generate a Playwright test based on a scenario using Playwright CLI
| name | create-branch |
| description | How to create and name git branches |
Please create branches with the following template: gonza/
If I have not given to you the branch name yet, please ask for it. If I accidentally give you the full branch name (i.e gonza/foo-bar), please discard the gonza/ part of it. Let's not end up with a branch called gonza/gonza/foo-bar
