القائمة
Generate release notes from git history and CHANGELOG. Formats for GitHub Release, Slack, or email. Use before tagging a release.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Generate or update OpenAPI specification from TypeScript/Express route definitions. Validate spec-to-code consistency. Use after adding or changing API endpoints.
Stack-agnostic Clean Code audit — module size, function-length/complexity (via your project's existing linter), long parameter lists, TODO/FIXME/HACK markers, commented-out code, debug-print leakage, and optional duplication detection. Produces a structured findings report with optional fix suggestions. Use before merges, at end of a feature, or as a regular hygiene pass.
Run a comprehensive code review across architecture, security, testing, naming, and patterns. Invokes relevant reviewer agents in sequence. Use before merging features or at the end of a phase. With --quorum, dispatches multi-model analysis for higher confidence.
Generate, review, test, and deploy database schema migrations. Use when adding columns, creating tables, or changing schema.
Scan TypeScript/Node.js project dependencies for vulnerabilities, outdated packages, and license issues. Use before PRs, after adding packages, or on a regular schedule.
Guided plan execution — list available plans, estimate cost, choose mode, and execute with live progress. Use when you want to run a hardened plan through the orchestrator.
| name | release-notes |
| description | Generate release notes from git history and CHANGELOG. Formats for GitHub Release, Slack, or email. Use before tagging a release. |
| argument-hint | [version tag, e.g. 'v1.2.0'] |
| tools | ["run_in_terminal","read_file"] |
"Generate release notes" / "Prepare release" / "What changed since last release?"
# Find the last tag
git describe --tags --abbrev=0
# List commits since last tag
git log $(git describe --tags --abbrev=0)..HEAD --oneline --no-merges
If no tags found → ask user for the commit range to use.
Parse commit messages using conventional commit prefixes:
| Prefix | Category | Show In Notes |
|---|---|---|
feat | New Features | ✅ Always |
fix | Bug Fixes | ✅ Always |
perf | Performance | ✅ Always |
docs | Documentation | ✅ If significant |
refactor | Internal | ⚠️ Only if user-visible |
test | Tests | ❌ Skip |
chore | Maintenance | ❌ Skip |
ci | CI/CD | ❌ Skip |
Read CHANGELOG.md for additional context:
Format for GitHub Release:
## What's New
### Features
- **Feature name**: brief description (#PR)
### Bug Fixes
- Fix description (#PR)
### Performance
- Improvement description (#PR)
## Breaking Changes
- (list any breaking changes with migration steps)
## Contributors
- @username (N commits)
| Shortcut | Why It Breaks |
|---|---|
| "The commit messages are good enough" | Commit messages are for developers. Release notes are for users — different audience, different detail level. |
| "Nobody reads release notes" | Users, support teams, and auditors rely on release notes. Missing notes cause support tickets and compliance gaps. |
| "I'll write them after release" | Post-release notes are always incomplete. Context fades fast — write them while the work is fresh. |
After completing this skill, confirm:
git log range verified)search_thoughts("release", project: "Falsify", created_by: "copilot-vscode", type: "decision") — load prior release decisions, breaking change precedents, and versioning conventionscapture_thought("Release: v<version> — <key changes summary>", project: "Falsify", created_by: "copilot-vscode", source: "skill-release-notes") — persist release history for future changelog continuity