OpenParable
Skip to content
← Back to skills

Changelog Update PR

Development
changelog-update-pr

Changelog Update PR is an Agent Skill for development published in the ScottPlot/ScottPlot repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Update root CHANGELOG.md for exactly the current branch's pull request in ScottPlot. Use when on a contributor PR branch and asked to add or update one concise unpublished changelog entry without summarizing unrelated changes.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/ScottPlot/ScottPlot/blob/HEAD/.agents/skills/changelog-update-pr/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/changelog-update-pr, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

PR Changelog

Edit only CHANGELOG.md.

Fast path:

  1. Run git status --short --branch.
  2. Use branch/upstream only as hints to find the PR; never trust numbers in branch names.
  3. Fetch PR metadata: number, title, author, base branch, linked issues.
  4. Inspect the smallest useful scope, usually changed filenames and git diff --stat <base>...HEAD; read patches only if metadata and filenames are unclear.
  5. In the top unpublished section, update an existing #PR bullet or append one bullet to the current list.

Rules:

  • Summarize only this PR.
  • Keep the entry concise and user-facing.
  • Add new bullets to the end of the latest block.
  • Do not modify text outside this bullet before asking.
  • Include (#PR, #issue) @author when known.

Style:

* Component: Add/Fix/Improve concise description (#PR, #issue) @author

Choose Component from the PR's changed public API, feature, control, cookbook area, or affected file names. Prefer the smallest accurate user-facing name; do not default to a memorized category list. Reuse nearby changelog component wording only when it clearly matches this PR.

Final response: report the text added to the changelog.