Agent skill

Dynamo PR Description

by DynamoDS in DynamoDS/Dynamo

Generate PR descriptions for Dynamo that align with the team template section names and order.

Apache-2.0Auto-check passedDevelopment

Install Dynamo PR Description

skills CLI
$ npx skills add DynamoDS/Dynamo --skill dynamo-pr-description -a claude-code

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

GitHub CLI
$ gh skill install DynamoDS/Dynamo dynamo-pr-description --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/DynamoDS/Dynamo.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/dynamo-pr-description .claude/skills/dynamo-pr-description && 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
dynamo-pr-description
GitHub stars
2k
Token cost
~880 tokens
SKILL.md length
337 words
Files
1
Skills in repo
13
Repo updated
First seen
Licence
Apache-2.0

At a glance

Generate PR descriptions for Dynamo that align with the team template section names and order.

  • Works in 6 steps: Read the diff (staged changes, commit… → Identify the why -- what problem does… → Fill .github/PULL_REQUEST_TEMPLATE.md… → …
  • Writing a pull request description
  • SKILL.md covers When to use, When not to use, Inputs expected and Output format, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Dynamo PR Description is an agent skill from DynamoDS/Dynamo. Generate PR descriptions for Dynamo that align with the team template section names and order. Use this skill whenever writing a pull request description, cleaning up a PR body, or generating a review-ready summary from a diff in the Dynamo repo. Also use when the user says "write a PR", "PR description", or "prep this for review."

Its SKILL.md is about 880 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 Jira and GitHub. The repository describes itself as: Open Source Graphical Programming for Computational Design and Automation. The licence is Apache-2.0.

When your agent uses it

  • Writing a pull request description
  • Cleaning up a PR body
  • Generating a review-ready summary from a diff in the Dynamo repo
  • The user says write a PR

Example prompts

  • “write a PR”
  • “PR description”
  • “prep this for review.”
  • “/dynamo-pr-description”

Workflow steps

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

  1. Read the diff (staged changes, commit history, or user-provided summary).
  2. Identify the why -- what problem does this solve?
  3. Fill .github/PULL_REQUEST_TEMPLATE.md from the diff and context.
  4. For each declaration checkbox, only check it if you've verified it's true.
  5. Write the release note from the user's perspective (one sentence, or N/A).
  6. Leave (FILL ME IN) placeholders for anything you can't determine from the diff.

What it can do on your machine

Read from SKILL.md and the folder at commit 8cadc02. 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

Dynamo PR Description loads about 880 tokens when it runs. Until then it costs about 89 tokens; SKILL.md has 337 words of instructions outside code blocks.

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

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 DynamoDS/Dynamo at commit 8cadc02, republished under its Apache-2.0 licence (© DynamoDS). 337 words, ~880 tokens.

Download SKILL.mdSave it as .claude/skills/dynamo-pr-description/SKILL.md (or your agent's skills folder).
name
dynamo-pr-description
description
Generate PR descriptions for Dynamo that align with the team template section names and order. Use this skill whenever writing a pull request description, cleaning up a PR body, or generating a review-ready summary from a diff in the Dynamo repo. Also use when the user says "write a PR", "PR description", or "prep this for review."

Dynamo PR Description

When to use

  • Writing a PR description from a diff in the Dynamo repo.
  • Cleaning up or reformatting an existing PR body to match the team template.
  • Producing review-ready summaries quickly.

When not to use

  • PRs targeting the DynamoMCP repo -- that repo has its own PR description skill.
  • Jira ticket triage -- use dynamo-jira-ticket instead.

Inputs expected

A git diff, commit log, or description of the changes. Optionally a Jira key.

Output format

A complete PR body matching the Dynamo template in .github/PULL_REQUEST_TEMPLATE.md, ready to paste.


Workflow

  1. Read the diff (staged changes, commit history, or user-provided summary).
  2. Identify the why -- what problem does this solve?
  3. Fill .github/PULL_REQUEST_TEMPLATE.md from the diff and context.
  4. For each declaration checkbox, only check it if you've verified it's true.
  5. Write the release note from the user's perspective (one sentence, or N/A).
  6. Leave (FILL ME IN) placeholders for anything you can't determine from the diff.

Rules

  • Mirror section names and heading order from the template exactly.
  • Keep facts verifiable from the diff. Do not invent Jira keys, reviewers, or test results.
  • Call out breaking changes or migration steps explicitly in Purpose.
  • If the PR changes public API, mention the affected types and whether PublicAPI.Unshipped.txt was updated.
  • If the PR adds new nodes, mention the node names and whether help files were included.
  • The API versioning declaration is important -- check it only if changes follow Semantic Versioning.
  • Release Notes is a mandatory section -- always include it, even if just N/A.
  • If the user provides explicit checklist bullets or section content, treat those as source of truth and override the defaults below.

PR Title

Format: DYN-1234: concise change summary (include Jira key when known).

Template

Read .github/PULL_REQUEST_TEMPLATE.md for the exact template structure. Follow its sections in order.

Content guidance within those sections:

  • In Purpose, include a concise "Key changes:" bullet list when it helps readability.
  • For Release Notes, write one concise sentence from the user's perspective, or N/A when not user-facing.

Example: PR adding a new node

markdown
### Purpose

DYN-5678: Add `String.Interpolate` node for string formatting with placeholders.

Key changes:
- New `StringInterpolate` method in `src/Libraries/CoreNodes/String.cs`
- Added to `PublicAPI.Unshipped.txt`
- NUnit tests in `test/Libraries/CoreNodesTests/StringTests.cs`
- Help files: `.dyn`, `.md`, `.jpg` in `doc/distrib/NodeHelpFiles/`

### Declarations

- [x] Is documented according to the standards
- [x] The level of testing this PR includes is appropriate
- [x] Changes to the API follow Semantic Versioning and are documented in the API Changes document.

### Release Notes

Added String.Interpolate node for formatting strings with named placeholders.

### Reviewers

(FILL ME IN) Reviewer 1

### FYIs

(FILL ME IN, Optional)

© DynamoDS, Apache-2.0. 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/dynamo-pr-description of DynamoDS/Dynamo.

Open the folder on GitHubat commit 8cadc02

Compare with similar skills

Dynamo PR Description 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.

Dynamo PR Description compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Dynamo PR Description this skillDynamoDS/Dynamo2k—~880Automated safety check: PassApache-2.0
Link Ticket To SessionJayantDevkar/claude-code-karma329—~1.8kAutomated safety check: NotesApache-2.0
Adhoc PRshopsys/shopsys350—~2.3kAutomated safety check: PassCustom licence
Code Reviewsortie-ai/sortie196—~2.9kAutomated safety check: PassMIT
Review Release Noteschef/chef-web-docs143—~5.2kAutomated safety check: PassCustom licence
Create PRwanteddev/montage-web117—~6.3kAutomated safety check: NotesMIT

Similar skills

  • Link Ticket To Session

    JayantDevkar/claude-code-karma

    Link the current Claude Code session to a ticket (Linear, Jira, GitHub Issues, or GitHub Pull Requests) and cache its title/status in karma.

    329 GitHub stars~1.8k tokensUpdated 8 days ago
    DevelopmentAuto-check: notes
  • Adhoc PR

    shopsys/shopsys

    Ad-hoc Pull Request Publisher — commits the current changes, pushes the branch, opens a GitHub pull request against the repository's default branch, and creates a matching SSP Jira issue in the…

    350 GitHub stars~2.3k tokensUpdated today
    DevelopmentAuto-check passed
  • Code Review

    sortie-ai/sortie

    Reviews pull requests in this repository for the defect classes a mechanical checklist misses: documentation that outlived the code it describes, reaction and retry state that leaks or clobbers a…

    196 GitHub stars~2.9k tokensUpdated today
    DevelopmentAuto-check passed
  • Review Release Notes

    chef/chef-web-docs

    Read a release notes file and edit it using Jira release data and GitHub pull requests as co-equal, optional sources.

    143 GitHub stars~5.2k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Create PR

    wanteddev/montage-web

    Create a GitHub pull request from the current branch. An agent skill from wanteddev/montage-web.

    117 GitHub stars~6.3k tokensUpdated today
    DevelopmentAuto-check: notes
  • Spec

    warpdotdev-demos/cloud-factory-demo

    Coordinate spec-driven development for a GitHub, Jira, Linear, or other issue-tracker issue marked ready-to-spec by using write-product-spec and write-tech-spec, creating PRODUCT.md and TECH.md…

    320 GitHub stars~2.1k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

More from DynamoDS/Dynamo

All 13 skills in this repo
  • Dynamo Jira Ticket

    DynamoDS/Dynamo

    Create structured Jira tickets for Dynamo from bug reports, failing tests, or feature requests.

    2k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Dynamo Dotnet Expert

    DynamoDS/Dynamo

    Write and review C/.NET code in Dynamo following Dynamo coding standards, modern C patterns, and repo conventions.

    2k GitHub stars~909 tokensUpdated today
    Auto-check passed
  • Dynamo Onboarding

    DynamoDS/Dynamo

    Navigate the Dynamo codebase and produce architecture briefings.

    2k GitHub stars~1.9k tokensUpdated today
    Auto-check passed
  • Dynamo Skill Writer

    DynamoDS/Dynamo

    Author and maintain Dynamo agent skills. An agent skill from DynamoDS/Dynamo.

    2k GitHub stars~2.2k tokensUpdated today
    Auto-check passed
  • Dynamo Unit Testing

    DynamoDS/Dynamo

    Write comprehensive NUnit tests for the Dynamo codebase following Dynamo testing patterns, conventions, and architectural constraints.

    2k GitHub stars~622 tokensUpdated today
    Auto-check passed
  • Dynamo UX Designer

    DynamoDS/Dynamo

    Plans UX flows, maps product needs to Weave Design System components, and generates structured Figma mockups using Autodesk Weave libraries.

    2k GitHub stars~3.1k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Dynamo PR Description

What does Dynamo PR Description do?

Generate PR descriptions for Dynamo that align with the team template section names and order. Dynamo PR Description is an agent skill from DynamoDS/Dynamo. Generate PR descriptions for Dynamo that align with the team template section names and order.

When should I use Dynamo PR Description?

Dynamo PR Description fits situations like: writing a pull request description; cleaning up a PR body; generating a review-ready summary from a diff in the Dynamo repo; the user says write a PR.

How do I install Dynamo PR Description in Claude Code?

Run `npx skills add DynamoDS/Dynamo --skill dynamo-pr-description -a claude-code`. Or copy the skill folder (.claude/skills/dynamo-pr-description in DynamoDS/Dynamo) into .claude/skills/dynamo-pr-description in your project. Claude Code loads it when a task matches its description.

How do I install Dynamo PR Description in Codex?

Run `npx skills add DynamoDS/Dynamo --skill dynamo-pr-description -a codex`. Or copy the skill folder (.claude/skills/dynamo-pr-description in DynamoDS/Dynamo) into .agents/skills/dynamo-pr-description in your project. Codex loads it when a task matches its description.

Can I use Dynamo PR Description 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 DynamoDS/Dynamo --skill dynamo-pr-description -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/dynamo-pr-description, .gemini/skills/dynamo-pr-description, .github/skills/dynamo-pr-description and .opencode/skills/dynamo-pr-description in your project.

What does Dynamo PR Description need to run?

SKILL.md names no scripts, command-line tools or credentials: Dynamo PR Description is instructions for the agent only.

Does Dynamo PR Description 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 Dynamo PR Description 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 Dynamo PR Description use?

Dynamo PR Description is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Dynamo PR Description use?

About 880 tokens (SKILL.md is roughly 3.5k 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 Dynamo PR Description?

Skills that share tags, products or a category with Dynamo PR Description: Link Ticket To Session (JayantDevkar/claude-code-karma, 329 stars), Adhoc PR (shopsys/shopsys, 350 stars), Code Review (sortie-ai/sortie, 196 stars) and Review Release Notes (chef/chef-web-docs, 143 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Dynamo PR Description?

DynamoDS (a GitHub organization) maintains it in DynamoDS/Dynamo, which has 2,033 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on October 7, 2026.

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