Evidence snapshot reviewed Sep 16, 2026GitHub checked Aug 21, 2026
Source-reviewedStandalone SkillFiles & Documents

release-notes

Derive user-facing release notes from recent change history.

At a glance

What it does

Derive user-facing release notes from recent change history.

Capabilities
Files & DocumentsDocumentationRelease Management

Before you choose it

Derive user-facing release notes from recent change history. The supplied pinned skill document describes its trigger and workflow.

Best for

Users who need this workflow in a DSH project.

Common tasks

  • Derive user-facing release notes from recent change history.

Permissions and data

The skill guides a local workflow; external behavior is not independently audited.

Permissions
  • Uses the documented skill workflow.
Data handling
  • Data handling was not independently audited.
External services
  • External services follow the supplied project instructions.
Credentials
  • Credential requirements were not independently tested.

Limitations

  • The skill document does not establish runtime compatibility.

What DSHub checked

  • The source commit and complete skill document were captured.

What DSHub did not check

  • Installation and runtime behavior were not tested.

Pinned install

Primary action

This standalone skill does not have a DSH Plugin install action. Use its source documentation for the delivery method.

Visit the source project ↗

Maintainer source

Skill instructions

View at commit f0d89ff ↗
Maintainer-authored contentCaptured from .agents/skills/release-notes/SKILL.md on Aug 29, 2026. The text and repository-relative media are fixed to commit f0d89ff68651 with content hash ad13de99bb40; provider-hosted badges may update independently. SKILL.md commands are upstream documentation; use the type-correct primary action above and verify it against this pinned source.

name: release-notes description: Use when asked to generate release notes, or when the /release-notes command runs — derive user-facing release notes from the change history since the last release.

Release Notes

Generate user-facing release notes for the current project since the last release.

Procedure

  1. Determine the last release point (git tags) and collect the change set since then (git log / diff of user-facing surfaces).
  2. Classify changes:
    • 新功能 (new features)
    • 改进 (improvements / behavior changes)
    • 修复 (bug fixes)
    • 破坏性变更 (breaking changes — call these out first)
    • 内部 (chore/refactor — omit from user-facing notes or fold into a footnote)
  3. Write notes in the user's language, focused on what changed for users — not implementation details.
  4. Reference issues/PRs where known, keep each bullet one line, group under the sections above.

Constraints

  • Do not fabricate changes — only what the history shows.
  • Breaking changes must be listed first, with migration hints.

Operate deliberately

Install and manage

Prerequisites and target Profile

Target: No native DSH Profile target.

Delivery: Skill Files — https://github.com/ccch1mneyyy/dsh-tui。

Compatibility and access

Requires_host_review: Not established by supplied evidence。

Review compatibility evidence ↗

Risk facts

Execution

Review instructions before use.

Evidence ↗
Evidence and editorial reviewManifest, Bundle patch, distribution and freshness

Immutable evidence

Review status and source activity

Human approved

Approved for publication after reviewing the source-linked content and immutable release record. AI assisted with the draft; the publication decision was human.

Human reviewed Aug 29, 2026, 3:18 PM UTC。GitHub facts last checked Aug 20, 2026, 2:01 PM UTC。

No material source change has been recorded since this evidence baseline.

Next step

Compare ecosystem artifact types →

Subscribe to material changes for release-notes →