القائمة
Use when implementation is complete and the user asks to raise, create, open, prepare, or update a PR for an existing Linear issue in this repository
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | raising-linear-pr |
| description | Use when implementation is complete and the user asks to raise, create, open, prepare, or update a PR for an existing Linear issue in this repository |
| argument-hint | [issue-id-or-branch] |
Move completed implementation work into review. This skill owns final branch sync, PR-phase gates, post-rebase validation, stale targeted eval decisions, push, PR creation or update, and the Linear In Review transition.
| Step | Requirement |
|---|---|
| 1 | Verify the worktree is clean and expected implementation commits exist |
| 2 | Fetch and rebase onto the default branch before final verification |
| 3 | Review the committed code, tests, and verification evidence before any AC decision |
| 4 | Run the acceptance-criteria gate from references/acceptance-criteria-gate.md |
| 5 | Run the design conformance gate from references/design-conformance-gate.md |
| 6 | Run changed-area validation and stale targeted eval decisions |
| 7 | Push the prepared branch |
| 8 | Create or update the PR |
| 9 | Move the Linear issue to In Review only after the PR exists |
In Review if any acceptance criterion is incomplete, unproven, blocked, or requires code/test/docs work.Use references/acceptance-criteria-gate.md for AC mechanics and
references/design-conformance-gate.md for design-conformance mechanics.
The key rules:
pass, fail, or not_applicable with checked paths.implementing-linear-issue when ACs, design conformance, validation, or evals reveal implementation work.Run repo validation commands from repo-map.json for the changed area.
Use references/promptfoo-db-gate.md for stale targeted eval decisions. Do not run the full promptfoo suite by default. Run targeted evals when DB evidence is missing or stale; skip only when the latest fully passing DB run is newer than the latest content-relevant Git change.
Use references/git-and-pr.md for branch sync, push, PR create/update, issue-linking, and boundary rules.
Tool contract: use repo test commands from repo-map.json, git status, git push, gh pr list, gh pr create, gh pr edit, gh pr view, gh pr checks, and the available Linear MCP tools needed for issue and comment operations. Retry once on tool failure, then stop and report the exact failing step.
closing-linear-issue for merge and cleanup.In Review before the PR exists.references/acceptance-criteria-gate.md — AC gate mechanicsreferences/design-conformance-gate.md — design conformance mechanicsreferences/promptfoo-db-gate.md — stale targeted eval decisions and helper usagereferences/git-and-pr.md — branch sync, push, PR body, and phase boundariesUse when reviewing a vd-studio pull request as the automated AI PR reviewer (OpenHands pr-review plugin) — judging test coverage for a diff, structuring the review report, or deciding merge readiness.
Use when test quality decisions are needed for new, changed, brittle, missing, or review-requested unit or component tests, including tests-first work, assertion choice, mock boundaries, lifecycle scenarios, or independent test-session handoff.
Use when filing, logging, raising, reporting, or submitting a product issue, feature request, bug, or feedback for the Studio or Utilities product areas in Linear.
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
Compact the current conversation into a handoff document for another agent to pick up.
Use when asked to implement, fix, build, or work on an existing Linear issue in this repository, and coding should stop before PR creation