Menu
Create a pull request with a concise, useful description
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
Run validation checks - determines whether to use fast (validate) or full (validate:full) based on changed files
Security code review for vulnerabilities. Use when asked to "security review", "find vulnerabilities", "check for security issues", "audit security", "OWASP review", or review code for injection, XSS, authentication, authorization, cryptography issues. Provides systematic review with confidence-based reporting.
Create and manage isolated Docker workspaces on your tailnet with Claude Code and OpenCode pre-installed. Use when working with Perry workspaces, connecting to coding agents, or managing remote development environments.
React and Next.js performance optimization guidelines from Vercel Engineering. Contains 45+ rules across 8 categories.
Cut a new release - bump version, commit, tag, and push to trigger CI publish
| name | create-pr |
| description | Create a pull request with a concise, useful description |
Create pull requests with concise, useful descriptions.
Use format: <type>: <short description>
Types: fix, feat, refactor, docs, chore, test
Examples:
fix: handle null user in session lookupfeat: add workspace pause/resumerefactor: extract terminal manager from agentKeep it short. 2-5 bullet points max.
## Summary
- <what changed>
- <why it changed>
- <any notable decisions or tradeoffs>
That's it. No "Test Plan", no "Screenshots", no checklists unless truly needed.
Check changed files:
git diff --name-only main...HEAD
Run validation:
bun run validate
Fix any issues found by validation before proceeding
Create PR (only after validation passes):
gh pr create --title "<type>: <description>" --body "$(cat <<'EOF'
## Summary
- <what>
- <why>
EOF
)"
Only add extra sections if genuinely useful: