Przejdź do treści
Biblioteka skilli
Programowanie · Pisanie

create-mobile-pr

/create-mobile-pr

Tworzy pull request w repozytoriach mobilnych Dimagi i CommCare według szablonu: gałęzie z prefiksem JIRA, sekcje Release Notes i QA Notes w RELEASES.md, historia bezpieczeństwa i plan QA.

Licencja
MIT
Ostatnia zmiana repozytorium
06.10.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
3
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
1
Przestarzałość

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

Licencja

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

Co robi i kiedy

Tworzy pull request w repozytoriach mobilnych Dimagi i CommCare według szablonu: gałęzie z prefiksem JIRA, sekcje Release Notes i QA Notes w RELEASES.md, historia bezpieczeństwa i plan QA.

Wyzwalacze z opisu

ship this
Oryginalny opis (EN)

Use when creating, opening, or submitting a pull request in a Dimagi mobile/CommCare repo — identified by JIRA-prefixed branches (e.g. CCCT-1929-...), a `RELEASES.md` with `### Release Notes` and `### QA Notes` sections, and the dimagi PR template (Safety story / Product Description / Technical Summary / QA Plan). Also triggers on "ship this" or when implementation is complete and ready to push. For repos without these conventions, use the generic `create-pr` skill instead.

Jak działa

  1. Process
  2. Hard rules (mechanical, always)
Sekcje z nagłówków SKILL.md, w oryginale · 124 linii, 1 239 słów
Podgląd SKILL.md
---
name: create-mobile-pr
description: Use when creating, opening, or submitting a pull request in a Dimagi mobile/CommCare repo — identified by JIRA-prefixed branches (e.g. CCCT-1929-...), a `RELEASES.md` with `### Release Notes` and `### QA Notes` sections, and the dimagi PR template (Safety story / Product Description / Technical Summary / QA Plan). Also triggers on "ship this" or when implementation is complete and ready to push. For repos without these conventions, use the generic `create-pr` skill instead.
---

# Create GitHub Pull Request

Open a **draft** PR with a JIRA-prefixed title, a description built from the repo's PR template, and `--assignee "@me"`. The user reviews and marks it ready on GitHub. Release/QA notes go in `RELEASES.md`, not the PR body.

Every artifact below has a **recipe** (what it contains) and a **budget** (how long it may be). Fill the recipe with true statements up to the budget, then stop. Write to that shape — do not treat the budget as a target to reach. An artifact that would be empty is omitted entirely, heading and all. **The whole PR body is capped at 120 words** — section bodies, excluding headings and the ticket link. Every section under budget but the body over 120 still fails; drop the least load-bearing section.

**The diff test — apply to every sentence of the PR body.** Before writing a sentence, ask: *could the reviewer learn this by reading the diff?* If yes, delete it. Names of new helpers, params, or values; which file the code lives in; "follows the existing convention"; what a function does mechanically — all visible in the diff, all cut. The PR body exists only for what the code cannot tell the reviewer: why, and what to watch for. `example.md` in this directory is a full worked example of good, terse output.

## Process

### 1. Gather context (parallel)

```
git branch --show-current
git log master..HEAD --oneline
git log master..HEAD          # full messages, fallback for ticket
git diff master...HEAD --stat
git diff master...HEAD
cat .github/PULL_REQUEST_TEMPLATE.md
cat RELEASES.md
```

Fold any notes/context/verification steps the user already gave into the right sections.

### 2. Title

**Recipe:** `TICKET Short Description Of The Change`, derived from the commits and diff (not the branch slug).
**Budget:** ≤72 chars. Title Case every word including short ones (On, To, For, The). Preserve acronym/identifier casing (`SSO`, `URL`, `iOS`, `CCCT-1929`).

Extract `TICKET` (`[A-Z]+-[0-9]+`) from the branch prefix; fall back to commit messages; if still none, ask.
Example: `CCCT-1929 Re-Fetch SSO Token On Invalid Token Error`

### 3. Ask about the author's testing

The Safety story needs what the *author* actually did. If they haven't already said, ask:

> What did you personally do to test this? (ran it on a device, exercised a flow, ran a test suite, reviewed the diff only, etc.)

Wait for the answer. Record it honestly, including "did not test locally." Never invent testing.

### 4. Update RELEASES.md

Find the topmost `## CommCare X.YZ` section. Release Notes and QA Notes are **separate decisions, separate drafts-for-approval, separate commits**. **No JIRA ticket numbers anywhere in RELEASES.md.**

**Release Notes** — go under the `### Release Notes` subsection, in one of `#### What's New`, `#### Important Bug Fixes`, or `#### Internal Release Notes`. Include only if the change is observable by end users or a specific project.
**Recipe:** one bullet stating what changed *from the user's perspective*.
**Budget:** one line per change. No implementation detail.

**QA Notes** — go under the `### QA Notes` subsection. What a tester with only a phone build must manually verify (app UI, settings, forms, Connect, PersonalID, their own test accounts, HQ admin views). A tester has no Android Studio, Logcat, adb, or tests; if a regression is invisible without those, say so and rely on automated coverage instead of writing an unrunnable step.
**Recipe:** one bullet per distinct check, phrased "verify X still works" / "confirm Y behaves as expected." Only non-obvious risks and behavior changes — the tester already knows the happy path.
**Budget:** 1–3 bullets; hard cap 5.

