issue-import
De la autor
Import new `<security-list>` reports into `<tracker>`: find threads not yet tracked, propose the imports (default: import unless rejected), create each tracker in `Needs triage`, and draft a receipt reply to the reporter. First step of the handling process.
Instalare
npx skills add apache/magpie --skill issue-import -a claude-code
Se instalează în .claude/skills/issue-import/ · 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.
- issue-import-from-mdapache/magpieOpen one or more `<tracker>` tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the `Needs triage` board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.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
- issue-invalidateapache/magpieClose a tracker as invalid: label, closing comment, board archive, and — for `<security-list>` imports — a polite-but-firm reply draft to the reporter with the team's reasoning. No reporter outreach for trackers imported from a public PR.Securitate★ 126
- issue-syncapache/magpieSynchronize a security issue in <tracker> with the state of its GitHub discussion, the <security-list> mailing thread, and any <upstream> PRs that fix it. The skill gathers all relevant signals and proposes label / milestone / assignee / field / draft-email updates — applying only what the user has explicitly confirmed. Suggests the next step in the handling process and prints the CVE allocation link when a CVE is needed.Securitate★ 126
- issue-triagepaperclipai/paperclipTriage Paperclip inbox issues that are stale, blocked, in-review, or assigned-but-not-progressing, and decide a single next action per issue (resume, reassign, unblock, escalate, or close).Inginerie★ 107.1K
- 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
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