スキル wiki-changelog
📝

wiki-changelog

安全

Generate Changelogs from Git History

Manually compiling changelogs from git history is time-consuming and error-prone. This skill automatically analyzes commit history and generates structured, categorized changelogs organized by change type and time period.

対応: Claude Codex Code(CC)
🥉 75 ブロンズ
1

スキルZIPをダウンロード

2

Claudeでアップロード

設定 → 機能 → スキル → スキルをアップロードへ移動

3

オンにして利用開始

テストする

「wiki-changelog」を使用しています。 Generate a changelog for the past week

期待される結果:

## Changelog - Last 7 Days

### Features 🆕
- Add user authentication flow (2024-01-15)
- Implement password reset functionality (2024-01-14)

### Fixes 🐛
- Resolve login redirect issue on mobile (2024-01-13)
- Fix timezone handling in date picker (2024-01-12)

### Documentation 📝
- Update API documentation with new endpoints (2024-01-11)

### Dependencies 📦
- Upgrade React to v18.2.0 (2024-01-10)

「wiki-changelog」を使用しています。 What changed in the last month? Include breaking changes.

期待される結果:

## Changelog - Last 30 Days

### Breaking Changes ⚠️
- **Migration Required**: Rename `User.getProfile()` to `User.profile()` - update all references
- **Migration Required**: API v2 endpoints now require authentication header

### Features 🆕
- Multiple new features listed...

### Fixes 🐛
- Multiple bug fixes listed...

セキュリティ監査

安全
v1 • 2/25/2026

Static analysis flagged 4 high-risk patterns related to 'weak cryptographic algorithm' at lines 3, 22, 27, and 32. This is a FALSE POSITIVE - the skill contains no cryptographic code. The analyzer misidentified common words in the markdown documentation. The skill is a simple changelog generator that reads git log data and produces structured output. No network calls, no external commands, no file writes, no environment access.

1
スキャンされたファイル
33
解析された行数
0
検出結果
1
総監査数
セキュリティ問題は見つかりませんでした

検出されたパターン

Weak Cryptographic Algorithm (FALSE POSITIVE)
監査者: claude

品質スコア

38
アーキテクチャ
100
保守性
87
コンテンツ
50
コミュニティ
100
セキュリティ
100
仕様準拠

作れるもの

Generate Release Notes

Quickly produce release notes by analyzing recent commits and categorizing all changes since the last release.

Track Project Activity

Understand what has changed in a project over time by viewing a structured summary of recent development activity.

Onboard Team Members

Help new team members understand recent changes and the current state of the project through organized changelogs.

これらのプロンプトを試す

Basic Changelog Request
Use the wiki-changelog skill to generate a changelog for this repository. What changes have been made recently?
Release Notes Request
Generate a changelog for version X.X.X release. Include all features, bug fixes, and any breaking changes.
Weekly Summary
Analyze the git history and provide a weekly summary of all changes, grouped by category like features, fixes, and documentation updates.
Breaking Changes Report
Generate a changelog that highlights all breaking changes and includes migration notes for upgrading.

ベストプラクティス

  • Ensure commit messages follow a consistent convention (Conventional Commits recommended) for accurate categorization
  • Review generated changelogs before publishing to ensure terminology matches project standards
  • Use the skill regularly (weekly or before each release) to maintain up-to-date changelogs

回避

  • Do not rely solely on automated categorization - verify that commits are grouped correctly
  • Avoid using vague commit messages like 'fix', 'update', 'changes' which reduce changelog usefulness
  • Do not skip reviewing breaking changes - always verify migration notes are accurate

よくある質問

Does this skill write files to my repository?
No. This skill only reads git history and generates changelog output. It does not modify any files.
How does the skill categorize commits?
The skill analyzes commit messages and classifies them based on keywords: Features (feat, add), Fixes (fix, bug), Refactoring (refactor), Docs (docs), Config (config), Dependencies (deps), and Breaking (break).
Can I customize the categories?
Currently the categories are predefined. You can modify the skill code to add custom categories if needed.
What if my commit messages are not descriptive?
The quality of the changelog depends on commit message quality. Encourage team members to write descriptive commit messages for better results.
Does this work with git submodules?
The skill analyzes the main repository history. Submodule changes would need to be tracked separately.
Can I generate changelogs for specific time periods?
Yes. The skill groups commits into daily (last 7 days) and weekly (older) periods by default. You can request specific date ranges in your prompt.

開発者の詳細

ファイル構成

📄 SKILL.md