Przejdź do treści
Biblioteka skilli
Programowanie · Przegląd i audyt

pr-standards

/pr-standards

Pilnuje standardów tworzenia pull requestów, linkowania zgłoszeń i komentarzy oraz zakładania zgłoszeń na GitHubie.

Licencja
Apache-2.0
Ostatnia zmiana repozytorium
12.11.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
1
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
2
Przestarzałość

Brak sygnałów. Repozytorium zmienione 12.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

Co robi i kiedy

Pilnuje standardów tworzenia pull requestów, linkowania zgłoszeń i komentarzy oraz zakładania zgłoszeń na GitHubie.

Oryginalny opis (EN)

Use when creating PRs, linking issues, managing PR comments, or creating GitHub issues

Jak działa

  1. PR Creation Guards
  2. Workaround Classification
  3. Issue-PR Bidirectional Linking
  4. AI Mention Policy
  5. Commit, PR Title & PR Description Style
  6. GitHub Issue Standards
  7. Related Skills
Sekcje z nagłówków SKILL.md, w oryginale · 201 linii, 1 001 słów
Podgląd SKILL.md
---
name: pr-standards
description: Use when creating PRs, linking issues, managing PR comments, or creating GitHub issues
---

# PR & Issue Standards

## PR Creation Guards

Run these checks in order before `gh pr create`. Replace `<default>` with the
repo's actual default branch — `main` on a trunk repo, `develop` on a git-flow
repo (see `gh-cli-patterns`, github-workflows, for detection).

> [!IMPORTANT]
> For Git Flow repositories, feature and bugfix PRs must always target `develop`.
> You must also add a checklist item to the session plan to merge `develop` into
> `main` (using `/promote-release`) before wrapping up the session.

Stacked PRs are not exempt: the guards and standards below apply to every layer.
Because `gh stack submit` creates the PRs (rather than `gh pr create`), run the
guards before submitting and apply the body rules afterward. See `pr-stacks`
(github-workflows).

**Guard 1 — Check for merged twin** (prevents zombie PRs):

```bash
gh pr list --repo JacobPEvans/<repo> --state merged --head <branch> --limit 5 --json number,url
```

If merged PR exists AND `git log origin/<default>..HEAD --oneline` is empty:
STOP. Remove stale worktree.

**Guard 2 — Check for existing open PR** (prevents duplicates):

```bash
gh pr list --repo JacobPEvans/<repo> --state open --head <branch> --limit 5 --json number,url
```

If open PR exists: `git push origin <branch>` instead of creating new PR.

**Guard 3 — Find related issues** (enforces linking):

```bash
gh issue list --repo JacobPEvans/<repo> --state open --search "<keywords>" --limit 20 --json number,title,url
```

Include `Closes #X` or `Related to #X` in PR body. After creation:
`gh issue comment <num> --body "Implementation: #<pr>"`.
This guard only searches GitHub issues — code/repo defects. If the PR resolves
an operational incident, reference the Zammad ticket in prose instead (see
Issue-PR Bidirectional Linking below).

**Guard 4 — Validate branch has commits**:

```bash
git log origin/<default>..HEAD --oneline
```

If empty: no new work. Clean up instead.

## Workaround Classification

When reviewing a PR, distinguish a real fix from a workaround. Workarounds
become permanent tech debt if merged without acknowledgement. Four red flags:

1. **No upstream issue cited**: PR body does not name a specific upstream
   bug, version, or repository where the underlying problem lives.
2. **Phantom remediation mechanism**: PR body claims an automated "sync
   workflow", "auto-update", or "re-trigger" mechanism — verify with
   `grep -r <name> .` in the repo; if zero matches, the mechanism does not
   exist and the inline copy will drift silently.
3. **Asymmetric application**: the change is local to 1 of N similar
   consumers of a shared pattern (e.g. inlines 1 of 6 cross-repo imports),
   with no written rationale for the asymmetry.
4. **No exit criterion**: PR does not name the condition under which this
   workaround can be removed (upstream version, infrastructure change,
   deprecation date).

**Three or more red flags → recommend close, not merge.** Workarounds get an
upstream issue and an exit criterion before merging, or they are rejected.

Origin: 2026-05-22 `ansible-splunk` PRs #216 (asymmetric inline of 1 of 6
imports, references a non-existent sync mechanism) and #218
(cron-retrigger band-aid with no exit criterion). Both reached
`mergeStateStatus: CLEAN` and would have merged under a mechanical-gate
review.

## Issue-PR Bidirectional Linking

Every PR body must include (bot PRs exempt):

```markdown
## Related Issues
Closes #X
```

Use `Closes #X` for full resolution (auto-closes on merge).
Use `Related to #X` for partial.

If the PR also resolves an operational incident, add a `Zammad: <full ticket
URL>` line alongside `Closes #X`. GitHub's auto-close syntax does not reach
Zammad — update the ticket separately (`zammad_update_ticket` when that MCP
tool is available, otherwise the REST update in `track-followups` step 1).

