Menu
Generate a changelog entry from recent git commits. Use when preparing a release or documenting what changed between versions.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Improve a SKILL.md file by applying missing or weak skill-authoring patterns (17 patterns across 7 categories). Use when a skill needs strengthening, after running skill:check to identify gaps, or when creating a new skill from scratch. Do NOT use for prompt-level improvements (use prompt:enhance instead) or for evaluation only (use skill:check instead).
Run a baseline-enhance-reeval loop on a SKILL.md to measure improvement. Generates targeted test cases for enhanced patterns to ensure the comparison reflects actual improvement in changed areas. Use when testing whether skill:enhance actually improves eval scores, measuring skill quality before and after changes, or automating the measure-enhance-measure workflow. Do NOT use for evaluation only (use /eval-run instead), for enhancement only (use skill:enhance instead), or for setting up eval infrastructure (use /eval-analyze and /eval-dataset instead).
Evaluate a SKILL.md file using three-layer linting: schema validation, 17 skill-authoring patterns, and optional substance review (--deep). Use when reviewing skill quality, checking pattern coverage, testing activation metadata, or assessing a skill before sharing. Add --deep for qualitative substance review. Do NOT use for prompt-level analysis (use prompt:skill-checker instead) or for enhancing/rewriting skills (use skill:enhance instead).
Deploy a service to the staging environment with health checks and rollback. Use when asked to deploy, push to staging, release to staging, or test a deployment. Do NOT use for production deployments (use deploy:production instead) or for CI/CD pipeline configuration.
Format source code files
Run database migrations against the target environment. Use when applying schema changes, running pending migrations, or checking migration status. Do NOT use for seed data insertion or database backups.
| name | docs:changelog |
| description | Generate a changelog entry from recent git commits. Use when preparing a release or documenting what changed between versions. |
| argument-hint | <from-tag> [<to-tag>] |
| user-invocable | true |
Generate a formatted changelog entry from git commit history between two tags.
If only from-tag is provided, use HEAD as the end point. If both tags are provided, generate the changelog for commits between them.
git log ${from_tag}..${to_tag} --oneline --no-merges
Group commits by type using conventional commit prefixes:
feat: -> Featuresfix: -> Bug Fixesdocs: -> Documentationrefactor: -> Refactoringtest: -> Testschore: -> MaintenanceCommits without a recognized prefix go into "Other Changes".
Output in Keep a Changelog format:
## [version] - YYYY-MM-DD
### Features
- Description (commit-hash)
### Bug Fixes
- Description (commit-hash)
### Documentation
- Description (commit-hash)
Search commit messages and bodies for "BREAKING CHANGE:" or commits with ! after the type prefix. If found, add a "Breaking Changes" section at the top of the changelog entry.
git log ${from_tag}..${to_tag} --grep="BREAKING CHANGE" --format="%h %s"