qwen-web-arwaky: Skill for Claude Code

repowise-scan — Self-Hosted Codebase Intelligence via CLI

Use the local repowise CLI (not the hosted MCP endpoint) so repository exclusions (.repowiseIgnore, .repowise/config.yaml exclude_patterns, .gitignore) apply and findings reflect production code only. The hosted endpoint at api.repowise.dev does not reindex on the free plan (no auto-sync) and can still report fixture files.

Preflight

Verify the CLI is installed and indexed:

repowise doctor        # all checks OK
repowise status        # last sync commit, index storage

If not indexed yet, run a fast structural index (no LLM, no cost):

repowise init --no-prose -y --mode fast

1. Dead code

# Table (default)
repowise dead-code

# JSON (best for agents — parse with python)
repowise dead-code --format json 2>/dev/null | python3 -c "import sys,json; d=json.load(sys.stdin); print(d)"

# High-confidence, safe-to-delete only
repowise dead-code --safe-only

# Filter by kind
repowise dead-code --kind unreachable_file
repowise dead-code --kind unused_export
repowise dead-code --kind unused_internal
repowise dead-code --kind zombie_package

Interpretation:

• unreachable_file at confidence ≤ 0.40 for crates/root_*_main_entry.rs → false positive — these are Rust binary entry points (fn main(), declared in Cargo.toml [[bin]]). Repowise does not mark Cargo [[bin]] as is_entry_point, so they read as unreachable (known issue: repowise-dev/repowise#666 for the Python analogue; Rust binaries have the same gap). Never delete them.
• zombie_package on a workspace root like crates/ → false positive (it is the workspace itself).
• Fixture paths (workspaces-bad/, workspaces-good/) should never appear — if they do, the exclude is not applied (see §6).

2. Code health

repowise health                        # repo-level KPIs + worst files
repowise health --format json 2>/dev/null | python3 -m json.tool
repowise health --include-internals    # include private-symbol findings