## AI Mention Policy

**NEVER tag AI assistants in PR comments** unless explicitly requesting
assistance. Do not tag to acknowledge fixes, notify of changes, or thank
for feedback. Just resolve the thread.

Exception: explicit requests like
`@gemini-code-assist review the security implications of this change`.

## Commit, PR Title & PR Description Style

Canonical conventions (no emoji, Conventional Commits, `feat:` vs `fix:`):
[docs.jacobpevans.com/conventions/commit-conventions](https://docs.jacobpevans.com/conventions/commit-conventions).

PR-specific additions: prefixes apply to commit subjects and PR titles
only — PR descriptions and release notes are plain prose. Applies to all
PRs — human, AI-assisted, and bot-authored automated fixes.

## GitHub Issue Standards

GitHub Issues track code, config, and repo defects/features — the fix lives in
a repository. Operational incidents (production/infrastructure anomalies,
RCAs, postmortems, runbook-worthy events) are not GitHub issues — they are
Zammad tickets (`#NNNNN`, the org's incident system of record). If what you're
filing describes something that broke or degraded in production rather than a
defect in this repo, it belongs in Zammad instead.

### Title Prefixes

| Prefix | Use Case |
| --- | --- |
| `[FEATURE]` | New functionality |
| `[BUG]` | Something broken |
| `[DOCS]` | Documentation changes |
| `[REFACTOR]` | Code improvements |
| `[Small Batch]` | Scoped 1-2 week work |

### Required Labels

**Type** (pick one): `bug`, `enhancement`, `documentation`, `question`
**Priority** (pick one): `priority:critical`, `priority:high`,
`priority:medium`, `priority:low`
**Size**: `size:xs` (<1d), `size:s` (1-3d), `size:m` (3-5d),
`size:l` (1-2w), `size:xl` (2+w)

### Feature Issue Template

```markdown
## Problem
**Raw idea**: [concept]
**Current pain**: [what's broken]
**Size**: [xs|s|m|l|xl]

## Solution Sketch
**Core concept**: [approach]
**Out of scope**: [boundaries]

## Rabbit Holes
- [complexity traps to avoid]

## Done Looks Like
- [ ] Acceptance criterion

## Verification Steps
- [ ] How to verify

## Metadata
**Related Issues**: Blocks: #XX / Blocked by: #YY / Related to: #ZZ
```

### Bug Issue Template

```markdown
## What Happened
[Expected vs actual]

## Steps to Reproduce
1. Step one

## Context
**Environment**: [details]

## Done Looks Like
- [ ] Bug no longer occurs
- [ ] Regression test added

## Verification Steps
- [ ] Reproduce steps no longer trigger bug
```

Every issue MUST have explicit, checkbox-format acceptance criteria.

## Related Skills

- **rebase-pr** (git-workflows) — Rebase-merge workflow for merging approved PRs
- **finalize-pr** (github-workflows) — Finalize PR state before merging
- **git-workflow-standards** (git-workflows) — Branch and worktree conventions that feed into PRs
- **pr-stacks** (github-workflows) — stack submission and merge tracking
- **gh-cli-patterns** (github-workflows) — Canonical default-branch detection (trunk vs git-flow)
- For branch creation and PR-branch sync, follow the [Git Town rule](https://github.com/dryvist/ai-llm-prompts/blob/main/auto-ai-agent/instructions/agentsmd/rules/on-demand/git-flow.md).

Wersje

RepozytoriumWynikLicencja
Ta strona · JacobPEvans/claude-code-plugins100Apache-2.0
dryvist/claude-code-plugins100Apache-2.0

Migawka bazy z 13.11.2026 · wersja paczki fae8a6752255 (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100github-cli-media
    Dołącza lokalne obrazy i wideo do zgłoszeń, pull requestów i komentarzy GitHub przez powtarzalną flagę --attach w GitHub CLI.
  • 100github
    Obsługuje GitHub przez gh CLI: tworzenie zgłoszeń, otwieranie pull requestów, sprawdzanie CI, przegląd PR-ów, zarządzanie wydaniami i złożone zapytania.
  • 100issue-burndown
    Przechodzi przez wiele otwartych zgłoszeń GitHub naraz: ustala, które są już naprawione lub objęte PR-ami, naprawia je seryjnie i doprowadza zbiór zgłoszeń do zmergowanych pull requestów.
  • 100github-backlog-triage
    Porządkuje backlog otwartych zgłoszeń i pull requestów repozytorium GitHub na wyraźne wywołanie użytkownika.
  • 90github
    Czyta i zarządza repozytoriami, issues, pull requestami i wyszukuje kod w GitHubie przez REST API.
  • 100github-ops
    Wykonuje szybkie operacje na GitHubie przez gh CLI: issues, pull requesty, repozytoria, Actions, wydania, gałęzie i sprawdzanie CI.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.