'Generate structured changelogs from git history. Use when user asks \'what changed recently\', \'generate a changelog\', \'summarize commits\' or user wants to understand recent development activity.
Installs into .claude/skills of the current project.
Are you the author of Wiki Changelog?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/thiagofernandes1987-create-wiki-changelog-apex)
---
skill_id: knowledge_management.wiki.wiki_changelog
name: "wiki-changelog"
description: "'Generate structured changelogs from git history. Use when user asks \'what changed recently\', \'generate a changelog\', \'summarize commits\' or user wants to understand recent development activity."
version: v00.33.0
status: ADOPTED
domain_path: knowledge-management/wiki/wiki-changelog
anchors:
- wiki
- changelog
- generate
- structured
- changelogs
- history
- user
- asks
- changed
- recently
source_repo: antigravity-awesome-skills
risk: safe
languages: [dsl]
llm_compat: {claude: full, gpt4o: partial, gemini: partial, llama: minimal}
apex_version: v00.33.0
executor: LLM_BEHAVIOR
security: {level: standard, pii: false, approval_required: false}
tier: 2
input_schema:
- name: code_or_task
type: string
description: "Code snippet, script, or task description to process"
required: true
output_schema:
- name: result
type: string
description: "Generated or refactored code output"
- name: explanation
type: string
description: "Explanation of changes or implementation decisions"
---
# Wiki Changelog
Generate structured changelogs from git history.
## When to Use
- 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.
## Diff History
- **v00.33.0**: Ingested from antigravity-awesome-skills community repo
---
## Why This Skill Exists
'Generate structured changelogs from git history.
<!-- SR_40: auto-generated from frontmatter `purpose`/`description` (OPP-Phase3). Expand with domain-specific rationale. -->
## What If Fails
If this skill fails to produce the expected output: (1) verify input completeness, (2) retry with more specific context, (3) fall back to the parent workflow without this skill.
<!-- SR_40: auto-generated from frontmatter `what_if_fails` (OPP-Phase3). -->