Agents & OrchestrationSûr100100/100
Handle PR Comments (Storybook)
Triage and resolve GitHub PR review comments one by one, interactively. Use when the user asks to handle, address, respond to, or resolve PR review comments, or mentions reviewer feedback on a pull request.
ou envoie-le directement à ton agent.
Installer dans ton projet
$ curl -fsSL https://arboristhree.xyz/cli/install-skill.mjs -o /tmp/arboris-install-skill.mjs && node /tmp/arboris-install-skill.mjs handle-pr-comments__storybookjs-storybook__agents-skills-5826eb8265dcStorybook
storybookjs/storybook
Contenu à copier
--- name: handle-pr-comments description: Triage and resolve GitHub PR review comments one by one, interactively. Use when the user asks to handle, address, respond to, or resolve PR review comments, or mentions reviewer feedback on a pull request. metadata: origin: Storybook internal: true --- # Handle PR Comments Evaluate review comments on the PR (from the current branch, or a PR number/URL if given). For each unresolved comment: summarize the feedback, suggest a resolution, ask the user how to resolve it, apply their choice, commit if needed, and resolve the thread. 1. **Find the PR.** Use the given number/URL, else derive it from the current branch (`gh pr view`). Stop if no PR exists. 2. **Fetch unresolved review threads** via the GraphQL `reviewThreads` field on the pull request — request each thread's `id`, `isResolved`, `isOutdated`, `path`, `line`, and comments. Filter to `isResolved == false`. (Use GraphQL, not REST: only it exposes thread `id`s and resolution state.) 3. **Loop one comment at a time.** For each: (a) summarize the feedback + file/line, reading surrounding code; (b) suggest a concrete fix; (c) ask via AskQuestion with options — apply suggested fix / apply a different fix / reply only / skip; (d) apply the choice; (e) if applicable, summarize what was changed and ask whether to commit; (f) resolve the thread via the GraphQL `resolveReviewThread` mutation. 4. **Report** an overview of what was changed, committed, replied to, skipped, and resolved. Include links. ## Notes - Handle real-user comments before addressing AI agents' (Copilot, CodeRabbit). - Group duplicate comments; when the same/similar issue is mentioned multiple times, handle them all at once. - Make a separate commit for each change.
Colle ce Markdown dans ton agent ou utilise les boutons ci-dessus pour l’écrire dans ton projet.
Ce que fait Handle PR Comments (Storybook)
Handle real-user comments before addressing AI agents' (Copilot, CodeRabbit).
Group duplicate comments; when the same/similar issue is mentioned multiple times, handle them all at once.
Make a separate commit for each change.
Comment utiliser Handle PR Comments (Storybook)
1
Copie le prompt
Un clic copie le prompt packagé (ou l'envoie à ton agent).
2
L'agent installe le skill
Il ajoute le SKILL.md et ses ressources à ton projet.
3
Activation automatique
Le skill s'active dès que le contexte correspond.
Déclencheurs pour Handle PR Comments (Storybook)
Dis simplement à ton agent quelque chose comme :
Applique le skill handle-pr-comments__storybookjs-storybook__agents-skills-5826eb8265dc à cette tâche
Utilise handle-pr-comments__storybookjs-storybook__agents-skills-5826eb8265dc pour améliorer cette implémentation
Passe en revue ce sujet avec handle-pr-comments__storybookjs-storybook__agents-skills-5826eb8265dc
Skills liés à Handle PR Comments (Storybook)
Acceleration (Microsoft)
Compare synthetic acceleration options and clearly separate scenario value from forecast commitments.Account Overview (Microsoft)
Create a synthetic Acme account overview and identify evidence that merits seller attention.Acroform Writer (Microsoft)
Use this skill whenever the user wants values written INTO an existing PDF form that lives in the connected SharePoint knowledge source — filling out, completing, populating, or submitting a fillable PDF (application, intake sheet, contract, government form) from data they supply, a spreadsheet row, or the conversation. Triggers include "fill out the job application form", "complete the intake form for [person]", "populate our standard NDA template", and "make this ready to send / non-editable" (flatten). The source form should be found via knowledge search; only ask the user to upload it if knowledge search turns up nothing plausible. different task), and do NOT use it on scanned/image-only PDFs that have no real fillable fields — those need OCR or manual overlay instead, which this skill explicitly detects and reports rather than silently failing.