For each: show the user the exact bullet text verbatim and the **release version heading it will go under** (e.g. `## CommCare 2.56`) so they can confirm it is landing in the right release — plus the subsection (`### QA Notes`, or `### Release Notes` → `#### Important Bug Fixes`). Wait for their approval, then commit alone (`Add release notes for TICKET` / `Add QA notes for TICKET`). Do not decide on the user's behalf to skip a note they might want — when in doubt whether a note is warranted, ask.

### 5. PR description

Build from `.github/PULL_REQUEST_TEMPLATE.md`, replacing every HTML comment with content. **Do not show the description for approval** — it's a draft the user edits on GitHub. Only RELEASES.md needed approval.

**Top of body:** `### [TICKET](https://dimagi.atlassian.net/browse/TICKET)` (display text is just the ticket).

Fill a section only when its recipe has something true to say; otherwise delete that heading and body. Always keep the ticket link and Safety story. **Omit the Labels and Review section.**

- **Safety story** — a neutral risk read in two lists, `**What gives confidence**` and `**Risks to review**`. Rank candidates by how much each one changes the reviewer's read and keep only the top ones, most important first — true is the floor, not the bar. Author actions in **first person** ("I exercised the happy path"); statements about the change in third person. Note a mitigation if there is one; otherwise leave it for the reviewer. `risk-categories.md` lists what to weigh.
  **Budget:** ≤2 items per list, ≤15 words each; ≤55 words total.
- **Technical Summary** — *only* what survives the diff test: why this approach over the obvious alternative, and any non-obvious decision, exclusion, or ordering dependency a reviewer should know before reading. If the diff already speaks for itself, omit the whole section.
  **Budget:** ≤40 words.
- **Product Description** — the user-facing behavior change.
  **Budget:** ≤25 words.
- **Automated test coverage** — what tests were added or changed and what they lock down.
  **Budget:** ≤25 words.

**Verify before building the body:** count the words in each drafted section and recut any that exceeds its budget — drop the lowest-ranked item, or tighten. Then sum them; if the total exceeds 120, cut the least load-bearing section whole.

### 6. Push

```bash
git rev-parse --abbrev-ref --symbolic-full-name @{u}   # upstream?
git push -u origin HEAD    # if none
git push                   # if behind (carries the RELEASES.md commits)
```

### 7. Create the draft PR

```bash
gh pr create --draft \
  --title "TICKET Short Description" \
  --body "$(cat <<'EOF'
<generated description>
EOF
)" \
  --assignee "@me"
```

No `--reviewer` — the user requests reviewers after leaving draft. Capture the printed PR URL for step 8.

### 8. Suggested Review Order comment

Skip if fewer than 2 non-generated files changed.

**Recipe:** the changed files in reading order, each with a short clause of rationale (≤15 words). Order: deleted/replaced code → schema/model/migration → new types/constants → core logic → integration/API → UI → tests (near their code, or first if they document intent) → config/build/cosmetic last. Skip generated files (lock files, compiled output, vendored deps). If the commits already tell a clean story, recommend reading commit-by-commit instead.

```bash
gh pr comment <PR-URL> --body "$(cat <<'EOF'
## Suggested Review Order

- `path/to/file-1.kt` — reason it comes first
- `path/to/file-2.kt` — reason it comes next
EOF
)"
```

Then output the PR URL.

## Hard rules (mechanical, always)

- Draft PR: `--draft`, `--assignee "@me"`, never `--reviewer`.
- No JIRA ticket numbers in RELEASES.md (release notes or QA notes).
- Each RELEASES.md update is its own commit, and only after the user approves the drafted bullets.
- Omit the template's Labels and Review section.
- Never leave the template's HTML-comment placeholders in the body.
- Every PR body section is at or under its word budget, and the body is ≤120 words.
- Push the branch before `gh pr create`.
Pliki w paczce (3)
  • SKILL.md 8 KB
  • example.md 4 KB
  • risk-categories.md 1 KB

Wersje

W bazie nie ma innych skilli o nazwie create-mobile-pr.

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

  • 100create-pr
    Tworzy i zgłasza pull request na GitHubie: commituje, wypycha bieżącą gałąź i zamienia ją w PR; dla repozytoriów mobilnych CommCare lepszy jest create-mobile-pr.
  • 100pr-risk
    Ocenia ryzyko pull requestu mobilnego CommCare i ustawia etykietę Low, Medium lub High Risk.
  • 100pr-description
    Pisze opisy PR i notatki wydania dla monorepo Sanity według szablonu repozytorium: Description, What to review, Testing i Notes for release.
  • 100pull-request-description
    Pisze tytuł i opis pull requesta w repozytoriach Sage Bionetworks na podstawie szablonu repozytorium i zgłoszenia Jira z nazwy gałęzi, skalując długość do złożoności zmiany.
  • 100create-pr
    Tworzy pull request według szablonu repozytorium, bez natychmiastowego scalania.
  • 90create-pull-request
    Tworzy lub odświeża pull request dla bieżącej gałęzi, z opisem z szablonu repozytorium, diffem i wynikami 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.