القائمة
Create or update a GitHub pull request with ticket context, synchronized branch history, and a concrete test plan.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Tensorlake SDK — sandboxes for AI agents and applications. Use when the user mentions tensorlake or sandboxes, or asks about Tensorlake APIs/docs/capabilities. Also use when building an application, coding agent, or agentic system that needs a sandbox to run code — e.g., executing LLM-generated or untrusted code, persistence via suspend/resume, snapshots/checkpoints for forking parallel workers, custom images, exposing ports, egress allowlists, PTY/interactive shells, computer-use / desktop automation, browser automation (Chrome CDP, Playwright), local tunnels for non-HTTP protocols, async parallel sandboxes, Harbor evals or RL rollouts, file transfer, SSH access, remote-dev (VS Code Remote-SSH), or OCI base images. Also covers Tensorlake's sandbox-native durable workflow orchestration. Works alongside any LLM provider (OpenAI, Anthropic), agent framework (Claude/OpenAI agents SDK, LangChain), database, or API. When this skill applies, ALWAYS WebFetch https://docs.tensorlake.ai/llms.txt first.
Ship Tribunal to production and triage deployment, health-check, Fly, Neon, GitHub OAuth/App, Tensorlake, proxy, review-engine, or live-review rollout issues. Use when a user asks to deploy Tribunal, prepare production secrets, verify production readiness, enable live reviews, debug broken deploys, inspect production health, or recover/rollback Tribunal services.
Ship Tribunal to production and triage deployment, health-check, Fly, Neon, GitHub OAuth/App, Tensorlake, proxy, review-engine, or live-review rollout issues. Use when a user asks to deploy Tribunal, prepare production secrets, verify production readiness, enable live reviews, debug broken deploys, inspect production health, or recover/rollback Tribunal services.
Address unresolved GitHub pull request review comments by analyzing feedback, implementing fixes, and resolving threads.
Generate or refresh a multi-agent project context document and execution-plan authoring prompt from repository analysis. Use when bootstrapping multi-agent orchestration, updating architecture/ownership/contracts guidance, or preparing a reusable planning prompt. Support explicit output path (`OUTPUT=<path>` or plain-language path request); otherwise detect a sensible default path from the project structure.
Stage intended changes, validate them, and create a focused commit with a clear, ticket-aware message.
| name | create-pr |
| description | Create or update a GitHub pull request with ticket context, synchronized branch history, and a concrete test plan. |
| context | fork |
| agent | git-ninja |
| allowed-tools | Read, Grep, Glob, AskUserQuestion, mcp__linear__get_issue, mcp__linear__update_issue, mcp__linear__create_comment, Bash(bun*run scripts/extract-ticket-from-branch.ts:*), Bash(git status:*), Bash(git branch:*), Bash(git fetch:*), Bash(git rebase:*), Bash(git merge:*), Bash(git log:*), Bash(git diff:*), Bash(git push:*), Bash(gh pr:*), Bash(gh api:*), Bash(bun run check:*) |
Be sure to prefix the pull request title with the ticket identifier.
TICKET if supplied, otherwise extract from branch:!bun --cwd "$(git rev-parse --show-toplevel)" run scripts/extract-ticket-from-branch.ts
!git status
!git branch --show-current
If the working tree is not clean, stop and commit first using /commit.
origin/main before creating the pull request:!git fetch origin
You must sync the branch with the latest origin/main using the best strategy for the current state (for example: rebase, fast-forward merge, or merge).
Complete this sync before opening or updating the pull request.
git log origin/main..HEAD --oneline
bun run check
Do not open or update a pull request while local checks fail.
If Linear MCP is available, fetch ticket details:
mcp__linear__get_issue({ id: "TEAM-27" })
Extract:
Title format: TEAM-XX: Brief description
gh pr create --title "TEAM-27: Add user profile settings" --body "$(cat <<'EOF'
## Summary
Brief description of what this PR does.
- Bullet points of key changes
## Linear
Closes TEAM-27
## Test plan
- [ ] Manual testing steps
- [ ] Automated tests added/updated
EOF
)"
If a pull request already exists for the branch, update it instead of creating a duplicate:
gh pr edit --title "TEAM-27: Add user profile settings" --body-file /tmp/pull-request-body.md
Before creating or updating the pull request:
origin/mainbun run check passes locallyIf creating a new branch, include the ticket:
git checkout -b feature/TEAM-27-brief-description
If Linear MCP is available, update the ticket:
/commit: produce clean, focused commits before this command./create-pr: requires a synced branch and passing local checks before opening or updating a pull request./address-pr: follows the same sync-first approach and commit quality standards while resolving feedback.Before opening or updating a pull request, run a Codex MCP code review and address all requested changes.