Skills wiki-changelog
📦
wiki-changelog
Content revision r1 Safe
Generate Repository Changelogs from Git History
Teams need quick, readable summaries of repository activity. This skill reviews git history and organizes commits into clear changelog sections.
Supports: Claude Codex Code(CC)
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Agent request
Review the Skillstore skill "wiki-changelog" from https://skillstore.io/skills/sickn33-wiki-changelog.md and its manifest at https://skillstore.io/api/skills/sickn33-wiki-changelog/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "wiki-changelog". Generate a changelog for the last week.
Expected outcome:
- Features: Added account export support and improved onboarding status messages.
- Fixes: Resolved failed login redirects and corrected duplicate notification handling.
- Documentation: Updated setup instructions to match the current environment variables.
Using "wiki-changelog". Summarize commits since the last release.
Expected outcome:
- Breaking Changes: Renamed the project configuration option and included migration guidance.
- Dependencies: Updated core packages to supported versions.
- Refactoring: Simplified repository services without changing user-facing behavior.
Security Audit
Safev5 • 7/7/2026 Open versioned report
Static analysis found no suspicious patterns in the single prompt-only skill file. Manual review found no prompt injection language, data exfiltration intent, or instructions that request unsafe tool use.
1
Files scanned
28
Lines analyzed
0
Review items
0
False positives ignored
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History →
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-wiki-changelog/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-wiki-changelog?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-wiki-changelog?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-wiki-changelog/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-wiki-changelog.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
sickn33. (2026). wiki-changelog security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-wiki-changelog/audits/5BibTeX citation
@techreport{sickn33-sickn33-wiki-changelog-2026,
author = {sickn33},
title = {wiki-changelog security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/sickn33-wiki-changelog/audits/5},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "wiki-changelog security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-07"
url: "https://skillstore.io/skills/sickn33-wiki-changelog/audits/5"
identifiers:
- type: other
value: "skillstore:sickn33-wiki-changelog:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: High 55
Architecture
85
Maintainability
87
Content
69
Community
83
Spec Compliance
What You Can Build
Prepare Release Notes
Create a structured changelog before tagging a new version or sharing a product update.
Summarize Sprint Activity
Review recent commits and explain development progress in clear categories.
Update Project Documentation
Convert repository changes into concise wiki or README update notes.
Try These Prompts
Recent Changelog
Generate a changelog for the recent commits in this repository. Group the changes by type and keep the descriptions user-facing.
Weekly Development Summary
Summarize the last two weeks of git history. Group changes by week, then classify each item as feature, fix, refactor, documentation, config, dependency, or breaking.
Release Candidate Notes
Create release candidate notes from commits since the last tag. Highlight breaking changes, migration notes, and user-facing improvements.
Audience-Specific Changelog
Generate a changelog for product stakeholders. Merge related commits, avoid internal implementation noise, and explain the user impact of each change.
Best Practices
- Run the skill from the repository root so git history and project context are available.
- Ask for a specific date range or tag range when preparing release notes.
- Review breaking change sections before publishing the changelog.
Avoid
- Do not use vague commit messages as final release notes without review.
- Do not include internal-only refactors when the audience needs product changes.
- Do not assume a breaking change exists unless commit history or code context supports it.
Frequently Asked Questions
Does this skill change repository files?
No. The skill describes a workflow for analyzing git history and writing changelog text.
Can it generate release notes for a specific version?
Yes. Ask for commits since a tag, branch point, or date range.
Does it need network access?
No. The skill is designed to use local git history and local project documentation.
How does it categorize changes?
It groups commits into features, fixes, refactoring, documentation, configuration, dependencies, and breaking changes.
Will it detect every user impact?
Not always. Clear commit messages and project documentation improve the quality of the changelog.
Which assistants can use this skill?
The report lists support for Claude, Codex, and Claude Code.