Menu
Generate release notes from git history between tags, commits, or date ranges
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
General development best practices and common gotchas when working on Biome. Use for avoiding common mistakes, understanding Biome-specific patterns (AST, syntax nodes, string extraction, embedded languages), and learning technical tips.
Guide for creating and writing proper changesets for Biome PRs. Use when a PR introduces user-visible changes (bug fixes, new features, rule changes, formatter changes, parser changes) that need a changeset entry for the CHANGELOG. Trigger when creating changesets, writing changeset descriptions, or choosing the correct change type.
Building AI agents with the Convex Agent component including thread management, tool integration, streaming responses, RAG patterns, and workflow orchestration
Guidelines for building production-ready Convex apps covering function organization, query patterns, validation, TypeScript usage, error handling, and the Zen of Convex design philosophy
How to create, structure, and publish self-contained Convex components with proper isolation, exports, and dependency management
Scheduled function patterns for background tasks including interval scheduling, cron expressions, job monitoring, retry strategies, and best practices for long-running tasks
| name | release-notes |
| description | Generate release notes from git history between tags, commits, or date ranges |
Generate structured release notes from git commit history, organized by category and impact.
since — Starting point: git tag, commit SHA, or relative date (e.g., v0.1.0, abc1234, 2 weeks ago). Defaults to latest tag or last 2 weeks.until — Ending point. Defaults to HEAD.format — Output format: markdown (default), slack, linkedin.Determine the commit range:
# If no `since` provided, find latest tag
git describe --tags --abbrev=0 2>/dev/null || echo "No tags found"
# Get commits in range
git log --oneline --no-merges ${since}..${until:-HEAD}
Parse commits by conventional commit prefix:
feat: / feat(scope): → New Featuresfix: → Bug Fixesrefactor: → Improvementsperf: → Performancedocs: → Documentationchore: / ci: / build: → Internal (omit from public notes)For each feature/fix, read the changed files to understand the user-facing impact:
git diff --stat ${commit}^..${commit}
Group by domain (detect from file paths):
convex/ → Backendpackages/ui/src/ → UIapps/web/ → Web Appapps/desktop/ → Desktop Appagent-service/ or agent-worker/ → AI/Agent Systemsandbox-worker/ → SandboxGenerate release notes in requested format.
# Release Notes — [version or date range]
## New Features
- **[Domain]**: Description of feature ([scope])
## Bug Fixes
- **[Domain]**: Description of fix
## Improvements
- **[Domain]**: Description of improvement
---
*N commits by N contributors over N days*
Focus on 2-3 headline features, business impact framing, no technical jargon. Keep under 1300 characters.
Compact bullet list with emoji prefixes. Link to PR numbers.