Run any Skill in Manus with one click

address-comments

Stars5

Forks2

UpdatedApril 7, 2026 at 07:10

Address unresolved review comments on the current pull request, asking the user to choose when multiple valid resolutions exist, then validate, commit, push, and resolve the comments that were fixed. Use only when the user explicitly invokes $address-comments.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

chasinglogic

chasinglogic/dotfiles

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

File Explorer

2 files

SKILL.md

readonly

name	address-comments
description	Address unresolved review comments on the current pull request, asking the user to choose when multiple valid resolutions exist, then validate, commit, push, and resolve the comments that were fixed. Use only when the user explicitly invokes $address-comments.

Address Comments

Overview

Review unresolved pull request feedback, implement the selected fixes, verify the result with tests and linting where available, and then commit, push, and resolve the comments that were addressed.

Workflow

Inspect the current pull request and gather the unresolved review comments or requested changes.
Group comments by file and theme so related fixes can be handled together.
If a comment can be addressed in multiple materially different ways, stop and ask the user which approach to take before editing.
Implement the agreed fixes without disturbing unrelated work.
Run the relevant test and lint commands for the affected area. If there is no obvious command, inspect the repository tooling and choose the appropriate validation commands.
Commit the changes with a focused commit message and push the branch.
Resolve only the comments that were actually addressed.

Decision Rules

Ask the user before choosing between competing valid interpretations of review feedback.
Do not resolve a thread unless the underlying concern was addressed in code or explicitly deferred with user approval.
If validation fails, fix the issue before committing, or stop and report the blocker if it cannot be resolved safely.

GitHub Notes

Prefer GitHub-aware tools and workflows when available for comment inspection and thread resolution.
Work from unresolved comments only; avoid reopening resolved review history unless it is directly relevant.

More from this repository

same repository

commit

chasinglogic/dotfiles

Create one or more atomic git commits from the current worktree, choosing ticket-prefixed summaries when the branch name contains a ticket identifier and falling back to conventional commit prefixes otherwise. Use only when the user explicitly invokes $commit to prepare, commit, and optionally push current changes.

2026-04-075

chasinglogic/dotfiles

Create a GitHub pull request for the current branch targeting the repository default branch, using a ticket-based title when the branch includes a ticket identifier and a description that explains what changed and why. Use only when the user explicitly invokes $pr.

2026-04-075

review

chasinglogic/dotfiles

Review the current branch diff against the repository integration branch, preferring `origin/develop` when it exists and otherwise using `origin/main`, then examine the changed files through frontend, backend, and infrastructure lenses as applicable and synthesize findings into one prioritized report. Use only when the user explicitly invokes $review to run a manual code review.

2026-04-075

name	address-comments
description	Address unresolved review comments on the current pull request, asking the user to choose when multiple valid resolutions exist, then validate, commit, push, and resolve the comments that were fixed. Use only when the user explicitly invokes $address-comments.

Address Comments

Overview

Review unresolved pull request feedback, implement the selected fixes, verify the result with tests and linting where available, and then commit, push, and resolve the comments that were addressed.

Workflow

Inspect the current pull request and gather the unresolved review comments or requested changes.
Group comments by file and theme so related fixes can be handled together.
If a comment can be addressed in multiple materially different ways, stop and ask the user which approach to take before editing.
Implement the agreed fixes without disturbing unrelated work.
Run the relevant test and lint commands for the affected area. If there is no obvious command, inspect the repository tooling and choose the appropriate validation commands.
Commit the changes with a focused commit message and push the branch.
Resolve only the comments that were actually addressed.

Decision Rules

Ask the user before choosing between competing valid interpretations of review feedback.
Do not resolve a thread unless the underlying concern was addressed in code or explicitly deferred with user approval.
If validation fails, fix the issue before committing, or stop and report the blocker if it cannot be resolved safely.

GitHub Notes

Prefer GitHub-aware tools and workflows when available for comment inspection and thread resolution.
Work from unresolved comments only; avoid reopening resolved review history unless it is directly relevant.