Menu
Use when creating a pull request, opening a PR, or when work on a branch is ready for review
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
Research and save a book, video, blog post, article, paper, podcast, link, or other resource into memory. Use when the user says "/save", "save this", "remember this", "store this resource", or asks Claude to quickly research something and log it into `~/Dropbox/memory/resources/`.
Check Railway services (api/web) for errors, view logs, and fix deployment issues. Use when deployments fail, services are unhealthy, or you need to investigate production errors.
Scan an entire repository and produce a long-term improvement plan. Use when the user says "improvement plan", "/improvement-plan", "roadmap", "what should we improve", "long-term plan", "tech debt audit", "codebase review", or asks to analyze the project for future improvements, refactoring opportunities, or strategic technical direction.
Ask clarifying questions when a task is ambiguous or underspecified before implementing. Identifies missing objectives, acceptance criteria, scope, constraints, and environment details, then presents concise numbered questions with multiple-choice options and sensible defaults. Do not use automatically, only when invoked explicitly
Systematic workflow for filling out PR templates with complete documentation and analysis
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise.
| name | create-pr |
| description | Use when creating a pull request, opening a PR, or when work on a branch is ready for review |
Creates a draft PR using the repo's PR template with auto-generated content for review.
digraph create_pr {
rankdir=TB;
node [shape=box];
gather [label="1. Gather context\n(branch, diff, commits, PR template)"];
jira [label="2. Ask for Jira ticket ID"];
body [label="3. Fill in PR template\n→ show for approval"];
create [label="4. Create draft PR"];
gather -> jira -> body -> create;
}
# Get branch and base
BRANCH=$(git branch --show-current)
BASE="master" # or main
# Get diff and commits
git diff origin/$BASE...HEAD
git log origin/$BASE..HEAD --oneline
Find the repo's PR template. Search for PULL_REQUEST_TEMPLATE in these locations (in order):
.github/PULL_REQUEST_TEMPLATE.mdPULL_REQUEST_TEMPLATE.mddocs/PULL_REQUEST_TEMPLATE.mdIf found, read the template — it defines the exact sections and structure for the PR body. Use it as-is; do not add, remove, or reorder sections.
Ask user: "What is the Jira ticket ID? (e.g., PLAT-123)"
Format URL: https://tulipmfg.atlassian.net/browse/{TICKET_ID}
Using the repo's PR template as the exact structure, fill in every section by analyzing the diff and commits:
If the template has checkboxes or options to select (e.g., level of impact), select the appropriate one(s).
Show the complete filled-in PR body to the user for approval/editing before proceeding.
If no PR template is found, use a minimal structure: Summary, Jira Task, Test Plan.
Use gh pr create --draft with the approved body. Always pass the body via HEREDOC.
Always use --draft flag.
Generate concise title (under 70 chars) from:
[PLAT-123]Show to user for approval.
--draft flag