skills.rest
shopwareLabs
shopwareLabsOFFICIAL
Explore all skills by this author →
WebsiteGitHub

release-info-writing

Draft release notes and upgrade entries from Shopware branch diffs.

41|5|Updated Oct 22, 2025
Search Tags:#upgrade#draft#release-notes#diff-analysis#writing-guidelines#shopware
One-click install
npx skills add https://github.com/shopwareLabs/ai-coding-tools --skill release-info-writing
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-info-writing
Source: https://github.com/shopwareLabs/ai-coding-tools/tree/main/plugins/contributor-writing/skills/release-info-writing
Command: npx skills add https://github.com/shopwareLabs/ai-coding-tools --skill release-info-writing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Draft release notes and upgrade entries that reflect code changes across branches to ensure consistent, compliant documentation.

Core Features & Use Cases

  • Automates generation of RELEASE_INFO-6.x.md and UPGRADE-6.x.md narratives from branch diffs.
  • Enforces Shopware writing rules and category placement using the project's reference guidance.
  • Supports human-in-the-loop review for rationale and migration notes when needed.

Quick Start

Review the current branch changes and generate draft RELEASE_INFO and UPGRADE entries following the standard templates.

Frequently Asked Questions about release-info-writing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I draft release notes from branch diffs for Shopware core changes?▼

You can generate RELEASE_INFO and UPGRADE narratives by analyzing branch diffs against trunk. The output follows Shopware standardized writing rules, category placement, and formatting conventions defined in project reference files.

What is the standard structure for Shopware release notes and upgrade entries?▼

Shopware release notes and upgrade entries follow a standardized structure defined in writing-rules and file-structure references. This includes specific category placement, formatting conventions, and narrative entry styles for RELEASE_INFO and UPGRADE files.

How do I automate release notes generation from code changes across Shopware branches?▼

Automate release notes generation by analyzing branch diffs against the trunk to produce draft narratives. The generated drafts apply Shopware writing rules and structure conventions, supporting human-in-the-loop review for rationale and migration notes.

Can I use this for Shopware 6.x upgrade documentation and release info files?▼

Yes, it supports generating RELEASE_INFO-6.x.md and UPGRADE-6.x.md narratives from branch diffs. The output enforces Shopware writing rules, category placement, and formatting conventions specific to the 6.x file structure.

When do I need human review for generated release notes and upgrade entries?▼

Human-in-the-loop review is needed when rationale and migration notes require contextual judgment beyond code diff analysis. The automated draft provides the structured narrative, and reviewers refine migration guidance before finalizing RELEASE_INFO and UPGRADE entries.

Related Skills

Explore More Content & Communication Skills→
shopwareLabsshopwareLabs
41

pr-description-writing

Draft conventional commit PR titles and Shopware 5-section descriptions.

Official
Advanced
blockscoutblockscout
229

task-to-code

Apply prepared coding-task changes and run defined verification steps.

Official
Advanced
jk278jk278

git-analyzer

Analyze git repositories to summarize commit history and file changes.

Community
Intermediate
harlan-zwharlan-zw
3

release-notes

Generate Nuxt-style release notes and upgrade prompts from commit history.

Community
Advanced