Pr Review

Name: Pr Review
Author: proffesor-for-testing

proffesor-for-testing/agentic-qe

131 installs
433 repo stars
Updated August 4, 2026
proffesor-for-testing/agentic-qe

Conduct structured pull-request reviews for agentic-qe changes—coverage, flake risk, n8n graph safety, and docs—before merge to main.

About

pr-review from proffesor-for-testing/agentic-qe provides a disciplined pull-request review framework for automation and agent changes, emphasizing tests, flake risk, workflow safety, and documentation before merge.

Structured PR review checklist
Emphasizes test and flake risk
Covers n8n and agent change surfaces
Improves merge confidence
Pairs with test-automation-strategy

Pr Review by the numbers

131 all-time installs (skills.sh)
+3 installs in the week ending Aug 4, 2026 (Skillselion tracking)
Ranked #395 of 1,352 Code Review & Quality skills by installs in the Skillselion catalog
Data as of Aug 5, 2026 (Skillselion catalog sync)

npx skills add https://github.com/proffesor-for-testing/agentic-qe --skill pr-review

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

[![Listed on Skillselion](https://skillselion.com/badge/skills/proffesor-for-testing/agentic-qe/pr-review.svg)](https://skillselion.com/skills/proffesor-for-testing/agentic-qe/pr-review)

Installs	131
repo stars	★ 433
Last updated	August 4, 2026
Repository	proffesor-for-testing/agentic-qe ↗

What it does

Conduct structured pull-request reviews for agentic-qe changes—coverage, flake risk, n8n graph safety, and docs—before merge to main.

Files

SKILL.mdMarkdownGitHub ↗

PR Review Workflow

Review pull requests with correct AQE scope boundaries, clear communication, and actionable feedback.

Arguments

<pr-number> — GitHub PR number to review. If omitted, prompt the user.

Steps

1. Read the Full Diff

gh pr diff <pr-number>
gh pr view <pr-number>

Read the complete diff and PR description. Do not skim — read every changed file.

2. Scope Check

Only analyze AQE/QE skills (NOT Claude Flow platform skills)
Platform skills to EXCLUDE: v3-, flow-nexus-, agentdb-, reasoningbank-, swarm-, github-, hive-mind-advanced, hooks-automation, iterative-loop, stream-chain, skill-builder, sparc-methodology, pair-programming, release, debug-loop
If the PR touches skills, verify the count/scope matches expectations (~82 AQE skills)
Flag any platform skill changes that may have leaked into an AQE-focused PR

3. Summarize Changes

Write a user-friendly summary of what changed and why:

Focus on outcomes, not implementation details
Avoid overly technical jargon
Keep it to 3-5 bullet points

4. Trust Tier Validation

For any skill changes, validate trust_tier assignments:

tier 3 = has eval infrastructure (evals/, schemas/, scripts/)
tier 2 = tested but no eval framework
tier 1 = untested
Flag inconsistencies (e.g., a skill with evals at tier 2 should be tier 3)

5. Code Quality Review

Check for:

Hardcoded version strings
Production safety concerns (adapter changes, breaking changes)
Missing test coverage for new code
Security issues (exposed secrets, injection risks)

6. Post Review

gh pr review <pr-number> --body "review comments"

Communication Rules

Keep tone constructive and actionable
Be outcome-focused: what should the author do, not what's wrong
Group related comments together instead of posting many small ones
If approving with minor suggestions, use APPROVE with comments, not REQUEST_CHANGES