Menu
Commit, push, and open a pull request for the current changes. Invoke explicitly with /pr.
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
Load when building, editing, or debugging Mako React apps — app files, npm dependencies, data bindings, the @mako/app-sdk hooks (useQuery / useDuckDB / useLocation / useSearchParams / navigate), URL state and shareable deep links, materialized Parquet/DuckDB bindings, and the live preview runtime.
Load for dbt branches, commits, pushes, pull requests, merges, repository sync, or branch cleanup.
Load when creating, editing, scheduling, running, or debugging dbt jobs and production deployments.
Load when building, editing, running, or debugging dbt models, dbt projects, schema.yml tests, sources, seeds, snapshots, incremental models, materializations, or dbt jobs in the Transforms section.
Load when creating, editing, configuring, validating, or debugging database sync flows, connector flows, pagination, incremental sync, destination mappings, and flow form fields.
Add a new MCP server preset (connector) to Mako's MCP client system — server URL, auth model (OAuth DCR, pre-registered app, or API key), scopes, icon, tests, and docs. Use when connecting a new external MCP server (like Slack or Close CRM) or changing how MCP connections authenticate.
| name | pr |
| description | Commit, push, and open a pull request for the current changes. Invoke explicitly with /pr. |
| disable-model-invocation | true |
Inspect changes: Run git diff to see all staged and unstaged changes. Run git status to see untracked files.
Stage relevant files: Add changed and new files. Skip files that shouldn't be committed (.env, dist/, node_modules/).
Write a commit message: Based on the actual diff, write a clear commit message:
feat:, fix:, refactor:, chore:, docs:Commit and push:
git add <files>
git commit -m "feat: description of change"
git push -u origin HEAD
Create the PR:
gh pr create --title "feat: description" --body "$(cat <<'EOF'
## Summary
- What changed and why
## Test plan
- [ ] How to verify
EOF
)"
Return the PR URL to the user.
master directly..env, credentials, or dist/ files.git diff first to understand the actual changes before writing the commit message.Before git commit / opening a PR, run full lint for every package you touched (CI is stricter than local hooks; Prettier violations fail ESLint as prettier/prettier):
| You changed files under... | Run |
|---|---|
app/ | pnpm --filter app run lint (and pnpm --filter app run typecheck if TS changed) |
api/ | pnpm --filter api run lint |
Fix all reported errors; do not push with "fix CI later" lint failures.