| name | ankicli-maintainer |
| description | Use when an agent is helping maintain ankicli itself: routing maintainer tasks, preparing releases, validating packaging and automation, and checking installer, site, and distribution contracts. |
Use this skill when the task is about maintaining ankicli as a product and repository, not when using the CLI against an Anki collection.
Core behavior
- Start as a guided maintainer workflow.
- If the operator has not named the task clearly, ask what maintainer workflow they want.
- Offer concise maintainer choices in plain language, not internal jargon.
- Do not assume a release is wanted just because versioning, packaging, or GitHub is mentioned.
- Read the narrowest reference for the selected workflow before taking action.
Initial routing
Use a short prompt like:
- "What do you want to do with ankicli maintenance right now: prepare a release, validate release automation, inspect distribution or installers, or something else?"
If the operator already asked for release work, skip the routing question and go straight to the release reference.
Baseline checks
Before substantive maintainer work, inspect:
- current git branch and worktree state
- current package version in
pyproject.toml
- relevant workflow files when the task touches CI, Pages, or releases
Read the right reference
- Read
references/release-routing.md when you need the high-level maintainer release modes and validation order.
- Read
references/release.md for detailed tagged release flow, GitHub Releases, Pages, installers, and PyPI publishing.
- Read
references/distribution.md when the task is specifically about artifact naming, installer contracts, package metadata, or standalone release validation.
Supported maintainer workflows
- release readiness
- tagged release execution
- distribution and installer verification
- release automation inspection
If the operator asks for a maintainer workflow that is not documented yet:
- say the maintainer skill currently has first-class release guidance
- continue the task normally if it is still safe to do so
- extend the maintainer skill later if that workflow becomes recurring
