en un clic
stellar-dev-skill-pr-review
stellar-dev-skill-pr-review contient 2 skills collectées depuis kaankacar, avec une couverture métier par dépôt et des pages de détail sur le site.
Skills dans ce dépôt
Work through the issues assigned to the user on the stellar/stellar-dev-skill repo (the AI-skills repo behind skills.stellar.org): find the open issues assigned to them, pick one (or go oldest-first), understand what it asks, create a branch, implement a best-effort fix following the repo's conventions — skill content, site code, or catalog cards — verify it (Raven fact-checks, compile checks, pnpm build), commit, and automatically open a PR that links the issue and flags any assumptions — then hand the new PR to the stellar-dev-skill-pr-review skill for review. Use whenever the user asks you to work on / solve / fix / clear the issues assigned to them on stellar-dev-skill, or turn a specific stellar-dev-skill issue into a PR. This is the write-and-open-PR counterpart to stellar-dev-skill-pr-review (which only reviews existing PRs). Do NOT use for reviewing/merging PRs, for stellar/stellar-docs (that's stellar-docs-issue-solver), or for issues that need a product/design decision rather than a change you can i
Review pull requests on the stellar/stellar-dev-skill repo (the AI-skills repo behind skills.stellar.org) as a maintainer would. Works two ways: given a specific PR URL/number, evaluate just that one; or given no specific PR, find every PR awaiting the user's review and work through them one at a time. For each PR: pull context, classify what it touches (skill content, site code, ecosystem cards, CI), verify it the right way for that class (Raven fact-checks, compile-against-real- crates, pnpm build, preview or local render), then approve + merge when confident, comment and hand off when something needs a human, or close duplicates — giving a very short report after each PR before the next. Use whenever the user pastes a stellar-dev-skill PR link, or asks you to review/triage/clear the PRs waiting on them on stellar-dev-skill or skills.stellar.org. Do NOT use for stellar/stellar-docs (that's stellar-docs-pr-review), for writing new skills, or for opening PRs from issues (that's stellar-dev-skill-issue-solver)