Przejdź do treści
Biblioteka skilli
Programowanie · Pisanie

pr-description

/pr-description

Pisze treść pull requesta, gdy trzeba opisać zmiany w kodzie.

Repozytorium
agent-team ↗
Licencja
MIT
Ostatnia zmiana repozytorium
06.11.2026

Ocena i bezpieczeństwo

92/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność17 / 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
2
Skrypty
0
Komentarze HTML
1
Adresy URL w SKILL.md
1
Przestarzałość

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

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co sprawdzić przed instalacją
  • SKILL.md zawiera komentarze HTML (1). Nie widać ich w podglądzie Markdown, a model je czyta.

Co robi i kiedy

Pisze treść pull requesta, gdy trzeba opisać zmiany w kodzie.

Oryginalny opis (EN)

Use when writing a PR body.

Jak działa

  1. Sections
Sekcje z nagłówków SKILL.md, w oryginale · 163 linii, 657 słów
Podgląd SKILL.md
---
name: pr-description
description: "Use when writing a PR body."
metadata:
  credits:
    skill: show-me
    author: Dex Horthy
    organisation: Humanlayer
    url: "https://github.com/humanlayer/skills/blob/main/plugins/show-me/skills/show-me/SKILL.md"
---
<!-- Vendored from mattpocock/skills@a496f55 (skills/engineering/pr), MIT, see THIRD_PARTY.md. Adapted for agent-team: see THIRD_PARTY.md. -->


Use this template for the PR body, in the project's language (French in the user's projects). It maps the upstream "Summary / Evidence / Merge Danger" onto the team's four sections; keep each bullet to one line. Never add an attribution footer to the body.

```markdown
## Contexte

- The ticket (id in the PR title, not here only) and why, in one or two bullets.

## Changements

- One line per change. Optional: <diagram, diff-sketch, or tree> when it makes the point faster than prose.

## Vérification

- **Avant :** <screenshot/output/failing test run>
  **Après :** <screenshot/output/passing test run>
- The commands run and the CI status.

## Limites

- Known gaps, follow-up tickets, visible deviations.
- **Réversibilité :** <facile à annuler ou à sens unique>. **Portée :** <un mot>.
```

## Sections

Skip all preambles and keep prose brief. Use the user's domain language (the project's glossary, if there is one).

### Changements (upstream: Summary)

Pick the smallest view that makes the key point clear.

- Show logic or an algorithm as pseudocode:

```text
on(save)
  if content is unchanged
    return cached result
  write new content
  return fresh result
```

- Show runtime control flow as a call tree:

```text
submitForm
  createSession
    persistPrompt
    launchAgent
  navigateToSession
```

- Show UI structure as a component tree, including state and module boundaries that matter:

```text
<SessionPage> (apps/example/src/routes/session.tsx)
  useSessionEvents()
  <SessionToolbar>
    <RunSkillButton> (packages/ui)
```

- Show file responsibility or a broad refactor as a shallow file tree:

```text
src/
├── commands/       # parses user actions
├── sessions/       # owns session state
└── transport/      # sends API requests
```

- Show component interaction, control flow, or data flow with Mermaid:

```mermaid
sequenceDiagram
    participant User
    participant UI
    participant Daemon
    User->>UI: choose command
    UI->>Daemon: send expanded prompt
    Daemon-->>UI: stream result
```

- Use `diff` when the point is what changes and the surrounding shape already exists. Match the diff shape to the topic.

For a component change:

```diff
 <SessionPage>
   useSessionEvents()
   <SessionToolbar>
+    <RunSkillButton />
   <SessionTimeline>
+    <SkillResultCard />
```

For a file-layout change:

```diff
 src/
 ├── commands/
+│   └── show-me.ts       # expands the slash command
 ├── sessions/
-└── transport.ts
+└── transport/
+    ├── client.ts
+    └── stream.ts
```

For a call-tree or call-stack change:

```diff
 submitForm
   createSession
     persistPrompt
+    expandSkillMention
     launchAgent
-  navigateToSession
+  navigateToSession
+    subscribeToEvents
```

For a state or control-flow change:

```diff
 on(save)
-  write content
+  if content is unchanged
+    return cached result
+  write new content
+  invalidate cache
```

- Show the whole block when most of it is new, when omitted context would hide ownership or order, or when the user needs a copyable target shape:

```ts
function expandSkill(command: string): string {
  const skillName = command.slice(1);
  return `use the ${skillName} skill`;
}
```

#### Guidance

Place each visual next to the short text it supports. Keep only the calls, files, props, states, and boundaries needed to answer the user's current question or the options to resolve the current discussion point.

You may use one of these, you may use several, it is unlikely you will use all of them. Use your judgement and don't overwhelm the user.

### Vérification (upstream: Evidence)

Concrete evidence that the change works. Show a before and after.

Screenshots are S-tier - when the environment is set up for it and the change is visual.

Execution-based evidence is A-tier. Test results, console output. Show the exact test that now fails and passes, using pseudocode.

### Limites (upstream: Merge Danger)

Describe whether it's a one-way or two-way door. You can walk back through two-way doors, but not one-way doors. A PR that is cheap to roll back is lower risk. Changes that involve destructive actions or hard-to-reverse decisions are one-way doors.

The blast radius is the potential impact or scope of the changes introduced by this PR. Consider all possibilities. Examples are layout shift, breakages for consumers, mobile responsiveness, etc.
Pliki w paczce (2)
  • CREDITS.md 1 KB
  • SKILL.md 5 KB

Wersje

RepozytoriumWynikLicencja
Ta strona · lemramimel/agent-team92MIT
tanstack/ai100MIT
dxos/dxos100Apache-2.0
sanity-io/sanity100MIT
gosodax/sodax-sdks100MIT
Epsilon0xCell/pr-shepherd-skills100MIT
jdx/mise100MIT
Kuan-AI-com/agent-skills100MIT
basicmachines-co/basic-memory100AGPL-3.0

Migawka bazy z 13.11.2026 · wersja paczki 7b4a4c79acd4 (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

  • 92pr
    Pisze treść pull requesta, gdy trzeba opisać zmiany w kodzie.
  • 92pr
    Pisze treść pull requesta, gdy trzeba opisać zmiany w kodzie.
  • 92pr
    Pisze treść pull requesta, gdy trzeba opisać zmiany w kodzie.
  • 92pr
    Pisze treść pull requesta, gdy trzeba opisać zmiany w kodzie.
  • 92pr
    Pisze treść pull requesta, gdy trzeba opisać zmiany w kodzie.
  • 92pr
    Pisze tytuł i treść pull requesta, gdy trzeba opisać zmiany w kodzie.

Uwagi i zgłoszenia

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