AutoTerminalScanClassic

Select a reviewed APM CLI version, then set up, pin, deploy, audit, and update APM-managed agent dependencies safely. Use when creating or editing apm.yml or apm.lock.yaml, choosing or installing APM, adding an Agent Skill, plugin, or MCP dependency, validating a pinned deployment, or preparing a cooldown-aware update proposal.

Set up and use an isolated Git worktree for repository implementation tasks. Use unless the user explicitly requests another workspace arrangement.

Review or create a BepInEx Mono mod for C# project and module structure, plugin identity, game compatibility, dependency boundaries, repository-family alignment, GitHub CI and release automation, package readiness, release metadata, and verification. Use when implementing, reviewing, preparing a release for, diagnosing quality gaps in, or applying a minimal-difference peer rollout to a BepInEx 5 Mono plugin or its build and release workflow.

Review or draft repository commit messages for Conventional Commits format, accurate change summaries, breaking-change footers, and required attribution trailers. Use before creating, amending, or validating a commit.

Maintain a canonical developer changelog and versioned release history. Use when adding or correcting Keep a Changelog entries, prerelease history, compatibility context, or release-source material; not for user-facing release notes or publishing.

Create or review channel-specific release notes from a canonical changelog. Use when checking destination history or publication readiness.

Investigate version-specific Lethal Company mechanics using verified Unity-build evidence, seeded RNG, exhaustive or sampled computation, and runtime observation; produce reproducible, bounded gameplay reports. Use for mechanics questions, full-seed enumeration, sealed-result reuse, Terminal or HUD endpoint interpretation, version comparisons, statistical prediction, or playable-strategy evaluation. Use unity-game-analyze for the underlying decompiled-code and serialized-asset trace.

Review or revise explanatory prose for readability, local structure, audience fit, and preserved nuance. Use for wording in documentation, comments, release notes, issues, pull requests, changelogs, handoff notes, and Agent Skills after the document's purpose and factual ownership are known. Use software-documentation-maintenance instead for repository-wide document maps, canonical ownership, technical evidence, coverage, or migration.

Design, restructure, and maintain a software repository's documentation system, including its required docs/domain, docs/architecture, and docs/operations map, canonical ownership, technical evidence, indexes, links, and change synchronization. Use when creating or migrating developer docs, documenting system behavior or design decisions, establishing documentation rules, or reviewing repository-wide documentation completeness. Pair with prose-quality-check for wording and with a domain skill for specialized technical correctness.

Roll out a validated canonical change from a designated primary repository to compatible peers with only necessary local differences. Use for shared Agent Skills, repository rules, workflows, or documentation conventions.

Create or update repository `.gitignore` rules, including pinned upstream template syncs. Use when changing ignored-file behavior or merging `github/gitignore` content.

Review repository changes for practical security and supply-chain risks. Use when work touches secrets, permissions, untrusted input, dependencies, executable or downloaded artifacts, CI or deployment configuration, containers, or vendored/generated files; skip documentation-only changes with no security-sensitive surface.

Review implementation changes for readability, maintainability, design intent, and verification. Use for source code, tests, scripts, configuration, generated or vendored files, and dependencies; pair with security-check for security- or supply-chain-sensitive changes.

Trace version-specific Unity game behavior through decompiled managed code, scenes, prefabs, prefab variants, ScriptableObjects, bundles, serialized references, and runtime mutation paths. Use when locating an implementation, reconciling code defaults with asset overrides, proving callback or object reachability, comparing Unity builds, or preparing code-and-asset evidence for a game-specific analysis or mod integration. Pair with a domain analysis skill for gameplay interpretation and with a mod quality skill for hook and implementation decisions.