Menú
Analyze Linear issues, validate them against the codebase, then implement fixes and create draft PRs.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Spot-check the health of a live Aztec network deployment by sweeping recent GCP logs for warn/error messages, mapping each to the deployed code, classifying expected vs unexpected, and verifying the hard invariants (no slashing, no attestation timeouts, no unexplained prunes/conflicts). Use when asked to "spot-check", "review logs", or "health check" a network (staging, testnet, devnet, ...) over a recent window.
Reference for merge-train automation internals -- workflows, scripts, CI integration, and configuration. Use when modifying or debugging merge-train infrastructure.
Build and update the developer documentation site for a new release
Guide for working with merge-train branches -- creating PRs, choosing the right base branch, understanding labels, handling failures, and bypassing checks.
Create a well-formed Linear issue — with complete context for a fresh agent, a point estimate (1/2/3/5), and acceptance criteria. Works standalone or as part of planning a project with multiple issues. Use when asked to file/create/open a Linear issue, "make a ticket", or when breaking a plan into tracked work.
Build or adjust a Linear cycle — for a whole team or just yourself. Size capacity from last-3-cycle velocity, fill with backlog bugs/high-priority items first and project work after (in your chosen project focus order), with no unassigned issues. Use when planning/prepping a cycle for a team, or when one member wants to fill/rebalance their own cycle work.
| name | fix |
| description | Analyze Linear issues, validate them against the codebase, then implement fixes and create draft PRs. |
| argument-hint | <issue-numbers, e.g. A-690 A-691 A-692> |
Given a list of Linear issue numbers, analyze each one against the codebase, then implement fixes and create draft PRs.
For each issue number provided:
mcp__linear-server__get_issue.| Issue | Title | Verdict | Reasoning |
|---|---|---|---|
| A-XXX | ... | Valid / Invalid / Unclear | One-line explanation |
mcp__linear-server__save_issue.Work through each confirmed issue sequentially in the main checkout:
Stash & branch: Stash any uncommitted changes, then create a branch from merge-train/spartan using the issue's gitBranchName from Linear. For a fix scoped to the v5 release line, branch from merge-train/spartan-v5 (which targets v5-next) instead.
git stash
git checkout -B <gitBranchName> origin/merge-train/spartan
Implement the fix: Edit the relevant files.
Build: Run yarn build from yarn-project to verify the fix compiles.
Commit: Stage only the changed files and commit with a descriptive message.
fix: <short description> (A-XXX)Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>Push & PR: Push the branch and create a draft PR. Use --base merge-train/spartan-v5 for v5-scoped fixes.
git push -u origin <gitBranchName>
gh pr create --draft --base merge-train/spartan --title "fix: ..." --body "..."
Fixes A-XXX).Return to original branch: Switch back and restore stashed changes before moving to the next issue.
git checkout <original-branch>
git stash pop
Repeat for each issue.
Report a summary table with the PR URL for each issue, or what went wrong if any failed.
| Issue | Title | PR |
|---|---|---|
| A-XXX | ... | URL or error |