Menü
Open a pull request with conventional title, structured description, and pre-flight checks.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Prepare a code branch and pull/merge request for human review through safe rebasing, repository-specific validation, multiple independent subagent review rounds, evidence-based fixes, conventional commits, pushing, PR creation, and CI babysitting. Use when asked to prepare, polish, or finalize a PR/MR; obtain several reviews; iterate until clean; or make a branch ready for human review.
Debug an `imprint teach` run — env vars, CLI flags, log files, tracing, and diagnostic commands. Helps diagnose slow, stuck, or failing teach runs.
Refresh checked-in examples from generated Imprint site tools and cut an Imprint patch release. Use when the user asks to commit new generated tools to examples, replace stale example tool snapshots, update example docs/tests after generated tool repairs, or publish a patch release after example/runtime fixes.
Audit and repair generated Google Flights Imprint tools. Use when validating Google Flights search, calendar, booking, airline/bag filters, one-way, round-trip, multi-city, or open-jaw behavior; when investigating `selection_token` or `selected_flights` producer-consumer contracts; or when live audit results are slow, bot-sensitive, under-tested, or incorrectly waived as infrastructure.
Investigate a site's auth-tool compile — ongoing or completed. Locate the real agent transcript (not just the hook log), read the live 2FA verification, inspect the emitted workflow.json, confirm the login actually completed, and diagnose "no auth tool compiled".
Cut a new semver release — bumps package.json, previews changelog, commits, tags, pushes, and verifies npm publish.
| name | pr |
| version | 1.0.0 |
| description | Open a pull request with conventional title, structured description, and pre-flight checks. |
| triggers | ["pr","pull request","open pr"] |
| allowed-tools | ["Bash","Read"] |
Open a pull request for the current branch with proper conventions.
Run these in parallel and report results:
bun run lint
bun run typecheck
bun test
If any fail, show the errors and ask the user whether to proceed or fix first.
Run these to understand the branch:
git branch --show-current — current branch namegit log main..HEAD --oneline — commits on this branchgit diff main..HEAD --stat — files changedThe PR title must be a conventional commit format: <type>(<scope>): <description>
Pick type and scope the same way as the /commit skill, but based on the overall branch intent (not individual commits).
Use this structure:
## Summary
- Bullet 1: what changed and why
- Bullet 2: key design decisions
- Bullet 3: anything reviewers should pay attention to
## Test plan
- [ ] Tests pass locally
- [ ] Specific scenario tested
Run git remote -v and git rev-parse --abbrev-ref --symbolic-full-name @{u} 2>/dev/null to check if the branch is pushed.
If not pushed, run git push -u origin <branch>.
gh pr create --title "<title>" --body "$(cat <<'EOF'
<body>
EOF
)"
Show the PR URL to the user when done.