New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Concise PR And Issue Descriptions

by 0xMiden in 0xMiden/protocol

Keep PR and issue descriptions short and decision-focused. An agent skill from 0xMiden/protocol.

MITAuto-check passedDevelopment

Install Concise PR And Issue Descriptions

skills CLI
$ npx skills add 0xMiden/protocol --skill concise-pr-and-issue-descriptions -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install 0xMiden/protocol concise-pr-and-issue-descriptions --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/0xMiden/protocol.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/concise-pr-and-issue-descriptions .claude/skills/concise-pr-and-issue-descriptions && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
concise-pr-and-issue-descriptions
GitHub stars
133
Token cost
~1.8k tokens
SKILL.md length
557 words
Files
1
Skills in repo
35
Repo updated
First seen
Licence
MIT

At a glance

Keep PR and issue descriptions short and decision-focused. An agent skill from 0xMiden/protocol.

  • Works in 3 steps: ## Summary - Closes #N, then one or two… → ## Changes - three to five bullets. Each… → ## Open questions - numbered, only for…
  • Editing a pull request body
  • SKILL.md covers The shared rule, Pull requests, Issues and What earns extra length
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Concise PR And Issue Descriptions is an agent skill from 0xMiden/protocol. Keep PR and issue descriptions short and decision-focused. Use when writing or editing a pull request body or a GitHub issue.

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Pull requests. It works with GitHub. The repository describes itself as: Core components of the Miden protocol. The licence is MIT.

When your agent uses it

  • Editing a pull request body
  • Tasks that involve Pull requests

Example prompts

  • “/concise-pr-and-issue-descriptions”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. ## Summary - Closes #N, then one or two short paragraphs: the problem, and why
  2. ## Changes - three to five bullets. Each says what changed and folds the reason into
  3. ## Open questions - numbered, only for decisions the reviewer must actually make.

What it can do on your machine

Read from SKILL.md and the folder at commit 62b59ec. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Concise PR And Issue Descriptions loads about 1.8k tokens when it runs. Until then it costs about 40 tokens; SKILL.md has 557 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~40
When it runs · the whole SKILL.md, loaded when a task matches
~1.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from 0xMiden/protocol at commit 62b59ec, republished under its MIT licence (© 0xMiden). 557 words, ~1,777 tokens.

