Run any Skill in Manus with one click

pr-comments

Stars15

Forks7

UpdatedJune 4, 2026 at 13:28

Triage and address Dialtone GitHub PR review comments. Use when the user invokes $pr-comments, $address-review, or asks to handle review feedback.

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

dialpad

dialpad/dialtone

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

2 files

SKILL.md

readonly

name	pr-comments
description	Triage and address Dialtone GitHub PR review comments. Use when the user invokes $pr-comments, $address-review, or asks to handle review feedback.

Dialtone PR Comments

Goal

Fetch real review comments, make a grounded fix plan, implement narrowly, validate, and reply only when safe.

Trigger

$pr-comments
$address-review
"pull review comments"
"address CodeRabbit comments"
"handle PR feedback"

Required Context

PR number or current branch PR.
GitHub inline review comments, preferably via gh api repos/dialpad/dialtone/pulls/<PR>/comments when comment IDs matter.
Target files and diffs.
.agents/resources/rule-map.md
Relevant validation from .agents/resources/validation.md

Constraints

Fetch actual inline comments and IDs before planning.
Do not rely on summary comments when inline comments are available.
Plan before edits unless the user already approved a concrete plan.
Keep fixes narrowly scoped to reviewer feedback.
Do not post public replies until fixes are committed/pushed or the user explicitly asks for reply-only handling.
If public writes fail or look risky, stop and ask before retrying.

Workflow

Identify PR from input or current branch.
Fetch inline comments and group actionable top-level comments by file and line.
Classify each item as code fix, test fix, clarification, duplicate, or needs user decision.
Present a plan with comment IDs, paths, proposed actions, and validation.
Read target files before editing.
Implement narrowly and run focused validation.
Commit/push when requested.
Reply with concise evidence: what changed, commit SHA when available, and validation.

Done When

Every actionable comment is fixed, answered, deferred with reason, or awaiting a user decision.
Validation evidence is recorded.
Public replies are posted only after the safe-write boundary is satisfied.

Verification

node .agents/evals/run-skill-contract-evals.mjs
Focused validation selected from .agents/resources/validation.md

References

.agents/resources/rule-map.md
.agents/resources/validation.md

More from this repository

same repository

commit

dialpad/dialtone

Safely stage and commit Dialtone changes. Use when the user asks to stage, commit, or prepare committed work.

2026-06-0415

component-work

dialpad/dialtone

Create or update Dialtone Vue components and keep package/docs artifacts synchronized. Use when the user asks for component creation, component API changes, stories, docs, or related tests.

2026-06-0415

dialtone-lookup

dialpad/dialtone

Look up Dialtone documentation, components, tokens, utilities, and icons before making design-system decisions. Use when the user asks about Dialtone APIs, docs guidance, component usage, tokens, utilities, icons, or implementation patterns.

2026-06-0415

doc-sync-check

dialpad/dialtone

Check whether source changes need Dialtone AI docs updates. Use before PR prep/create or when source package behavior changes.

2026-06-0415

pr-complete

dialpad/dialtone

Complete merged Dialtone PR follow-up safely. Use after a PR has merged or when closing out a local PR branch.

2026-06-0415

pr-create

dialpad/dialtone

Prepare, create, or update a Dialtone pull request. Use when the user invokes $pr-create, asks to open a PR, or asks to fill a PR description.

2026-06-0415

Dialtone PR Comments

Goal

Fetch real review comments, make a grounded fix plan, implement narrowly, validate, and reply only when safe.

Trigger

$pr-comments

$address-review

"pull review comments"

"address CodeRabbit comments"

"handle PR feedback"

Required Context

PR number or current branch PR.

GitHub inline review comments, preferably via gh api repos/dialpad/dialtone/pulls/<PR>/comments when comment IDs matter.

Target files and diffs.

.agents/resources/rule-map.md

Relevant validation from .agents/resources/validation.md

Constraints

Fetch actual inline comments and IDs before planning.

Do not rely on summary comments when inline comments are available.

Plan before edits unless the user already approved a concrete plan.

Keep fixes narrowly scoped to reviewer feedback.

Do not post public replies until fixes are committed/pushed or the user explicitly asks for reply-only handling.

If public writes fail or look risky, stop and ask before retrying.

Workflow

Identify PR from input or current branch.

Fetch inline comments and group actionable top-level comments by file and line.

Classify each item as code fix, test fix, clarification, duplicate, or needs user decision.

Present a plan with comment IDs, paths, proposed actions, and validation.

Read target files before editing.

Implement narrowly and run focused validation.

Commit/push when requested.

Reply with concise evidence: what changed, commit SHA when available, and validation.

Done When

Every actionable comment is fixed, answered, deferred with reason, or awaiting a user decision.

Validation evidence is recorded.

Public replies are posted only after the safe-write boundary is satisfied.

Verification

node .agents/evals/run-skill-contract-evals.mjs

Focused validation selected from .agents/resources/validation.md

References

.agents/resources/rule-map.md

.agents/resources/validation.md