with one click
statico
statico contains 11 collected skills from DonaldMurillo, with repository-level occupation coverage and site-owned skill detail pages.
Skills in this repository
Build, test, or debug a statico plugin. Use when the user wants to write a project-specific rule, scaffold a plugin, or investigate plugin behavior.
Reclaim disk space by cleaning build artifacts, dependency caches, and benchmark repos. Auto-invokes before merges, releases, and after big branch switches — or whenever the user asks to clean up, free space, or trim the repo.
Keep statico's user-facing documentation in lockstep with code changes. Auto-invoke proactively whenever the user adds, removes, or modifies CLI flags, subcommands, config keys (`.statico.toml` / `StaticoConfig`), output formats, plugin hooks, plugin protocol fields, the public Rust API (`src/lib.rs` re-exports), template content (`templates/`), or framework profiles. Also invoke when bumping `Cargo.toml` `version`, `rust-version`, or dependency versions that change behavior, and when the user mentions "ship", "release", "publish", or "the docs are stale". Verifies README.md, CHANGELOG.md, the files under `docs/`, the templates under `templates/`, and the example plugin under `examples/plugins/`. Default action is to AUDIT and report drift; only edit when the user confirms or the drift is mechanically obvious (e.g., the README CLI table is missing a flag we just merged).
Run a statico code health analysis on the current project. Presents a human-readable summary of dead code, unused exports, circular dependencies, and overall health score. Use when asked to check code health, find dead code, or review code quality.
Interactive dead code cleanup using statico analysis. Identifies dead files, presents them with context, and helps safely remove them one by one. Use when asked to clean up dead code, remove unused files, or reduce codebase size.
Measure the impact of refactoring using statico before/after analysis. Snapshots code health before changes and compares after. Use when planning or completing a refactoring, measuring code quality improvements, or verifying cleanup effectiveness.
Develop, test, and debug statico plugins. Use when creating plugins, modifying plugin code, or running the plugin development workflow (init, build, run, doctor).
Rust CLI static analyzer for TypeScript and Rust projects. Detects dead code, unused exports/types/dependencies, circular dependencies, code duplication, and framework-specific issues. Supports AI-optimized output formats, auto-fix suggestions, and Mermaid dependency graphs. Use when analyzing code health, measuring refactoring impact, setting up CI code-quality gates, or exploring unfamiliar codebases.
Cut a new statico release. Use when the user says "cut a release", "release vX.Y.Z", "ship X.Y.Z", "publish a release", or otherwise asks to produce a new versioned release of statico. Drives `scripts/release.sh` end-to-end (version bump → tests → commit → tag → optional push) with conservative error handling.
Run statico code analysis on the current project. Use when asked to check code health, find dead code, review code quality, or analyze dependencies.
Fix code quality issues found by statico. Use after running statico analyze to address dead code, unused exports, and other detected issues.