Menü
Generate or update CHANGELOG.md from git history for a release.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Use when designing memory or persistent context for an agent — deciding what to persist vs. recompute, how to retrieve only what's relevant, and how to summarize/compact history to fit the context window. Use when an agent forgets, bloats its context, or repeats work.
Interactive installer for Rosetta. Guides users through selecting and installing skills and language-specific rules at user-level or project-level, verifies paths, and optionally optimizes installed files.
Instinct-based learning system that observes sessions via hooks, creates atomic instincts with confidence scoring, and evolves them into skills, commands, and agents.
Use when building or reviewing an evaluation for an LLM feature — assembling a representative test set, choosing pass criteria (exact match, programmatic checks, rubric, or LLM-as-judge), and catching regressions. Use when asking "how do I know this prompt or model change is better?"
Use when writing or reviewing a prompt for an LLM — making it specific, structured, and testable (clear task, role/context, examples, an explicit output contract, decomposition, room to reason) and avoiding the anti-patterns that make prompts brittle. Provider-agnostic.
Pattern for progressively refining context retrieval to solve the subagent context problem.
| name | changelog |
| description | Generate or update CHANGELOG.md from git history for a release. |
| disable-model-invocation | true |
Update CHANGELOG.md for version $1 (default: Unreleased if no version given).
Steps:
git describe --tags --abbrev=0 (if none, use the repo's
first commit).git log <prev>..HEAD --pretty=format:'%s'.feat: → Added, fix: → Fixed, perf:/refactor: → Changed, etc.).CHANGELOG.md exists, insert a new version block at the top under any Unreleased
section, preserving prior entries. If it doesn't exist, create one with the standard
Keep a Changelog header.keep-a-changelog skill for exact formatting and heading conventions.Write human-readable entries, not raw commit subjects — collapse noise, keep the signal.