Menü
Analyze Linear issues, validate them against the codebase, then implement fixes and create draft PRs.
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
| 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 |
Build and update the developer documentation site for a new release
Collect and aggregate e2e test wall-clock timings — run the suite with the timing instrumentation on, find the per-worker JSONL it produces, and print per-test sums plus a ranked span leaderboard. Use when asked to measure, profile, or break down where the e2e suite spends time.
Monitor a PR on a ~10-minute loop and drive it to green and conflict-free — watch CI, dispatch fixers for failures (new commits, never amend), and resolve base conflicts (rebase by default, merge if the branch already merged the base). Stop and report when the PR is green with no conflicts.
Determine which git commit an Aztec network (next-net, devnet, staging) is running now or was running at a past time T, and whether a specific fix or PR is live on it. Use for incident triage ("was the fix deployed when X happened?"), confirming a fix reached a network, or identifying the exact deployed commit.
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.
Run realistic Chonk (client IVC) benchmarks using pinned protocol inputs. Covers native and WASM proving, per-circuit breakdowns, BB_BENCH instrumentation, and profiling code augmentation. Use when asked to benchmark, profile, or measure Chonk proving performance.