Menu
Create a branch from unstaged changes, commit with conventional message, and open a PR. Use when user wants to quickly ship current work.
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
This skill should be used when the user asks to "onboard", "analyze this repo", "understand this codebase", "familiarize yourself", "what is this project", or needs to deeply understand a codebase's architecture, patterns, and conventions before starting work.
Analyze the current repo deeply and suggest agentic workflows tailored to its architecture, patterns, and pain points. Use when user calls /aw-planner.
Read a GitHub issue with all comments and linked content to add as working context. Use when the user provides a GitHub issue URL or reference.
Generate a comprehensive manual testing guide for completed work, with note sections for user feedback that the agent reviews afterward. Use when the user wants to manually test changes before shipping.
Review PR comments, validate which are actionable and correct, and propose fixes for valid ones. Use when user wants to address feedback on a pull request.
Convert Markdown text to Zendesk-compatible HTML. Use when user needs to format content for Zendesk tickets, macros, triggers, or automations.
| name | branch-and-pr |
| description | Create a branch from unstaged changes, commit with conventional message, and open a PR. Use when user wants to quickly ship current work. |
Create a new branch, commit current changes, and open a pull request in one workflow.
git status and git diff to understand what changed{username}/{type}-{short-description}
git config user.name (lowercase, no spaces)git checkout -b {branch-name}git add -A{type}: {description} (max 72 chars)gh pr createtype: lowercase descriptionfix: handle null user in auth middlewarefeat: add dark mode toggle to settingsrefactor: extract validation logic to helperWrite like a human developer, not an AI:
Brief 1-2 sentence summary of what this does.
- Bullet points for specific changes if needed
- Keep it scannable
Tested by [how you verified it works]
Avoid:
Good examples:
Before pushing, show:
Branch: {branch-name}
Commit: {commit-message}
Changes to be pushed:
{file list}
Ready to push and create PR? (y/n)
Wait for explicit user confirmation before proceeding.