address-pr-comments
Triage pull-request feedback, implement justified changes, and draft evidence-backed replies.
AMY PELLEGRINI’S WORKFLOW / SKILLS & AGENTS
These are the skills and agents I use in my own development workflow. I’m sharing them in case they’re useful to you, too. There are rough edges, and I keep refining them as I learn what works. Feel free to borrow, adapt, and make them your own.
Install a skill01 / EXPLORE
One maintained definition per workflow. Skills discover your project’s tools and conventions; agent definitions provide optional Claude Code orchestration.
24 entries
Triage pull-request feedback, implement justified changes, and draft evidence-backed replies.
Audit the repository’s CI coverage against its documented quality requirements and report evidence-backed gaps.
Inspect local commit hooks and report what they enforce, how they run, and where checks can be bypassed.
Assess test distribution and meaningful coverage using the repository’s own testing strategy.
Refine or triage issues into clear business value, scope, acceptance criteria, and verification steps.
Inspect checks on a pull request’s current commit and report a clear CI verdict.
Verify completion and merge an authorized pull request before confirming its issue is resolved.
Create focused Git commits with accurate messages and verification appropriate to the change.
Commit the requested changes and push the intended branch while respecting remote and branch protections.
Demonstrate work in progress, collect criterion-level feedback, and preserve what was actually reviewed.
Drive a scoped feature through implementation, validation, and a reviewable handoff using the target repository’s conventions.
Open a pull request with a focused description, the correct base branch, and relevant validation evidence.
Coordinate multiple independent work items with isolated working trees and explicit per-item handoffs.
Review multiple pull requests in isolated checkouts and combine findings into a ranked report.
Prepare an issue for implementation by checking requirements, repository context, and a suitable working branch.
Create, inspect, close, or reopen an iteration or project board using the target project’s own workflow.
Coordinate either a repository quality assessment or acceptance-criteria verification of a specific feature.
Run a combined assessment of test strategy, CI coverage, and commit hooks, then consolidate actionable findings.
Verify a feature against its acceptance criteria on the actual implementation and record reproducible evidence.
Draft release notes from a verified release scope for the intended audience and distribution channel.
Guide a human acceptance review of a specific build and record explicit criterion-level decisions.
Implement one acceptance criterion through a verified red, green, and refactor cycle using the project’s test tools.
Coordinate scoped feature development and return validated, reviewable changes without assuming a particular repository or stack.
Assess repository quality or verify feature behavior with reproducible evidence while leaving implementation code unchanged.
Try a broader search or clear the filters.
02 / MAKE IT YOURS
Use Vercel’s Skills CLI with Node.js and npm installed. Run commands inside the project where you want the skill. These commands target the published library repository; use the local path below before publication.
Preview the library before installing a skill. This lists the skills available in the library.
npx skills add amypellegrini/amypellegrini.github.io --listEach entry has a command. Choose a target with --agent claude-code, --agent codex, or --agent pi, or use the interactive selection. Add --global for your user account; omit it for the current project.
npx skills add amypellegrini/amypellegrini.github.io --skill tdd --agent claude-codeList installed skills, or use npx skills update to update them later.
npx skills listFrom the root of this website repository, you can preview the maintained skills without publishing:
npx skills add ./skills --listThe CLI installs SKILL.md packages. Claude Code agent definitions belong in your project’s .claude/agents/ directory. Open an agent entry to download its file and see its destination. Installing the dev or qa skill does not also install its agent.
Skills discover the repository, default branch, test commands, tracker, and workflow states from your project. Boards, devices, and companion agents are optional unless the task needs them. Install only the workflows you use; each includes a fallback when a companion skill is absent.
03 / MAINTAINED TOGETHER
These workflows make no assumptions about your organization, product, programming language, branch names, or board columns. They preserve the useful discipline: focused changes, evidence-backed testing, clear review, and explicit human acceptance.
Each skills/<name>/SKILL.md is a self-contained workflow. Edit it here, or adapt an installed copy to your project.
The dev and qa definitions coordinate workflows in Claude Code. Portable skills can also run directly without these agents.
The JSON registry records categories, file paths, SHA-256 checksums, source links, and install commands.
Definitions are maintained in this library. Refreshing the registry indexes those files; it never re-imports instructions from another project.