# Awesome Agentic Patterns PR Review

Review pull requests for the awesome-agentic-patterns repository.

- Repository: https://github.com/nibzard/awesome-agentic-patterns (5058 stars)
- Category: Git and review
- License: Apache-2.0
- Last updated: 2026-10-14
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add nibzard/awesome-agentic-patterns --skill awesome-agentic-patterns-pr-review -g -a claude-code -y`
Codex: `npx skills add nibzard/awesome-agentic-patterns --skill awesome-agentic-patterns-pr-review -g -a codex -y`
Cursor: `npx skills add nibzard/awesome-agentic-patterns --skill awesome-agentic-patterns-pr-review -g -a cursor -y`
Gemini CLI: `npx skills add nibzard/awesome-agentic-patterns --skill awesome-agentic-patterns-pr-review -g -a gemini-cli -y`

## Description

Review pull requests for the awesome-agentic-patterns repository. Use when asked to validate a PR, assess whether a contribution fits the repo, inspect pattern submissions under patterns/, check merge readiness, repair a small submission issue on top of a contributor branch, draft a polite contributor comment, or apply the repository's pattern-first and non-promotional contribution policy to a GitHub pull request.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Awesome Agentic Patterns PR Review

## Overview

Review PRs in this repository by applying the local contribution policy and checking the actual changed files. Treat `CONTRIBUTING.md` as the source of truth for acceptance criteria, `TEMPLATE.md` as the source of truth for expected pattern structure, and the validation scripts in `scripts/` as the source of truth for structural checks and generated-file expectations.

## Read First

- `CONTRIBUTING.md`
- `README.md`
- `TEMPLATE.md`
- `scripts/lint_front_matter.py`
- `scripts/pattern_validator.py`
- `scripts/build-data.ts` when the PR touches patterns, generated README sections, or generated site data

Do not restate repo policy from memory when those files are available. Quote or summarize the repository's own rules instead.

## Workflow

### 1. Inspect the PR

Use `gh` first:

- `gh pr view <number> --repo nibzard/awesome-agentic-patterns --json title,number,state,isDraft,author,baseRefName,headRefName,headRepository,headRepositoryOwner,maintainerCanModify,files,additions,deletions,mergeable,mergeStateStatus,reviewDecision,statusCheckRollup,labels,url,body`
- `gh pr diff <number> --repo nibzard/awesome-agentic-patterns --patch`
- `gh pr checks <number> --repo nibzard/awesome-agentic-patterns`

If you need the exact branch locally, fetch it with:

- `git fetch origin refs/pull/<number>/head:pr-<number>`

Capture these facts before deciding anything:

- Whether the PR is a new pattern submission, a pattern edit, or a broader repo/tooling change
- Whether the change correctly uses `patterns/<slug>.md` rather than editing generated docs directly
- Whether `README.md` or `apps/web/public/` generated outputs changed because the contributor regenerated outputs, or because they hand-edited generated files
- Whether `maintainerCanModify` is enabled and which fork/branch must be updated if you need to fix the PR
- Whether GitHub mergeability is trustworthy yet; `UNKNOWN` can be transient right after a push

The rest: https://github.com/nibzard/awesome-agentic-patterns/blob/HEAD/skills/pr-review/SKILL.md