Diagnose pixiv-cli GitHub Actions failures and verify current-head quality, platform, PR-verification, native/browser, and release evidence. Use for CI readiness, failed or stalled runs, or an explicitly authorized rerun/cancel/dispatch; default to read-only evidence gathering.
Write a pixiv-cli commit message grounded in the staged diff. Use when asked to name or prepare a commit, not to stage, commit, push, merge, or publish automatically.
Edit pixiv-cli documentation, AGENTS.md, client bridges, repository maintenance skills, or the distributed product skill. Use when commands, APIs, configuration, architecture, testing, or contributor workflows change and their documentation must stay accurate and portable.
Add, change, or review a pixiv-cli Pixiv or FANBOX MCP tool, including schema, SDK routing, structured output, errors, and stdio behavior. Use for MCP tool implementation or compatibility work, not routine installed-CLI operation.
Prepare, update, or verify a pixiv-cli pull request using its current template, trusted verification policy, reviewed diff, and head-specific check results. Use for contributor handoff or PR readiness; merging, live /test execution, and releases are separate actions.
Prepare pixiv-cli bilingual versioned release notes, audit source coverage, coordinate an authorized version release, or recover its independent publishers. Use for release preparation and historical Release synchronization, not routine feature PR metadata.
Review pixiv-cli working changes, commits, or pull requests for requested behavior, Go design, SDK/CLI/MCP contracts, security, native boundaries, and verification gaps. Use for independent review or pre-delivery self-review; review-only unless edits are authorized.
Operate the installed pixiv CLI to search works and users, reverse-search images with SauceNAO or ascii2d, inspect Pixiv references, read feeds and rankings, and perform explicitly authorized bookmark, follow, comment, account, or download actions. Use only for an explicit Pixiv or pixiv-cli request, a pixiv command…
In pixiv-cli, write and review intent-focused code comments, API documentation, docstrings, and numbered workflow stages. Use when an implementation changes a contract or non-obvious invariant, a multi-stage function needs navigation, or existing comments are noisy or stale. Keep natural-language choice neutral and…
Implement, diagnose, refactor, and design pixiv-cli Go changes using its actual CLI, SDK, MCP, account, and storage boundaries. Use before source changes or engineering design; choose the separate native or MCP workflow when that boundary is involved. No personal skills are required.
Change or validate pixiv-cli Rust ugoira, cgo/FFI, committed static libraries, vendored dependencies, Linux ABI, and native runner evidence. Use when native sources, library hashes, target toolchains, or encoder behavior change; not for routine Go-only or documentation edits.
Select and run pixiv-cli regression, TDD, document, SDK, CLI/MCP, and build checks. Use when changing behavior, reproducing a bug, choosing test scope, or reporting readiness. Separates offline fixtures, native evidence, and explicitly authorized live API tests.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: