Run any Skill in Manus with one click

Get Started

$pwd:

triage-reviews

Name: Triage Reviews
Author: stickerdaniel

// Fetch PR review comments, verify each against real code/docs, fix valid issues, commit and push

Run Skill in Manus

$ git log --oneline --stat

stars:37

forks:10

updated:March 29, 2026 at 09:10

SKILL.md

readonly

name	triage-reviews
description	Fetch PR review comments, verify each against real code/docs, fix valid issues, commit and push
disable-model-invocation	true
argument-hint	[PR number]

Triage PR Review Comments

Fetch all review comments on the current PR, verify each finding against real code, fix valid issues, and push.

Phase 1: Gather Comments

Determine the PR number:
- Use $ARGUMENTS if provided
- Otherwise: gh pr view --json number --jq .number

Fetch ALL comments (reviewers post in multiple places):

gh api --paginate repos/{owner}/{repo}/pulls/{pr}/reviews
gh api --paginate repos/{owner}/{repo}/pulls/{pr}/comments
gh api --paginate repos/{owner}/{repo}/issues/{pr}/comments

Extract unique findings — deduplicate across Copilot, Greptile, and human reviewers. Group by file and line.

Phase 2: Verify Each Finding

For EVERY finding, verify against real code before accepting or rejecting:

Read the actual code at the referenced file:line
Check if the issue still exists — it may already be fixed in a later commit
Verify correctness using:
- Code analysis (read surrounding context, trace call paths)
- Run btca resources to see what's available, then btca ask -r <resource> -q "..." for library/framework questions
- Web search for API behavior, language semantics, or CVEs
Classify each finding:
- Valid — real bug, real gap, or real improvement needed
- False positive — reviewer misread the code, outdated reference, or style preference

Phase 3: Fix & Ship

Fix all Valid findings
Run the project's lint/test commands (check CLAUDE.md for exact commands)
- If lint/tests fail, fix the failures before committing
- If a failure cannot be fixed automatically, skip that fix and report it as Valid (unfixed) in the Phase 4 table

git add only changed files, git commit with message:

fix: Address PR review feedback

- <one-line summary per fix>

Push: gt submit (or git push if not using Graphite)

Phase 4: Report

Present a final summary table of ALL findings with verdicts:

#	Source	File:Line	Finding	Verdict	Reason

Notes

Never dismiss a finding without reading the actual code first
If unsure, err toward "Valid" — it's cheaper to fix than to miss a bug
For library/API questions, always use btca or web search — don't guess

related-skills.json

same repository

saas-starter.md

from "stickerdaniel/saas-starter"

A brief description of what this skill does

2026-05-3137

pair-review.md

from "stickerdaniel/saas-starter"

Iterativer Plan-Review-Loop mit OpenAI Codex als zweiter Meinung. Use when the user runs /pair-review, asks for cross-model verification of a plan file in ~/.claude/plans/, or — most importantly — before calling ExitPlanMode in plan mode to validate the proposed plan with adversarial review.

2026-05-1737

autumn-best-practices.md

from "stickerdaniel/saas-starter"

Skill for integrating Autumn - the billing and entitlements layer over Stripe.

2026-03-2937

emil-design-eng.md

from "stickerdaniel/saas-starter"

This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.

2026-03-1937

convex-guidelines.md

from "stickerdaniel/saas-starter"

Canonical Convex backend coding patterns — validators, function registration, queries, mutations, actions, schemas, pagination, cron jobs, file storage, and Better Auth integration. Use when writing or reviewing any Convex backend code.

2026-03-1937

svelte-form-builder.md

from "stickerdaniel/saas-starter"

Workflow for generating form JSON and using the Svelte Form Builder (svelte-form-builder.vercel.app) to scaffold SvelteKit remote function forms with Valibot validation. Use when creating forms via the form builder.

2026-03-1937

package.json

"author": "stickerdaniel"

"repository": "stickerdaniel/saas-starter"

View GitHub Repository View Creator Repositories

$ install --global

$ download --local

Run Skill in Manus

$ useful --forSOC

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations15-1253L4

Triage PR Review Comments

Fetch all review comments on the current PR, verify each finding against real code, fix valid issues, and push.

Phase 1: Gather Comments

Determine the PR number:

Use $ARGUMENTS if provided
Otherwise: gh pr view --json number --jq .number

Fetch ALL comments (reviewers post in multiple places):

gh api --paginate repos/{owner}/{repo}/pulls/{pr}/reviews
gh api --paginate repos/{owner}/{repo}/pulls/{pr}/comments
gh api --paginate repos/{owner}/{repo}/issues/{pr}/comments

Extract unique findings — deduplicate across Copilot, Greptile, and human reviewers. Group by file and line.

Phase 2: Verify Each Finding

For EVERY finding, verify against real code before accepting or rejecting:

Read the actual code at the referenced file:line

Check if the issue still exists — it may already be fixed in a later commit

Verify correctness using:

Code analysis (read surrounding context, trace call paths)
Run btca resources to see what's available, then btca ask -r <resource> -q "..." for library/framework questions
Web search for API behavior, language semantics, or CVEs

Classify each finding:

Valid — real bug, real gap, or real improvement needed
False positive — reviewer misread the code, outdated reference, or style preference

Phase 3: Fix & Ship

Fix all Valid findings

Run the project's lint/test commands (check CLAUDE.md for exact commands)

If lint/tests fail, fix the failures before committing
If a failure cannot be fixed automatically, skip that fix and report it as Valid (unfixed) in the Phase 4 table

git add only changed files, git commit with message:

fix: Address PR review feedback

- <one-line summary per fix>

Push: gt submit (or git push if not using Graphite)

Phase 4: Report

Present a final summary table of ALL findings with verdicts:

Source

File:Line

Finding

Verdict

Reason

Notes

Never dismiss a finding without reading the actual code first

If unsure, err toward "Valid" — it's cheaper to fix than to miss a bug

For library/API questions, always use btca or web search — don't guess

triage-reviews

Triage PR Review Comments

Phase 1: Gather Comments

Phase 2: Verify Each Finding

Phase 3: Fix & Ship

Phase 4: Report

Notes

More from this repository

More from this repository

Triage PR Review Comments

Phase 1: Gather Comments

Phase 2: Verify Each Finding

Phase 3: Fix & Ship

Phase 4: Report

Notes