newcomer-issue-explainer
De la autor
Given an open good-first-issue on the configured `<upstream>` repo, explain it in beginner terms and sketch a concrete approach: which files to read first, what "done" looks like, and where to ask follow-up questions — without writing any code. First confirms the issue is open, non-security, and scope-clear, then drafts the explanation for maintainer review. Posts nothing without explicit maintainer confirmation.
Instalare
npx skills add apache/magpie --skill newcomer-issue-explainer -a claude-code
Se instalează în .claude/skills/newcomer-issue-explainer/ · Fiecare comandă descarcă skill-ul direct de pe GitHub cu utilitarul open source skills.
Identic octet cu octet cu commit-ul scanat, cu licența depozitului și un fișier SOURCE.txt.
Vrei ca agentul să-ți propună skill-uri în timp ce scrii? Vezi cum folosești skill-urile din IDE.
Verificări de siguranță pe SKILL.md
- Conține text ascuns (caractere invizibile, comentarii lungi sau blocuri codificate)Mediu
De ce 75
aiqbench calculează scorul de încredere din semnale publice. Nu este un audit de securitate, așa că citește un skill înainte să-l instalezi.
Skill-uri similare
Cele mai apropiate de acesta prin ce fac și când sunt folosite.
- good-first-issue-authorapache/magpieDraft one net-new *good first issue* on the configured `<upstream>` repo from one supplied gap or small maintainer-named task. Run suitability and readiness checks before showing the draft. File via `gh` only after explicit maintainer confirmation. Never curate or relabel the existing backlog.Productivitate★ 126
- upstream-firstmgifford/accessibility-skillsLoad this skill before implementing a fix for a barrier that may originate in a shared component, design system, renderer, or external dependency rather than this project's own code. Decide whether the responsible fix is local, an existing installed capability, or an upstream contribution before writing a workaround. Absolutely always record any temporary local divergence with an owner and removal condition. Under no circumstances open, comment on, or submit anything in an external project without explicit human approval.Design★ 57
- welcomeapache/magpieDraft a first-contact orientation comment for a first-time contributor on a newly opened issue or PR on the configured `<upstream>` repo. Detects first-time authorship via the GitHub `author_association` field and drafts a welcome with contributing-guide link, community-norm pointers, and expected next steps. Waits for explicit maintainer confirmation before posting. Does not post for repeat contributors.Altele★ 126
- issue-fixapache/magpieFix a tracked security issue in a public `<upstream>` PR: sync the tracker, propose a plan, and on confirmation write the change, open the PR from the user's fork (on Subversion: share a private patch and commit once the team clears it), and update the tracker. Public content never reveals the CVE or the security nature of the change.Securitate★ 126
- issue-import-from-prapache/magpieOpen a tracker for a security-relevant fix that already exists as a public `<upstream>` PR, with no `<security-list>` report. The tracker lands in `Assessed` with scope, PR-state and remediation fields filled from the PR; pairs with `security-cve-allocate`.Securitate★ 126
- code-reviewapache/magpieWalk a maintainer through deep, sequential code review of open PRs on the configured `<upstream>` repo. Defaults to the **"my reviews"** queue (five maintainer signals — see the Inputs table); selectors narrow to one PR, an area label, or a collaborator subset. Drafts an `approve` / `request-changes` / `comment` review per PR and posts on confirmation.Inginerie★ 126
Note și recenzii
—
nicio recenzie
Ai încercat acest skill? Notează-l ca să-i ajuți pe alții. Autentifică-te
Discuție
Intră în discuție. Autentifică-te