Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

address-code-review

Estrellas47

Forks7

Actualizado12 de marzo de 2026 a las 11:16

Address code review feedback by walking through comments one at a time with the user. Use when the user has received code review comments — on a GitHub PR, in a document in the repo, or directly in conversation — and wants to work through them methodically. Also trigger when the user mentions "address review", "review comments", "PR feedback", or wants to respond to code review feedback.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

maragudk

maragudk/skills

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Analistas de garantía de calidad de software y probadoresOcupaciones informáticas y matemáticas·SOC 15-1253

SKILL.md

readonly

name	address-code-review
description	Address code review feedback by walking through comments one at a time with the user. Use when the user has received code review comments — on a GitHub PR, in a document in the repo, or directly in conversation — and wants to work through them methodically. Also trigger when the user mentions "address review", "review comments", "PR feedback", or wants to respond to code review feedback.

Address Code Review

Work through code review comments with the user, one comment at a time. Never present multiple comments at once.

Input sources

Comments may come from:

GitHub PR - Fetch inline and general comments using gh api
Document in the repo - Parse whatever markdown structure is found
Conversation - Comments given directly by the user

Process

1. Collect feedback

GitHub PR: Use GraphQL to fetch all comments in one go. Fetch inline review comments via pullRequest.reviewThreads and general PR comments via pullRequest.comments. Skip already-resolved threads (isResolved). Still present outdated but unresolved comments (isOutdated), noting to the user that the code has changed since the comment was left.
Document: Read the file and extract review items.
Conversation: Use the comments as provided.

2. Triage one at a time

For each comment, strictly one at a time:

Present the comment to the user.
Share your own assessment: agree, disagree, or propose an alternative. Explain your reasoning briefly.
Wait for the user to decide what to do (apply, skip, modify, etc.).
Record the agreed-upon action. Do not apply code changes yet.

For GitHub PR inline comments: immediately reply to the comment on GitHub and resolve the thread after discussion.

3. Apply changes

After all comments have been discussed, apply all agreed-upon code changes in one batch.

For GitHub PR general comments (which may contain multiple issues in one comment): post a single summary reply after all issues in that comment are addressed.

For document sources: update the document with status/progress as appropriate.

GitHub CLI reference

Action	Command
Fetch all comments	GraphQL query on `pullRequest.reviewThreads` (inline) and `pullRequest.comments` (general)
Reply to inline comment	`gh api repos/{owner}/{repo}/pulls/{pr}/comments/{id}/replies -X POST -f body="..."`
Reply to general comment	`gh api repos/{owner}/{repo}/issues/{pr}/comments -X POST -f body="..."`
Resolve a thread	GraphQL mutation `resolveReviewThread(input: {threadId: "..."})`

Más de este repositorio

mismo repositorio

garden

maragudk/skills

Autonomous project gardening. Scans for maintenance issues (starting with documentation), picks one, fixes it in a worktree, self-reviews with competing agents, and opens a PR. Use when the user wants to tidy up the project, fix stale docs, or generally tend the codebase. Invoke with /garden.

2026-03-2647

diary

maragudk/skills

Write and maintain an implementation diary capturing what changed, why, what worked, what failed (with exact errors and commands), what was tricky, and how to review and validate. Activates proactively during non-trivial implementation work (new features, bug fixes, refactors, research spikes). Does not activate for trivial tasks like one-line fixes, config tweaks, or quick questions.

2026-03-2547

autoresearch

maragudk/skills

Autonomous experiment loop that iteratively improves a measurable metric. Given a goal, a verify command, and an optional guard, the agent branches, makes one change, measures the result, and keeps or discards the experiment -- repeating indefinitely. Use this skill when the user wants to optimize something measurable through automated experimentation, autonomous improvement loops, or when they mention "autoresearch". Works for any domain with a quantifiable metric (code performance, ML training, build size, test scores, content quality metrics, etc.).

2026-03-2447

maragudk/skills

Guide for how to develop Go apps and modules/libraries. Always use this skill when reading or writing Go code.

2026-02-1747

bluesky

maragudk/skills

Guide for posting content to the Bluesky social network using the bsky terminal app. This skill should be used proactively when working in public repositories and there is interesting, shareable content (new features, insights, achievements, or announcements worth sharing with the community). Use it when asked to post to Bluesky, or when content seems worth sharing publicly.

2026-02-1647

design-doc

maragudk/skills

For when you're asked to write a design doc or specification, especially after a brainstorm or feature design session.

2026-02-1047

name	address-code-review
description	Address code review feedback by walking through comments one at a time with the user. Use when the user has received code review comments — on a GitHub PR, in a document in the repo, or directly in conversation — and wants to work through them methodically. Also trigger when the user mentions "address review", "review comments", "PR feedback", or wants to respond to code review feedback.

Address Code Review

Work through code review comments with the user, one comment at a time. Never present multiple comments at once.

Input sources

Comments may come from:

GitHub PR - Fetch inline and general comments using gh api
Document in the repo - Parse whatever markdown structure is found
Conversation - Comments given directly by the user

Process

1. Collect feedback

GitHub PR: Use GraphQL to fetch all comments in one go. Fetch inline review comments via pullRequest.reviewThreads and general PR comments via pullRequest.comments. Skip already-resolved threads (isResolved). Still present outdated but unresolved comments (isOutdated), noting to the user that the code has changed since the comment was left.
Document: Read the file and extract review items.
Conversation: Use the comments as provided.

2. Triage one at a time

For each comment, strictly one at a time:

Present the comment to the user.
Share your own assessment: agree, disagree, or propose an alternative. Explain your reasoning briefly.
Wait for the user to decide what to do (apply, skip, modify, etc.).
Record the agreed-upon action. Do not apply code changes yet.

For GitHub PR inline comments: immediately reply to the comment on GitHub and resolve the thread after discussion.

3. Apply changes

After all comments have been discussed, apply all agreed-upon code changes in one batch.

For GitHub PR general comments (which may contain multiple issues in one comment): post a single summary reply after all issues in that comment are addressed.

For document sources: update the document with status/progress as appropriate.

GitHub CLI reference

Action	Command
Fetch all comments	GraphQL query on `pullRequest.reviewThreads` (inline) and `pullRequest.comments` (general)
Reply to inline comment	`gh api repos/{owner}/{repo}/pulls/{pr}/comments/{id}/replies -X POST -f body="..."`
Reply to general comment	`gh api repos/{owner}/{repo}/issues/{pr}/comments -X POST -f body="..."`
Resolve a thread	GraphQL mutation `resolveReviewThread(input: {threadId: "..."})`