cc74ad0bd0
Some checks failed
ci/woodpecker/push/woodpecker Pipeline failed
- .woodpecker.yaml: image paths -> library/autojanet-{agent,dispatcher}
- .woodpecker.yaml: secret names RS_HARBOR_USER / RS_HARBOR_PASS (global)
- container/Dockerfile: restore COPY skills/, skills/ populated from opencode config
- skills/: 84 opencode skills bundled into image
- k8s/manifests: update image refs to library/
33 lines
1.1 KiB
Markdown
33 lines
1.1 KiB
Markdown
---
|
|
name: wiki-changelog
|
|
description: "Analyzes git commit history and generates structured changelogs categorized by change type. Use when the user asks about recent changes, wants a changelog, or needs to understand what changed in th..."
|
|
risk: unknown
|
|
source: community
|
|
date_added: "2026-02-27"
|
|
---
|
|
|
|
# Wiki Changelog
|
|
|
|
Generate structured changelogs from git history.
|
|
|
|
## When to Activate
|
|
|
|
- User asks "what changed recently", "generate a changelog", "summarize commits"
|
|
- User wants to understand recent development activity
|
|
|
|
## Procedure
|
|
|
|
1. Examine git log (commits, dates, authors, messages)
|
|
2. Group by time period: daily (last 7 days), weekly (older)
|
|
3. Classify each commit: Features (🆕), Fixes (🐛), Refactoring (🔄), Docs (📝), Config (🔧), Dependencies (📦), Breaking (⚠️)
|
|
4. Generate concise user-facing descriptions using project terminology
|
|
|
|
## Constraints
|
|
|
|
- Focus on user-facing changes
|
|
- Merge related commits into coherent descriptions
|
|
- Use project terminology from README
|
|
- Highlight breaking changes prominently with migration notes
|
|
|
|
## When to Use
|
|
This skill is applicable to execute the workflow or actions described in the overview.
|