Menu
SkillsMP has collected 20 skills from nuncaeslupus/ai-chat-exporter. Open a skill to review its source and details.
Showing 20 of 20 collected skills.
When the user needs claude-arsenal/ set up in a host repo, or wants to register a workspace via --workspace. Re-running is safe (refreshes stale bundle files only). Do NOT use to add tasks (see queue-add) or resume the worker loop (see continue).
Use whenever anything under src/core/parsers/ is being added or repaired — capturing a live DOM, deriving selectors, implementing a BaseParser subclass, and verifying live that every widget the chatbot renders survives into an export. Triggered by "add a…
Use whenever anything under src/core/exporters/ is being added or repaired — a new output format, a content type missing from some formats, or an exported file that will not open. Triggered by "add EPUB/CSV export", "add a new export format", "images are…
When the user wants to resume work or run the worker loop — picks the next unblocked task, optionally scoped by tag(s) and/or a workspace, or matched by title text. Use /continue [TAG … | WORKSPACE | search-text]. Do NOT use before running init.
Use whenever the user wants to turn a coverage.py report into a ranked list of the highest-value missing tests — runs analyze_coverage.py over coverage.json and surfaces contiguous missing-line runs marking whole untested functions or branches. Triggers —…
Use whenever a uv-managed Python project's dependencies need upgrading safely — the uv lock --upgrade, pip-audit (CVEs), test-gate, classify-breakage runbook. Runs compare_lockfile.py to split lockfile churn into direct vs transitive before a transitive bump…
When the user is defining the technical solution after discovery — contracts, task split, risk register, sequencing. Owns scripts — validate_plan. Do NOT use for problem investigation (see specify), implementation (see execution), or PR review (see review).
When the user is implementing code changes from a design — code change, tests, merge-ready output. Do NOT use for investigation (see specify), design (see design), or routine one-off scripts that bypass the design step.
Use whenever the user wants an objective PASS/FAIL on a task's measurable acceptance gate from status/plan.md, with the measured numbers — runs run_gate.py to read the gate (metric, op, threshold) and recorded evidence, or audit every task's gate at once.…
Use whenever the user is creating commits, opening pull requests, or waiting on PR review/CI feedback — applies Conventional Commits + branch naming, then polls the open PR for review-bot reactions and CI status, addresses each comment inline or replies, and…
Use when the user wants to enable, configure, or troubleshoot Claude Code's built-in LSP tool for a project — detects language manifests (pyproject.toml, package.json, go.mod, Cargo.toml, …), asks which languages to enable, then prints the LSP binary and…
Use when the user wants to triage a Python project's surviving mutmut mutants after a run — runs the analysis script, classifies each survivor as REAL_GAP, EQUIVALENT, or UNTESTABLE, and reports the test fixes worth making. Triggers — "analyze mutmut…
Use whenever a Python package is ready to publish to PyPI — the build, twine check, version bump, tag, and upload runbook. Runs validate_release.py to catch version drift (pyproject vs __version__ vs the intended tag) and stale dist/ artifacts before upload.…
Use whenever a Python project needs scaffolding or retrofitting to the arsenal defaults — uv, ruff, strict mypy, the standard Makefile, a 3.12+ floor. Runs analyze_project.py to report the missing pieces and applies them; flags a models/*.json spec dir for…
When the user wants to add a task to the claude-arsenal queue. Do NOT use to update or remove existing tasks.
When the user wants queue progress counts by status, or to audit the queue for inconsistencies (orphans, broken deps, false-done). Do NOT use to modify task status.
When the user is reviewing a PR, diff, design doc, or proposal — risks, tech debt, standards compliance. Do NOT use for implementation (see execution), design (see design), or release sign-off (see ship).
Use whenever the user signals end-of-job, invokes /session-end, or a Stop hook fires at conversation close — three steps. (1) write status/handoff.md if host repo opts in; (2) retrospective scan for repeated errors and proposed skill updates; (3) PR audit —…
When the user is confirming a change is ready for production before merge — compatibility, tests, observability, rollback. Do NOT use for implementation (see execution) or PR review (see review).
When the user is investigating a problem or scoping a new feature with unclear impact — analyzes it and proposes options. Owns scripts — validate_spec. Do NOT use for already-scoped work (see design), implementation (see execution), or routine code edits.