Download SKILL.mdSave it as .claude/skills/concise-pr-and-issue-descriptions/SKILL.md (or your agent's skills folder).
name
concise-pr-and-issue-descriptions
description
Keep PR and issue descriptions short and decision-focused. Use when writing or editing a pull request body or a GitHub issue.

Concise PR and Issue Descriptions

The shared rule

A PR or issue body answers why it exists, what it covers, and what the reader has to decide. Then it stops. Aim for under ~400 words.

Cut anything the reader can already get from the diff, from CI, or from a link:

  • Test plans and verification checklists. CI reports what passed; a green checklist pasted by the author proves nothing a reviewer can act on.
  • Command transcripts, test counts, timing.
  • Process narration: approaches tried and abandoned, how the rebase went, which review round changed what.
  • File-by-file enumeration, and long code blocks a permalink would cover.
  • Mechanism the linked code already shows.
  • The same link repeated. Link an issue or a file once.

Use commit-pinned permalinks (/blob/<full-sha>/path#L123), never branch refs - branch line numbers rot, and a stale link costs the reader more than the paragraph saved.

Pull requests

Sections, in this order. Drop any that would be empty.

  1. ## Summary - Closes #N, then one or two short paragraphs: the problem, and why this change is the answer. State the motivation, do not restate the diff.
  2. ## Changes - three to five bullets. Each says what changed and folds the reason into the same sentence. Close with a one-line sweep of cross-cutting facts (what stayed the same, which commitments or IDs change, which crates are untouched).
  3. ## Open questions - numbered, only for decisions the reviewer must actually make. Two sentences each.

The one exception to "no process narration": a force-push that replaced a materially different approach earns a single sentence, so a reviewer comparing revisions is not left guessing.

Example

Avoid (verification noise, process narration, per-file detail):

markdown
## Summary
This PR removes the AggLayer faucet component. See below for details.

## Changes
- Deleted `crates/miden-agglayer/asm/components/faucet/faucet.masm`
- Deleted `crates/miden-agglayer/asm/agglayer/faucet/mod.masm`
- Deleted `crates/miden-agglayer/src/faucet.rs` (318 lines)
- Updated `crates/miden-agglayer/build.rs` lines 235-255 to drop the faucet branch
- Updated 24 call sites across bridge_in.rs, bridge_out.rs, ...

## Note on the approach
An earlier revision added a builder-returning variant to miden-standards, but after
rebasing onto #3486 that no longer worked, so I reverted it and started over.

## Test plan
- [x] Full suite: 1841 passed, 0 failed
- [x] `cargo test -p bench-transaction --release`: 28 passed
- [x] `make clippy`, `make check-no-std`, `make build-no-std`, `make doc`

Good (motivation, effect, open decisions):

markdown
## Summary

Closes [#2585](https://github.com/0xMiden/protocol/issues/2585).

The `agglayer::faucet` component was vestigial: it re-exported three procedures from the
standards library, a strict subset of what the standard `FungibleFaucet` component exports.
The re-exports resolve to the same standards procedures, so the mint/burn MAST roots are
unchanged by the swap.

The functional gap was the token name: `AggLayerFaucet::new` fabricated it from the symbol,
leaving the metadata hash preimage `abi.encode(name, symbol, decimals)` unrecoverable from
faucet storage. #2586 needs it to verify the registered hash on-chain.

## Changes

- Removed the `miden-agglayer-faucet` MASM package, `src/faucet.rs` and the generated
  `FAUCET_CODE_COMMITMENT`. Faucet identity now comes from `FungibleFaucet::try_from(&Account)`,
  which checks the interface instead of a commitment that had to hand-mirror the component stack.
- The builders take a token name, and `MetadataHash::from_fungible_faucet` derives the
  registered hash from faucet storage so the two cannot drift.

The component stack is otherwise unchanged. The faucet code commitment changes, as do faucet
account IDs. `miden-standards` is untouched.

## Open questions

1. `TokenName::MAX_BYTES` is 32, a policy cap below the 55-byte encoding capacity. #2586 turns
   the current workaround into a hard ceiling on foreign token names, so it is worth settling
   before that work starts.
Show full SKILL.md (279 more words)Show less

Issues

Same discipline, different shape. An issue makes the case that something should change and gives whoever picks it up enough to start.

  1. Title - the problem or the wanted outcome, not a summary of the fix.
  2. Opening paragraph - what is wrong or missing, stated as fact, with a permalink to the code. No preamble.
  3. Impact - what breaks, who is affected, or what it blocks. This is what earns the issue its priority, so do not leave it implicit.
  4. Proposed direction (optional) - a few bullets naming the approach. Not a design doc and not an implementation plan; the PR does that.
  5. Prerequisites and related issues, as a short trailing list.

Additionally leave out of issues:

  • Step-by-step implementation plans and per-file edit lists.
  • Exploration narrative ("I first tried X, then Y").
  • Speculation about causes you have not checked. Say what you observed and mark what is unverified.

Quote code only when the excerpt is the point (a wrong line, a confusing signature), and keep it to a few lines. Otherwise link it.

Example

Avoid (fix plan in place of a problem statement):

markdown
### Proposed Solution

We should refactor `get_size_hint` to avoid the temporary allocation. Steps:
1. Add a `serialized_size()` method to `MastForest` in `miden-core`
2. Change `AccountCode::get_size_hint` at line 301 to call it
3. Update the tests in `mod.rs` lines 890-940
4. Run `cargo test -p miden-protocol`
...followed by the full diff, inline.

Good (problem, evidence, impact, direction):

markdown
`AccountCode::get_size_hint` measures the encoded size by serializing the whole `MastForest`
into a throwaway `Vec<u8>` and reading its length
([code](https://github.com/0xMiden/protocol/blob/a95dc00a/crates/miden-protocol/src/account/code/mod.rs#L301-L315)).

Every `AccountCode::to_bytes()` therefore serializes the forest twice: once to size the
buffer, once to fill it, with a heap allocation in between that is immediately dropped.
Account code is serialized on every account update, so this is on a hot path.

Fix direction: give `MastForest` a size calculation that does not build the buffer, and have
`get_size_hint` call it. The existing `TODO` at that line anticipates this.

What earns extra length

Only what the reader needs and cannot get elsewhere:

  • A security or correctness argument for why a change is safe.
  • A protocol-level consequence: a commitment that changes, an account ID that moves, a storage layout that shifts.
  • A deliberate deviation from a convention, with its reason.
  • For issues, a genuine design question put to the team - the trade-offs, the options, and what you need decided. These are discussions, and being terse costs more than it saves.

Depth in these is fine. Everything else gets cut.

© 0xMiden, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/concise-pr-and-issue-descriptions of 0xMiden/protocol.

Open the folder on GitHubat commit 62b59ec

Compare with similar skills

Concise PR And Issue Descriptions next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Concise PR And Issue Descriptions compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Concise PR And Issue Descriptions this skill0xMiden/protocol133—~1.8kAutomated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
Create Pull Requestcline/cline70k1 repos~1.6kAutomated safety check: PassApache-2.0
Pull Request Title and Body Writeropeninterpreter/openinterpreter69k2 repos~1.1kAutomated safety check: PassApache-2.0

Similar skills

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Check PR

    onyx-dot-app/onyx

    Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed

  • Contributor-First PR Merge

    HKUDS/OpenHarness

    Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed

  • Create Pull Request

    cline/cline

    Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.

    70k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed

  • Pull Request Title and Body Writer

    openinterpreter/openinterpreter

    Rewrites the title and body of one or more pull requests with gh, leading with why the change was made, then what changed, and describing only the net result.

    69k GitHub starsUsed in 2 repos~1.1k tokens
    DevelopmentAuto-check passed

  • GitHub Review Iteration

    prisma/orm

    Official

    Runs a loop on a GitHub pull request: fetch review state, triage comments into actions, implement them and resolve threads, repeating until nothing actionable is left.

    48k GitHub stars~2.2k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from 0xMiden/protocol

All 35 skills in this repo

  • Advice Provider Hygiene

    0xMiden/protocol

    A skill your agent uses when writing kernel, account, or note MASM code that reads from or writes to the advice provider (advice stack / advice map) — validate advice data.

    133 GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • Cheap Masm Equivalents

    0xMiden/protocol

    A skill your agent uses when writing or reviewing MASM hot paths or loops — prefer the cheaper equivalent: loop counters and pointers on the operand stack instead of procedure locals, neq.0 over…

    133 GitHub stars~804 tokensUpdated yesterday
    Auto-check passed

  • Concise Changelog Entries

    0xMiden/protocol

    Keep CHANGELOG.md entries to a single concise sentence. An agent skill from 0xMiden/protocol.

    133 GitHub stars~805 tokensUpdated yesterday
    Auto-check passed

  • Conversion Method Naming

    0xMiden/protocol

    A skill your agent uses when naming a conversion or accessor method in Rust — follow the Rust API naming conventions for the method's cost and ownership.

    133 GitHub stars~450 tokensUpdated yesterday
    Auto-check passed

  • Decouple Component From Storage

    0xMiden/protocol

    A skill your agent uses when writing a generic MASM utility that accesses a caller-selected account storage slot — receive the slot as a parameter so the utility is portable across storage layouts.

    133 GitHub stars~529 tokensUpdated yesterday
    Auto-check passed

  • Felt Construction

    0xMiden/protocol

    A skill your agent uses when constructing a Felt from a numeric value in Rust — use checked construction unless the canonical bound is already proved.

    133 GitHub stars~439 tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Concise PR And Issue Descriptions

What does Concise PR And Issue Descriptions do?

Keep PR and issue descriptions short and decision-focused. An agent skill from 0xMiden/protocol. Concise PR And Issue Descriptions is an agent skill from 0xMiden/protocol. Keep PR and issue descriptions short and decision-focused.

When should I use Concise PR And Issue Descriptions?

Concise PR And Issue Descriptions fits situations like: editing a pull request body; tasks that involve Pull requests.

How do I install Concise PR And Issue Descriptions in Claude Code?

Run `npx skills add 0xMiden/protocol --skill concise-pr-and-issue-descriptions -a claude-code`. Or copy the skill folder (.claude/skills/concise-pr-and-issue-descriptions in 0xMiden/protocol) into .claude/skills/concise-pr-and-issue-descriptions in your project. Claude Code loads it when a task matches its description.

How do I install Concise PR And Issue Descriptions in Codex?

Run `npx skills add 0xMiden/protocol --skill concise-pr-and-issue-descriptions -a codex`. Or copy the skill folder (.claude/skills/concise-pr-and-issue-descriptions in 0xMiden/protocol) into .agents/skills/concise-pr-and-issue-descriptions in your project. Codex loads it when a task matches its description.

Can I use Concise PR And Issue Descriptions in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add 0xMiden/protocol --skill concise-pr-and-issue-descriptions -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/concise-pr-and-issue-descriptions, .gemini/skills/concise-pr-and-issue-descriptions, .github/skills/concise-pr-and-issue-descriptions and .opencode/skills/concise-pr-and-issue-descriptions in your project.

What does Concise PR And Issue Descriptions need to run?

SKILL.md names no scripts, command-line tools or credentials: Concise PR And Issue Descriptions is instructions for the agent only.

Does Concise PR And Issue Descriptions access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Concise PR And Issue Descriptions safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Concise PR And Issue Descriptions use?

Concise PR And Issue Descriptions is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Concise PR And Issue Descriptions use?

About 1.8k tokens (SKILL.md is roughly 7.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Concise PR And Issue Descriptions?

Skills that share tags, products or a category with Concise PR And Issue Descriptions: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars) and Create Pull Request (cline/cline, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Concise PR And Issue Descriptions?

0xMiden (a GitHub organization) maintains it in 0xMiden/protocol, which has 133 GitHub stars. The repository holds 35 skills in this directory. The repository was last updated on October 9, 2026.

Source: 0xMiden/protocol on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.