Menú
Generate a changelog entry in HISTORY.md from git changes. Use when user requests changelog, version update, or history entry.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Create or update a release version entry in version.md. Use when drafting a new version, cutting a release, or when the user asks to create or update release notes.
Application overview for frename. Use when: orienting to the project for the first time, deciding which crate or module to touch, understanding what the app does end-to-end, looking up where a concept lives (tags, files, ordering, colors), or understanding keyboard shortcuts and the tag/file lifecycle.
Core development guide for frename-core. Use when: adding or changing traits (StoredTagStore, AppStateStore), modifying TagList logic, working with OrderedCollection, adding Tag fields, changing FileSnapshot/FileTagger, writing core tests, or adding database schema/migrations.
Image preview implementation guide for frename. Use when: adding or changing the media_viewer feature, working with FileKind classification, changing how FolderWorkspace opens files, adding JPEG or HEIC/HEIF decoding, understanding the no-unload path for images, or moving video_player into media_viewer.
UI + core combination guide for frename. Use when: wiring a new feature that spans both UI state and core data, deciding where logic lives (core vs UI), connecting a new message to a core operation, changing how file workspace or folder workspace coordinates with TagList or AppDatabase, or understanding the data flow between a user action and disk write.
Undo/redo implementation guide for frename. Use when: implementing the undo infrastructure in frename-core, adding a new undoable command, wiring Ctrl+Z/Ctrl+Y in the UI, or understanding how History, UndoContext, and commands interact.
| name | changelog |
| description | Generate a changelog entry in HISTORY.md from git changes. Use when user requests changelog, version update, or history entry. |
| disable-model-invocation | false |
Generate a changelog entry in HISTORY.md based on recent git changes.
Follow these steps to create a changelog entry:
Try to get git changes using one of these approaches:
git diff HEADgit log -1 --statgit diff <commit1> <commit2> --statIf git is not available, ask the user what changes were made.
Read HISTORY.md and extract the latest version number at the top of the file.
# X.Y.Z Title# 0.1.0 Initial project setupIncrease the minor version (Y) by 1 and reset the patch (Z) to 0:
0.1.0 → 0.2.00.2.5 → 0.3.01.9.0 → 1.10.0Categorize the changes into one or more of these sections:
Summarize each change in 5-12 words.
Create a new entry at the TOP of HISTORY.md with this format:
# {version} {5-word title}
## {Section}
- {change description 5-12 words}
- {change description 5-12 words}
- {change description 5-12 words}
{blank line before previous entry}
# 0.3.0 Added user authentication system
## Added
- User login and registration endpoints
- JWT token generation and validation
- Password hashing with bcrypt
- Session management middleware
# 0.2.0 Database integration complete
## Added
- PostgreSQL database connection pool
- Migration system with versioning