Menu
Use when a TypeScript or React codebase needs dead-code detection or safe unused-code removal with TSR, especially for unused exports, unused files, `.tsrignore`, and gradual cleanup workflows.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Route work in the `~/.apm` global APM workspace: decide what owns a change, which path is the source of truth, and which APM rollout / `mise` task to run. Use for skill update and redistribution requests (`skillアップデートして再配布して`, `再配布`), `apm.yml` / `apm.lock.yaml` and managed catalog rollout, manual-skills package state, orphaned APM packages, checked-out external dependency repositories, optional repository-scoped skill packages, and `apmのバージョンあげて` / pinned `apm` source checks. For skill body, description, script, reference, or asset design itself, coordinate with `skill-creator`; for general mise usage outside the APM workspace (including `mise upgrade TOOL` and `minimum_release_age`), use `mise`.
Use when deciding whether to install, enable, or troubleshoot Headroom context compression for local AI agent workflows, especially MCP, proxy, or agent-wrap usage.
Use when adding or reviewing CI-stability hooks and gates: Lefthook/pre-commit/pre-push configuration, aligning local push gates with GitHub Actions, deciding commit-vs-push gate scope, or migrating pre-commit to Lefthook. For mise task design itself, use `mise`; for debugging failing PR checks, use `gh-fix-ci`.
Curate external agent collections into this APM workspace. Use when evaluating whether an outside agent repository can be installed through APM, importing selected agents into catalog/agents, recording provenance, or refreshing curated agents from upstream.
Use when creating, rebuilding, or updating a Google Forms survey from a Markdown survey spec such as SURVEY_QUESTIONS.md, especially when the form should stay synchronized with question text, required flags, Google Forms item types, scale labels, and removed-question notes.
Slack app management knowledge for app settings, manifests, OAuth installs, scopes, bot users, Marketplace settings, App Home, display names, sender names, mrkdwn message formatting, and safe workspace-visible changes. Use when diagnosing or changing a Slack app, installed app, bot user, app label, DM header, chat sender, message text decoration, Slack links, block quotes, app approval/install state, token impact, Slack API app settings, Slack Marketplace settings, or stale Slack app name propagation.
| name | tsr |
| description | Use when a TypeScript or React codebase needs dead-code detection or safe unused-code removal with TSR, especially for unused exports, unused files, `.tsrignore`, and gradual cleanup workflows. |
This skill is for safe dead-code cleanup in TypeScript or React projects. Start by checking configuration and running detection mode first. Do not jump directly to deletion.
Detailed config, examples, and migration notes already live in examples/, README.md, and references/.
.tsrignore を調整したい使わない場面:
.tsrignore に逃がすRun the skill-local config loader first. Resolve config-loader.ts from the installed tsr skill directory instead of hard-coding a user-specific home path.
node <installed-tsr-skill-dir>/config-loader.ts
pnpm tsr:check > /tmp/tsr-report.txt
pnpm tsr:fix
pnpm tsr:fix の前に、report の中身を確認すること。
TSR config は次の順で解決される。
.tsr-config.json~/.config/tsr/config.jsontsr-config.default.json初手で設定が怪しい場合は、削除より先に config-loader.ts の出力を確認する。
entryPatterns が対象を広げすぎていないか.tsrignore に framework 特有の除外が入っているかmaxDeletionPerRun が大きすぎないか--write へ進む.tsrignore を更新せずに report だけ見て判断するconfig-loader.tsexamples/*.jsontsr-config.schema.jsonreferences/workflow.md.tsrignore guide: references/tsrignore.mdMIGRATION.md