tokyubevoxelverse

Test a repository's setup documentation by executing it literally in a clean environment. Use to find where a README's install, build, or run instructions are wrong, outdated, or silently assume undocumented tools, versions, services, or steps.

Resurrect a dead repository. Use when a project no longer installs, builds, or runs because it has aged — broken dependencies, deprecated APIs, dead tooling, registry rot, runtime drift. Revives it incrementally, keeping a verified working state at every step.

Turn a vague bug report into a minimal, runnable reproduction. Use when the report is "it crashes sometimes" / "it's broken on some inputs" and the fix needs the smallest script or test that reliably triggers the bug first.

Determine whether the next release is legally a patch, minor, or major by diffing the public API surface against the last published version. Use before cutting a release, when reviewing "is this breaking?", or when writing honest release notes.

Write an end-of-session handoff note — what changed, what's half-done, what's risky, exact next steps — for a teammate or future self. Use at the end of a work session, before a vacation, or when transferring work-in-progress to someone else.

Reconcile a long-diverged fork with its upstream. Use when a fork has drifted for months or years and the user wants to catch up to upstream while keeping only the local changes that still matter — rebuilt as a clean, minimal patch set.

Give a repository a full health exam — doc rot, dependency staleness, CI decay, git hygiene, dead links, docs contradicting code — and grade it. Use when the user wants to know what quietly rotted, or a prioritized maintenance list.

Review a pull request or diff adversarially — by trying to break it with hostile tests rather than reading and approving. Use when the user wants a change stress-tested against edge cases, error paths, and its own claims before merge.

Triage a repository's issue backlog — dedupe, label, flag missing repro info, draft replies, and rank what's worth fixing. Use when a maintainer faces a pile of open issues and wants order restored without closing things rudely or blindly.

Prepare a private repository for safe open-sourcing. Use when the user wants to make a repo public and needs the secrets sweep (code AND git history), personal-info scrub, license and community files, and a go/no-go checklist.

Hunt down and fix flaky tests. Use when a test suite fails intermittently, CI needs re-runs to go green, or the user wants to know which tests are flaky versus genuinely broken — and why.

Investigate why a strange piece of code exists before anyone deletes it (Chesterton's fence). Use when the user points at a weird line, hack, magic constant, or workaround and asks why it's there, whether it's still needed, or if it's safe to remove.