new-issue
/new-issue
Pisze w stałym formacie szkic zgłoszenia GitHub dla monorepo Leather z opisu lub rozmowy, gotowy do wysłania na GitHubie.
- Autor
- leather-io ↗
- Repozytorium
- mono ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 13.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 5
- Skrypty
- 1
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 4
Brak sygnałów. Repozytorium zmienione 13.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
- 1 skrypt w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.
Skrypty: scripts/package.sh
Co robi i kiedy
Pisze w stałym formacie szkic zgłoszenia GitHub dla monorepo Leather z opisu lub rozmowy, gotowy do wysłania na GitHubie.
Oryginalny opis (EN)
Draft a GitHub issue for the Leather monorepo (leather-io/mono) in a fixed, agent-ready shape, from a description or from the current conversation, and hand back a prefilled GitHub issue to submit. Use when asked to file an issue, write an issue, report a bug, open a ticket, create an issue for this, or turn a finding into an issue.
Jak działa
- 1. Detect the surface
- 2. Generate the feature map
- 3. Gather facts
- 4. Classify
- 5. Anchor (checkout or clone)
- 6. Decisions and Verify (checkout or clone)
- 7. Split
- 8. Dedup (checkout or clone)
- 9. Redact, draft, check
- 10. Create
Podgląd SKILL.md
--- name: new-issue description: Draft a GitHub issue for the Leather monorepo (leather-io/mono) in a fixed, agent-ready shape, from a description or from the current conversation, and hand back a prefilled GitHub issue to submit. Use when asked to file an issue, write an issue, report a bug, open a ticket, create an issue for this, or turn a finding into an issue. --- # New issue Draft one issue per unit of work for `leather-io/mono`, in the shape in `references/templates.md`, and hand the person a prefilled GitHub issue. They add screenshots and press Submit; you never do. Humans and agents read the same issue, so every draft carries precise anchors, the decisions a fixer must not guess, how to verify the fix, a checkable done condition and explicit scope. **Nothing is created without an explicit yes** after the person has seen every draft in full with its title and labels. A draft is not consent for the next one. ## 1. Detect the surface Two independent checks. Say once which source you have and whether `gh` works. **Source**: where the research runs. Take the first that works. | Source | When | Research and feature map | Permalink SHA | | ------------- | ----------------------------------------------------------------------- | ----------------------------- | ------------------------------------ | | **Checkout** | the working directory is a `leather-io/mono` checkout (`git remote -v`) | in place | `git rev-parse origin/dev`, no fetch | | **Clone** | no checkout, but you can run shell commands and reach github.com | a shallow clone of `dev` (§2) | the clone's `git rev-parse HEAD` | | **Text mode** | no shell, or the clone fails | none: no map, no anchors | none | **GitHub**: how dedup and creation run. | GitHub | When | Labels (§4) | Dedup (§8) | Create (§10) | | ----------- | ------------------------- | --------------------------- | ----------------- | ------------------------------------ | | **`gh`** | `gh auth status` succeeds | checked against the repo | `gh issue list` | `gh issue create --web` | | **No `gh`** | anything else | from `references/labels.md` | public search API | a prefilled link and a Markdown body | Text mode has no shell, so no `gh` and no dedup either; the report says the issue still needs anchors, Decisions and Verify from someone with a checkout or a clone. ## 2. Generate the feature map Before any research, with a checkout or a clone. `pnpm lt feature-map generate --help` lists the apps the generator supports (today `extension`); generate every one, whatever the report is about. - **Checkout**: in place, `pnpm lt feature-map generate --app extension`. If `pnpm lt` reports an unknown command, run `pnpm --filter @leather.io/tools build` first. The map reflects the working tree, which may be a branch ahead of `dev`; treat a route or spec it names as a lead and confirm it at the permalink SHA (§5). - **Clone**: a shallow clone and only the tools package's dependencies, a few seconds warm: ```bash dir="$(mktemp -d)" git clone --depth 1 --branch dev --single-branch https://github.com/leather-io/mono.git "$dir/mono" cd "$dir/mono" pnpm install --filter @leather.io/tools... --ignore-scripts pnpm --filter @leather.io/tools build pnpm lt feature-map generate --app extension ``` Node 22.15 or later is required. Without `pnpm` on the path, use `corepack pnpm`, or `npx pnpm@<version>` with the version from `packageManager` in the root `package.json`. The map lands in `.claude/skills/feature-map/extension.md`. If generation fails, say so, continue with the route search in §5 and name the failure in the report. ## 3. Gather facts - Invoked with no description after a working session: draft from the conversation. Use what was observed, run or read; do not invent steps that were not taken. - Otherwise take the description given. - Compare what you have with the **Version** and **Where** sections (screen or route · network · account type). Ask one round of questions, only for what you cannot derive: the platform when the symptom could live in more than one place, the app version, the account type (software, Ledger, policy). Never ask for what the code, the feature map or the conversation already answers. - For a bug, ask for the exact error text, as a free-text question and never a pick from options. If none comes back, put "error text not captured" in **Actual** and keep the cause suspect. ## 4. Classify From `references/labels.md`: the type (`bug`, `enhancement`, or none for an idea), exactly one `platform:*`, one to three `area:*`, and for bugs a proposed severity. With `gh`, cross-check with `gh label list --limit 100` and use only labels that exist. - **Severity is proposed in your report, never put in the labels.** - **Critical stops the draft.** Funds at risk or a wallet compromised goes to the private channel, not a public issue: the Leather bug bounty on Immunefi, or for maintainers the private `leather-io/leather-security` repo. Say why and draft nothing public. ## 5. Anchor (checkout or clone) Pin every permalink to one SHA: in a checkout the local `git rev-parse origin/dev`, in a clone the clone's `git rev-parse HEAD`. `https://github.com/leather-io/mono/blob/<sha>/<path>#L<n>`. In a checkout never fetch; a fetch can block on a hardware key. Confirm each cited line with `git show <sha>:<path>` before linking it, so the permalink shows what you read, not a working tree. - **Extension**: search `extension.md` for the route, a `RouteUrls` key, a selector or words from the screen, and follow the feature-map skill when it is available. Take the route, gate, flags, preconditions, page-object actions and covering spec from the entry. - **Packages**: find the function and its co-located `*.spec.ts`; the repro is the test command. - **Mobile and web**: search the routes (the `apps/mobile/src/app` file tree, `apps/web/app/routes.ts`) and the screen component for a UI string from the report. A cause is `### Cause (proven)` only when a reproduction ran in this session: a failing test, or a path you observed executing. Anything you only read is `### Cause (suspect)`. ## 6. Decisions and Verify (checkout or clone) Both sections come from the research in §5, before drafting. - **Verify**: fill it yourself from the anchors and the feature map: the unit command and the spec to extend or add, the covering E2E spec from the feature-map entry or "none covers this", an existing fixture or mock to reuse. Only the **Needs** line depends on the person. - **Decisions**: list every point where more than one fix is reasonable and neither the code, the repo conventions (`CLAUDE.md`) nor an earlier issue picks one: drop or throw, this issue or a follow-up, which layer owns the fix. Skip choices the code already settles. - **Ask once**: one round with `AskUserQuestion` when available, otherwise a numbered list. At most four questions: the decisions with the largest effect on the fix, each with two to four options and your recommendation first, plus the **Needs** line when the fix needs a device, Speculos, a funded account or a flag. Whatever is answered becomes `Settled: <choice> — <reason>`. Whatever is skipped or did not fit stays `Open:` with its options and your recommendation; never a second round. ## 7. Split - **One platform per issue**, and the title prefix matches its label. A fix that lives in a shared package is one `platform:packages` issue even when both apps show the symptom. - **A change each app implements separately** becomes one issue per app, each with a `### Sibling` section. - **One issue per unit someone can own and close.** Propose the split with a title per issue; the person decides. ## 8. Dedup (checkout or clone) - **With `gh`**: `gh issue list --repo leather-io/mono --search "<2-3 keywords>" --state all --limit 10`. - **Without `gh`**: `curl -s "https://api.github.com/search/issues?q=repo:leather-io/mono+is:issue+<keywords>&per_page=10"`; unauthenticated search allows 10 requests a minute. Show the closest matches with number, state and title as a hint. Do not decide for the person that it is a duplicate. ## 9. Redact, draft, check 1. **Redact before drafting**: runs of 12 or 24 lowercase words that look like a mnemonic, xpub, xprv, zpub and other extended keys, 64-hex private keys, WIFs, emails, account and wallet names, API keys and tokens. Replace with `<redacted>` and say what you removed. 2. **Draft** each issue from `references/templates.md`, verbatim headings, in the order given. Title: `<Extension|Mobile|Web|Packages>: <what breaks, in the user's words>`. Drop empty sections. UI strings and error text verbatim in code. `references/examples.md` shows the target. 3. **Check the budget**: the core stays under 250 words of prose, not counting code blocks, links, Decisions, Verify and the details block. Move overflow (logs, long pointers, rationale, history) into `<details><summary>Evidence and pointers</summary>`. Done when has one to three checkboxes, each checkable by someone else: a spec that passes, a visible string, a number. 4. **Show everything**: per issue, the title, labels, full body, proposed severity, duplicate hints, what stays suspect and which decisions stay open. Wait for yes. Apply edits and show again. ## 10. Create Only after yes, one issue at a time. - **Title and body go through files**: write each to a temporary file with the file-writing tool, never through `echo`, `printf` or a heredoc, so the shell never expands `$(...)`, backticks or `$VAR` in reporter text; without `gh`, URL-encode from those files the same way. - **With `gh`**: `gh issue create --repo leather-io/mono --web --title "$(cat <title-file>)" --body-file <body-file> --label "<type>,<platform>,<areas>"`. It opens the browser with a new issue prefilled; the person adds screenshots and submits. - **Without `gh`**, text mode included: give two things. A prefilled link, title and body URL-encoded: `https://github.com/leather-io/mono/issues/new?title=<title>&body=<body>&labels=<labels>`. Then the same Markdown body in one code block, ready to paste if the link fails. GitHub applies `labels` only for people with triage access; tell everyone else a maintainer labels it. - An over-long URL fails with 414: leave the details block out of the link and tell the person to paste it from the code block once the issue is open. - **Siblings**: open the first issue, ask for its number once submitted, then open the second with `### Sibling` set to `#<first>`, and offer the back-link line for the person to add to the first. ## 11. Report The source and whether `gh` worked, the issue URLs or the links you handed over, the labels per issue, the proposed severity, what stays suspect or unverified, which decisions stay open, what you redacted, which duplicates were close, and whether the feature map generated.
Pliki w paczce (5)
- SKILL.md 11 KB
- references/examples.md 8 KB
- references/labels.md 6 KB
- references/templates.md 6 KB
- scripts/package.sh 1 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · leather-io/mono | 100 | MIT |
| richkuo/rk-skills | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 914c30de71d0 (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
- 100gh-create-issue
Zakłada zgłoszenia na GitHubie dla błędów, funkcji oraz ustaleń z audytu lub przeglądu. - 100create-issue
Zgłasza issue na GitHubie dla błędu, funkcji, audytu lub wniosku z przeglądu. - 100create-github-issue
Tworzy zgłoszenia GitHub przez CLI gh: nowe issue, zgłoszenie błędu, prośba o funkcję lub zadanie. - 100monorepo-navigation
Pomaga poruszać się po strukturze monorepo Leather: wskazuje właściwy pakiet dla nowego kodu, istniejące implementacje i zależności między pakietami. - 100testing-patterns
Opisuje konwencje i wzorce testowania w monorepo Leather: konfigurację Vitest, nazewnictwo, fixtures i workflow TDD. - 100create-github-issue
Tworzy zgłoszenia GitHub przez GitHub CLI z szablonami, etykietami, osobami przypisanymi, kamieniami milowymi i wersjami roboczymi.