Skip to content
TrustedSkillsbeta
Back to all skills

Generate Pr Description

Checked
lichens-innovation·vlatest·backend·MIT

Automatically crafts clear, concise pull request descriptions summarizing code changes and their purpose.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add lichens-innovation/ai-dev-tools --skill generate-pr-description -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

lichens-innovation

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned lichens-innovation/ai-dev-tools at b296ea020c.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
b296ea020c
Manifest
skills/generate-pr-description/SKILL.md
Scanned
6 files, 526 lines
Copies in repo
2 — all of them scanned
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill generates descriptions for pull requests (PRs). It takes a list of changes and automatically crafts a concise summary suitable for inclusion in a PR. The generated description can be used to clearly communicate the purpose and scope of code modifications to reviewers.

When to use it

  • When you need to quickly create a PR description without manually writing one.
  • For projects with frequent small changes where detailed descriptions are time-consuming.
  • To ensure consistency in PR descriptions across a development team.
  • When automating the creation of pull request documentation.

Key capabilities

  • Generates concise PR descriptions.
  • Accepts a list of code changes as input.
  • Suitable for various project types and sizes.

Example prompts

  • "Generate a PR description from these changes: [list of changes]"
  • "Create a pull request summary based on the following modifications: [list of changes]"
  • “Write a short description for this PR: [list of changes]”

Tips & gotchas

The quality of the generated description depends heavily on the clarity and detail provided in the input list of changes. Ensure the change list is well-formatted and descriptive for optimal results.