القائمة
Analyze Linear issues, validate them against the codebase, then implement fixes and create draft PRs.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/AztecProtocol/aztec-packages --skill fixيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
Reference for merge-train automation internals -- workflows, scripts, CI integration, and configuration. Use when modifying or debugging merge-train infrastructure.
Compile noir-protocol-circuits (kernels, rollup, etc.) and compute their gate counts with `bb gates`, for both the chonk (client IVC) and ultra_honk schemes. Use when asked to regenerate circuit variants, compile protocol circuits, or measure gate/circuit sizes.
Regenerate the protocol-circuit sample Prover.toml files (the witnesses CI feeds to `nargo execute`). Covers which of the two commands regenerates which tomls — the prover-client `regenerate_rollup_sample_inputs` suite for the block-root and above rollup circuits, and the e2e prover full test for the private-kernel and transaction-base circuits — and the one exception, private-kernel-reset/Prover.toml (the inner reset), which is NOT generated by the test at all and is maintained entirely by hand. Use when a `nargo execute` CI check fails on a crates/*/Prover.toml, after changing protocol-circuit inputs/constants, or when asked to refresh/regenerate Prover.toml sample inputs.
عرض SKILL.md
| 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 next using the issue's gitBranchName from Linear (or the component's merge train, see CLAUDE.md). For a fix scoped to the v5 release line, branch from v5-next instead.
git stash
git checkout -B <gitBranchName> origin/next
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 v5-next for v5-scoped fixes.
git push -u origin <gitBranchName>
gh pr create --draft --base next --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 |