summarize-pr

Summarize a GitHub pull request — purpose, key changes, review state, CI status, and outstanding blockers. Use when the user pastes a PR URL (github.com/<org>/<repo>/pull/<n>), references a PR by number (e.g. "PR

Aller à l'installation

Dépôt: Blazemeter/claude-base
Dernière activité de la source: 29 juin 2026 à 05:14
Langue détectée de SKILL.md: anglais
Étoiles: 1
Forks: 1

Options d'installation

Le prompt qui vérifie d'abord la source est sélectionné par défaut. Vous pouvez passer à une commande directe ou télécharger une copie locale.

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.

npx skills add https://github.com/Blazemeter/claude-base --skill summarize-pr

La commande reste sur une seule ligne. Faites défiler horizontalement pour la vérifier avant de la copier.

Vous préférez une copie locale ? Téléchargez les fichiers actuellement disponibles dans SkillsMP.

Vérifiez les fichiers source

Lisez SKILL.md et les fichiers associés affichés par SkillsMP avant de décider de l'installer.

Explorateur de fichiers

2 fichiers

SKILL.md

Instructions source · Aperçu en lecture seule

Retour à la recherche Retour à l’installation

constraint-engineering

Use when a team wants to apply the Constraint Engineering guideline to a feature or repo — audits the current repo against an 8-item build checklist (spec-first, small checked steps, right-sized models, fast checks, an independent reviewer, isolated workspaces, hard safety rules, tracked outcomes), and generates copy-ready, stack-adapted template files. Trigger phrases — "apply constraint engineering", "help me write a spec for this feature", "audit this repo against the constraint engineering checklist", "set up an independent AI reviewer", "is this repo AI-SDLC S2 or S3 ready".

2026-08-24

design-rationale

Produce a Design Rationale section for a design/spec/architecture artifact — justifying OOP/SOLID application, which design pattern(s) were considered and chosen (or why none applies), and which collection/data-structure was picked for each non-trivial data need, with the complexity/performance tradeoff that justifies it. Asks the developer clarifying questions when a structural choice (concurrency, cardinality, mutability, ordering, hot-path-vs-cold-path) is a genuine judgment call, rather than guessing. Language-agnostic — works for Java, Python, JavaScript/TypeScript, or any other stack. Use whenever a pipeline is about to lock in a design/spec for non-trivial work (new module, service, class hierarchy, data pipeline), or when a developer explicitly asks for a design/architecture review, "why this data structure", or "apply SOLID/design patterns here". Do NOT use for one-line fixes or purely mechanical changes with no structural decisions to make.

2026-07-27

file-doc-task

File or update a documentation-planning JIRA task for a customer-facing feature, using the documentation team's standard template. Idempotent create-or-update — safe to run early (draft a DOC-ready ticket from the specs/design to guide development) and again at finalize (reconcile the description against what was actually shipped). For FEATURE or USER-FACING work the skill first asks once whether the change needs customer-facing documentation, and only creates the ticket if it does. Also use when a developer explicitly asks to "create a doc task", "file a docs ticket", "DOC-ready ticket", "update the doc task", or hand work off to the documentation team. Do NOT use for pure refactors, internal-only fixes, or build/dependency chores.

2026-07-08

Tout voir dans ce dépôt

name	summarize-pr
description	Summarize a GitHub pull request — purpose, key changes, review state, CI status, and outstanding blockers. Use when the user pastes a PR URL (github.com/<org>/<repo>/pull/<n>), references a PR by number (e.g. "PR
allowed-tools	Bash(gh *), Read
effort	low

summarize-pr

Produce a concise, structured summary of a GitHub pull request. The goal is to let the user decide what to do about the PR without opening the browser — purpose, scope, review state, blockers, recommendation.

When to use

User pastes a PR URL like https://github.com/<org>/<repo>/pull/123.
User refers to a PR by number — "summarize PR 123", "what's in 123", "is 123 ready".
User asks for the state of a PR they own or are reviewing.

When NOT to use

Reviewing a local diff or working tree — use a code-review skill.
Deep CI failure investigation — use a CI-investigation skill.
Non-GitHub PRs (GitLab merge requests, Bitbucket PRs).

Preconditions

gh CLI installed and authenticated. If gh auth status fails, tell the user to run gh auth login and stop.
For private repos, the user's gh token must have repo access.

summarize-pr

Options d'installation

Vérifiez les fichiers source

summarize-pr

When to use

When NOT to use

Preconditions

Workflow

summarize-pr

When to use

When NOT to use

Preconditions

Workflow

Output format

Notes

Related

summarize-pr

Informations de source

Options d'installation

Vérifiez les fichiers source

Plus depuis ce dépôt

Plus depuis ce dépôt

summarize-pr

When to use

When NOT to use

Preconditions

Workflow

summarize-pr

When to use

When NOT to use

Preconditions

Workflow

Output format

Notes

Related