What is pr-reviewer?
Automated GitHub PR code review with diff analysis, lint integration, and structured reports. Supports Go, Python, and JavaScript/TypeScript.
yun520-1/mark-heartflow-skill
Automated GitHub PR code review with diff analysis, lint integration, and structured reports. Use when reviewing pull requests, checking for security issues, error handling gaps, test coverage, or code style problems. Supports Go, Python, and JavaScript/TypeScript. Requires `gh` CLI authenticated with repo access.
npx skills add https://github.com/yun520-1/mark-heartflow-skill --skill "skills/pr-reviewer"Quick start
Install it or open the source, trigger it with a clear task, then follow the source workflow.
npx skills add https://github.com/yun520-1/mark-heartflow-skill --skill "skills/pr-reviewer"Use pr-reviewer to help me with: [describe your task]. Before you begin, tell me what input you need, the steps you will follow, and the expected output.
No structured workflow was detected; follow the original SKILL.md below.
Continue to the workflowDirect answers
Automated GitHub PR code review with diff analysis, lint integration, and structured reports. Supports Go, Python, and JavaScript/TypeScript.
It is relevant to workflows involving Code review, Testing, Engineering, Research.
SkillSignal detected this source-specific command: npx skills add https://github.com/yun520-1/mark-heartflow-skill --skill "skills/pr-reviewer". Inspect the repository and command before running it.
The upstream source does not declare a dedicated Agent platform.
Static analysis detected read-files signals. Review the cited source lines before installing; these signals are not a security audit.
This page combines upstream documentation with deterministic repository, quality, and static-risk signals. It is not described as a manual test or security review.
SkillSignal brief
Automated GitHub PR code review with diff analysis, lint integration, and structured reports. Supports Go, Python, and JavaScript/TypeScript.
Useful in these contexts
Core capabilities
Distilled from the source
About 2 min · 10 sections
Use when reviewing pull requests, checking for security issues, error handling gaps, test coverage, or code style problems.
Quality breakdown
Based on traceable docs and repository signals; stars are not treated as quality.
Compare before choosing
These links are selected from shared tasks, functions, stacks, platforms, and same-name variants. Compare the source owner, documentation, permissions, and maintenance signals.
Systematic code error diagnosis and fix skill. Handles compilation errors, runtime exceptions, type errors, logic bugs, crash analysis, dependency conflicts, and unexpected behavior. TRIGGER when: user reports an error/exception/bug/crash, build or test failures, unexpected behavior in code, type errors, runtime stack traces, dependency resolution failures, or asks "why is this not working" / "fix this error" / "debug this". DO NOT TRIGGER when: user asks for code review without errors, general
Analyzes code diffs and files to identify bugs, security vulnerabilities (SQL injection, XSS, insecure deserialization), code smells, N+1 queries, naming issues, and architectural concerns, then produces a structured review report with prioritized, actionable feedback. Use when reviewing pull requests, conducting code quality audits, identifying refactoring opportunities, or checking for security issues. Invoke for PR reviews, code quality checks, refactoring suggestions, review code, code quali
Multi-agent orchestration using dmux (tmux pane manager for AI agents). Patterns for parallel agent workflows across Claude Code, Codex, OpenCode, and other harnesses. Use when running multiple agent sessions in parallel or coordinating multi-agent development workflows.
Multi-agent orchestration using dmux (tmux pane manager for AI agents). Patterns for parallel agent workflows across Claude Code, Codex, OpenCode, and other harnesses. Use when running multiple agent sessions in parallel or coordinating multi-agent development workflows.
Universal SQL code review assistant that performs comprehensive security, maintainability, and code quality analysis across all SQL databases (MySQL, PostgreSQL, SQL Server, Oracle). Focuses on SQL injection prevention, access control, code standards, and anti-pattern detection. Complements SQL optimization prompt for complete development coverage.
Automated code review for GitHub pull requests. Analyzes diffs for security issues, error handling gaps, style problems, and test coverage.
gh CLI installed and authenticated (gh auth status)golangci-lint for Go linting, ruff for Python linting# Review all open PRs in current repo
scripts/github/pr-reviewer.sh check
# Review a specific PR
scripts/github/pr-reviewer.sh review 42
# Post review as GitHub comment
scripts/github/pr-reviewer.sh post 42
# Check status of all open PRs
scripts/github/pr-reviewer.sh status
# List unreviewed PRs (useful for heartbeat/cron integration)
scripts/github/pr-reviewer.sh list-unreviewed
Set these environment variables or the script auto-detects from the current git repo:
PR_REVIEW_REPO — GitHub repo in owner/repo format (default: detected from gh repo view)PR_REVIEW_DIR — Local checkout path for lint (default: git root of cwd)PR_REVIEW_STATE — State file path (default: ./data/pr-reviews.json)PR_REVIEW_OUTDIR — Report output directory (default: ./data/pr-reviews/)PR_REVIEW_STATE (default: ./data/pr-reviews.json) — Tracks reviewed PRs and their HEAD SHAsPR_REVIEW_OUTDIR (default: ./data/pr-reviews/) — Markdown review reports| Category | Icon | Examples |
|---|---|---|
| Security | 🔴 | Hardcoded credentials, AWS keys, secrets in code |
| Error Handling | 🟡 | Discarded errors (Go _ :=), bare except: (Python), unchecked Close() |
| Risk | 🟠 | panic() calls, process.exit() |
| Style | 🔵 | fmt.Print/print()/console.log in prod, very long lines |
| TODOs | 📝 | TODO, FIXME, HACK, XXX markers |
| Test Coverage | 📊 | Source files changed without corresponding test changes |
Tracks HEAD SHA per PR. Only re-reviews when new commits are pushed. Use review <PR#> to force re-review.
Reports are saved as markdown files in the output directory. Each report includes:
Add to a periodic check (heartbeat, cron job, or CI):
UNREVIEWED=$(scripts/github/pr-reviewer.sh list-unreviewed)
if [ -n "$UNREVIEWED" ]; then
scripts/github/pr-reviewer.sh check
fi
The analysis patterns in the script are organized by language. Add new patterns by appending to the relevant pattern list in the analyze_diff() function:
# Add a new Go pattern
go_patterns.append((r'^\+.*os\.Exit\(', 'RISK', 'Direct os.Exit() — consider returning error'))