Use for iQ-Studio release changelog drafting and review. Apply when the user asks for a changelog entry, a vX.Y.Z summary, a release-notes draft, or guidance on what should appear in `docs/changelog.md`. Anchors version scope to the git tag and reconciles every bullet against the current repository state.
Use for general iQ-Studio repository changes and routing: launcher changes, mod/ Python modules, shell scripts, tutorials, README updates, benchmarks, AVL docs, SDK docs, model-deploy workflows, offline package docs, and deciding which focused iQ-Studio skill to apply. Use iq-studio-literacy for prose standards and iq-studio-formatting for Markdown structure. Do not use for unrelated repositories.
Use for iQ-Studio commit message drafting, commit-log review, and deciding how to split staged or unstaged changes into commits. Apply when the user asks for a commit log, commit message, git commit style, or repository commit principle guidance.
Use for iQ-Studio Markdown structure and repository documentation formatting: image paths, heading strategy, code block labels, command prompts, notes and warnings, relative links, README section names, and audit-tool verification. Use when editing README files, tutorials, benchmarks, AVL docs, SDK docs, model-deploy docs, docs/ pages, or documentation links.
Use for iQ-Studio documentation language quality: official product names, capitalization, table status wording, typo cleanup, punctuation hygiene, and professional English polish. Use when editing or reviewing iQ-Studio Markdown text, README files, tutorials, benchmarks, AVL docs, SDK docs, model-deploy docs, changelogs, and documentation tables.