Skill7.2k estrellas del repoactualizado 6d ago

github-review-follow-up

Inspect unresolved GitHub pull request review threads, group actionable feedback, implement selected fixes locally, and only reply or resolve threads after explicit user intent.

Ver fuente Repositorio: iPolloWork

Instalar en Claude Code

Copiar

git clone --depth 1 https://github.com/Devin-AXIS/iPolloWork /tmp/github-review-follow-up && cp -r /tmp/github-review-follow-up/examples/plugin-packages/github/skills/github-review-follow-up ~/.claude/skills/github-review-follow-up

Después abre una sesión nueva de Claude Code; el skill carga automáticamente.

Definición

SKILL.md

# GitHub Review Follow-up

Use this skill for requested changes, inline review comments, and unresolved Pull Request feedback.

## Workflow

1. Resolve `owner`, `repo`, and PR number from the request, URL, or current branch.
2. Call the GitHub service `pull-request-detail` and `review-threads` actions.
3. Separate the returned threads into:
   - unresolved and actionable;
   - informational or approval-only;
   - outdated, resolved, duplicate, or ambiguous.
4. Group actionable items by file or behavior and present a numbered, concise scope.
5. If the user asked to address everything, fix all clear unresolved items. Otherwise confirm which numbered items are in scope.
6. Modify the local checkout with each change traceable to its review thread.
7. Run the narrowest relevant tests and summarize what was addressed and what remains.

## Write safety

- Do not post a comment or call `resolve-review-thread` unless the user explicitly asks.
- Never mark a thread resolved before the corresponding change or explanation is complete.
- If comments conflict or would regress behavior, explain the conflict before editing.
- If the PR or repository is ambiguous, stop and request the missing target rather than guessing.

Del mismo repositorio

acme-researchSkill

Search and summarize material from the Acme research service.

agent-first-screenshotsSkill

Agent-first screenshots — an agent drives the real app via CDP and produces clean, defect-free product screenshots (newsletters, landing pages, social, decks, PR). Dual-channel verification (DOM + pixels + vision) in a capture loop. Use for any "take/redo screenshots of the app" task.

context7-docs-researchSkill

Resolve the correct library and retrieve a small, relevant set of version-aware official documentation before answering a technical question.

context7-version-aware-implementationSkill

Use the current project dependency versions and Context7 documentation to implement or upgrade code without importing APIs from a different release line.

create-pluginSkill

Create an OpenCode plugin for iPolloWork. Scaffolds the plugin file with the correct API shape, tool definitions, and hook registration. Use when the user asks to 'create a plugin', 'write a plugin', or 'make a plugin that does X'.

daytona-chrome-cdpSkill

Launch and control standalone Chrome in a Daytona sandbox via CDP. Use for web sign-in, OAuth, Den Web setup, browser-only flows, or when the app should not be driven through Electron CDP.

daytona-cloud-serverSkill

Daytona cloud server, Den sandbox, desktop plus cloud e2e, marketplace server, worker proxy, cloud auth, org policies, connect Electron to Den. Use for server-side setup in validated flows.

daytona-devSkill

Daytona development environment overview. Use when the user asks about Daytona setup, Daytona toolbox, dev environment, noVNC, CDP, server sandbox, secrets volume, Electron sandbox, standalone Chrome, validation, or artifacts volume.