Agent-Skills.md

Agent Skills: update-pr-description-and-title

Update the current PR description from the repo PR template and set a conventional-commit title based on the PR changes.

UncategorizedID: michaelvessia/nixos-config/update-pr-description-and-title

Repository

michaelvessia/nixos-config
MichaelVessia
2

Install this agent skill to your local

pnpm dlx add-skill https://github.com/MichaelVessia/nixos-config/tree/HEAD/modules/programs/agents/shared/skills/update-pr-description-and-title

Skill Files

Browse the full folder contents for update-pr-description-and-title.

Download Skill

Loading file tree…

modules/programs/agents/shared/skills/update-pr-description-and-title/SKILL.md

Skill Metadata

Name
update-pr-description-and-title
Description
Update the current PR description from the repo PR template and set a conventional-commit title based on the PR changes.

Context

  • Current PR: !gh pr view --json number,title,url,body,files,commits,baseRefName 2>/dev/null || echo "No PR found"

Your task

Update the current PR's description to adhere to the repository's PR template, then set the PR title in conventional-commit format.

  1. Find the PR template by checking .github/PULL_REQUEST_TEMPLATE.md, .github/PULL_REQUEST_TEMPLATE/, and .github/pull_request_template.md using Glob.
  2. If a template exists, read it with the Read tool.
  3. Update the PR description using gh pr edit to follow the template structure. Focus on the overall intent and motivation of the PR, not a list of individual changes. Do NOT:
    • Enumerate specific files changed
    • List every commit or diff
    • Describe mechanical edits (renames, imports, etc.) Instead, explain why the change was made, what problem it solves, and any important design decisions. Fill in template sections based on this intent. If you don't know how to fill out a section, leave it empty.
  4. If no template exists, ensure the description includes at minimum:
    • A concise summary of the intent and motivation (not a changelog)
    • Steps to test the PR
  5. Generate a conventional-commit PR title from the actual PR changes:
    • Prefer the dominant type from commit prefixes when available (feat, fix, docs, refactor, test, chore, ci, build, perf).
    • Otherwise infer type from changed files and behavior.
    • Use a concise scope when obvious from touched paths.
    • Format exactly as <type>(<scope>): <summary> if scope exists, otherwise <type>: <summary>.
    • Keep title lowercase (except proper nouns), imperative, and at most 72 chars.
  6. Apply both updates in one command with gh pr edit --title ... --body ....