Menu
Generate or update CHANGELOG.md from landed git history. Use when the user asks to "write a changelog", "update the changelog", or summarize what changed over the last week/period.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Create a simple, modern HTML review page and run a local browser feedback loop with inline element/text annotations and structured questions. Use when the user wants to discuss or iterate on a design, plan, comparison, scope decision, content draft, or other topic that is easier to review visually than in chat.
Squash the current branch's work into a single commit and open (or update) a GitHub pull request with Graphite (`gt`). Use when asked to "create a PR", "open a pull request", "put this up for review", or to update an existing PR for the current branch.
Ingest a new AnimeGameData (AGD) build end-to-end — deobfuscation mappings, TextMap fallback-list audit, first-seen version index, and corpus regen. Use when bumping AGD_PATH / AGD to a new game version.
Regenerate, audit, commit, and push Istaroth's generated text corpus in the text/ submodule. Use when the user asks to "regen corpus", regenerate committed text output, audit a corpus diff for content loss, or push a previously verified text regeneration.
Identify and add new AnimeGameData field deobfuscation mappings by comparing cleartext and obfuscated AGD revisions. Use when a new Genshin Impact build changes obfuscated JSON field names or when rust/istaroth-agd-regen/src/deob.rs needs a new version mapping block.
Add or revise retrieval-quality eval fixtures under istaroth/rag/eval/retrieval_fixtures/ (one JSON file per category, e.g. breadth.json). Use when asked to add a retrieval eval case, add a new eval category, improve a fixture's ground truth, or harden fixtures against false misses. Fixtures grade whether retrieval surfaces the sources a query needs, measured by passage-anchored facet coverage.
| name | changelog |
| description | Generate or update CHANGELOG.md from landed git history. Use when the user asks to "write a changelog", "update the changelog", or summarize what changed over the last week/period. |
Maintain CHANGELOG.md at the repo root. Run every command from the repo root.
Read the cutoff marker near the top of CHANGELOG.md:
<!--
Last updated through commit: <full-hash> (<short-hash>)
...
-->
Document only commits landed after that hash. If CHANGELOG.md does not
exist yet, ask the user (or infer from the request) how far back to go.
List the commits to document, newest first:
git log <cutoff-hash>..HEAD --pretty=format:"%H|%ad|%s" --date=short
For a fresh changelog with a date bound instead of a hash, use
git log --since="<date>" ....
## Week of YYYY-MM-DD – YYYY-MM-DD.Frontend, MCP, RAG, Backend,
Text/corpus, Dev infra, CI/build, AGD types, Parsing robustness,
Tech debt, Docs, Project/docs. Add a new area label when a recurring one
isn't covered.The Text/corpus area is special: split its sub-bullets into two labeled
groups, new content first, then changes:
- **Text/corpus**
- *New content:*
- <newly extracted categories / data>
- *Enhancements & fixes:*
- <restructuring, keying fixes, titling, corpus regeneration>
Classify a commit as new content when it surfaces game data not previously in the corpus (a new category, newly extracted descriptions/stories). Everything else — restructuring, dedup, keying fixes, human-readable titles, regenerations — goes under Enhancements & fixes.
After writing the entries, set the marker to the newest documented commit
(HEAD of the range). Keep both the full hash and the short hash:
Last updated through commit: <full-hash> (<short-hash>)
Update text commits and submodule-pointer moves into the relevant
corpus entry; don't list them on their own.