Peqy

Review peqy bot comments on a PR and assess their validity against the codebase

PublishedMay 30, 2026

Loading actions...

5 minBeginnerprompt4 files

Skill content

Main instructions and any bundled files for this skill.

markdown

Additional Files (3)

Review the comments left by peqy[bot] on a pull request and assess whether each comment is valid, actionable, and consistent with the codebase's existing patterns.

Steps

Determine the PR number:
- If $ARGUMENTS is provided, use it as the PR number
- Otherwise, detect the current branch and find its open PR using gh pr view --json number
Fetch all review comments from peqy using:
```
gh api repos/rhesis-ai/rhesis/pulls/{PR_NUMBER}/comments
```
Filter to comments from peqy[bot].
For each comment:
- Read the file and lines referenced in the comment
- Investigate the surrounding codebase for existing patterns and conventions
- Assess validity considering:
  - Does the suggestion match existing patterns in the codebase?
  - Would applying it introduce inconsistency (e.g. adding a comment only in one place when the same pattern exists uncommented elsewhere)?
  - Is the concern real or theoretical?
  - Does it conflict with project conventions in CLAUDE.md?
- Classify as: Valid (worth fixing), Marginal (technically correct but not worth changing), or Invalid (wrong or inconsistent with codebase)
Present a summary table:

# Comment File Verdict Reasoning
For comments classified as Valid, ask the user if they want them applied.

Contents

View Original Source

Related Skills

General

PromptBeginner5 minmarkdown

Untitled Skill

193

Jan 12, 2026

General

PromptBeginner5 minmarkdown

Frontend Typescript Linting.mdc

TypeScript and ESLint rules that MUST be followed when creating, modifying, or reviewing any file under apps/frontend/, including .ts, .tsx, .js, and .jsx files. Also apply when discussing frontend li...

160

Feb 15, 2026

General

PromptBeginner5 minmarkdown

2. Apply Deepthink Protocol (reason about dependencies

risks

127

Jan 15, 2026