// Use when creating a pull request. Runs verification, reviews changes, and creates the PR with correct metadata. Invoke BEFORE pushing code.
| name | pr-creation |
| description | Use when creating a pull request. Runs verification, reviews changes, and creates the PR with correct metadata. Invoke BEFORE pushing code. |
| allowed-tools | ["Read","Edit","Write","Bash","Glob","Grep","mcp__conductor__GetWorkspaceDiff"] |
| metadata | {"internal":true} |
Follow these steps in order when creating a pull request. Do not skip any step.
bun run verify
This runs type checking, linting, and tests across the monorepo.
Do NOT proceed if verification fails. Fix issues first, then re-run.
Use mcp__conductor__GetWorkspaceDiff with stat: true to see all changed files, then review the full diff to understand the scope of changes.
Stage and commit all changes. Follow any user instructions about commit message style.
-u flag if the branch has no upstreamfeat: | fix: | docs: | style: | refactor: | perf: | test: | build: | ci: | chore: | revert:gh pr create --base main with:
gh pr create --base main --title "title here" --body "$(cat <<'EOF'
## Summary
- bullet points describing changes
## Test plan
- [ ] testing steps
🤖 Generated with [Claude Code](https://claude.com/claude-code)
EOF
)"
CRITICAL - Invoke BEFORE writing ANY test code. Use when creating new tests, adding test cases, modifying existing tests, writing `it()` or `describe()` blocks, or touching any `*.test.ts` or `*.spec.ts` file. Enforces no try-catch in positive tests, no early returns, no test skipping.
Environment variable management patterns. CRITICAL use when adding new environment variables (secrets, API keys, config), debugging "X not defined" or missing env var errors, tests passing locally but failing in CI, Turborepo not passing env vars to tasks, or troubleshooting deployment configuration errors.
Test the local Rudel API with authenticated requests. Use when the user wants to test API endpoints, debug RPC calls, verify auth flows, or inspect API responses against the local dev server.
TypeScript coding standards. Use when writing TypeScript, reviewing code, or refactoring. Enforces named exports, no dynamic imports, discriminated unions, proper type safety.
Query ClickHouse databases using the chcli CLI tool. Use when the user wants to run SQL queries against ClickHouse, explore database schemas, inspect tables, or extract data from ClickHouse.
Code architecture patterns. Use when organizing code, refactoring classes, designing service structure, or extracting/moving code to new files. Enforces function ordering, service functions over classes, dependency injection.