debt

Detect TypeScript and JavaScript antipatterns via fallow static analysis and append findings to a debt ledger.

1|1|Updated Jun 21, 2026
One-click install
npx skills add https://github.com/Navdeepgambhir9023/nav --skill debt-navdeepgambhir9023
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debt
Source: https://github.com/Navdeepgambhir9023/nav/tree/main/skills/debt
Command: npx skills add https://github.com/Navdeepgambhir9023/nav --skill debt-navdeepgambhir9023

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires fallow.

What problem does it solve? Technical debt that depends on someone remembering to flag it always gets undercounted. This Skill automatically detects real antipatterns in a codebase — dead code, duplication, complexity hotspots, circular dependencies, and boundary violations — and records them in a persistent ledger so debt is visible and tracked instead of forgotten. ## Core Features & Use Cases - Automated Static Analysis: Runs fallow via npx against TypeScript/JavaScript code, either scoped to a goal's changed files or across the whole repository. - Idempotent Debt Ledger: Appends deduplicated findings (keyed by SHA-1 fingerprint) as JSON lines to .loop/memory/debt.nav and updates the memory index, so re-runs never double-count. - Read-Only Safety: Never modifies source files, never auto-fixes, and honestly reports unsupported languages (Python, Go, Rust) instead of fabricating findings. - Use Case: After closing a development goal, run the debt scan to catch newly introduced dead exports or duplicated logic and log them as tracked entries the owner can later resolve through a dedicated goal. ## Quick Start Ask the assistant to run a debt scan on this repository and report any antipatterns it finds.

Frequently Asked Questions about debt

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect dead code and duplication in a TypeScript project?

Run the debt scan, which invokes `npx fallow` to detect unused files, unused exports, clone groups, circular dependencies, and boundary violations. Findings are parsed from fallow's JSON output and appended to a debt ledger with deduplication.

What static analysis tool does this debt detection use?

It uses fallow (https://github.com/fallow-rs/fallow), invoked via npx. Standalone runs use `npx fallow --format json` for a full-repo view, while goal-scoped runs use `npx fallow audit --gate all --format json --base <sha>`.

Does this debt scanner support Python, Go, or Rust codebases?

No. Only TypeScript and JavaScript are supported via fallow. Repositories containing other languages have those languages reported as 'not yet supported' in the output rather than being analyzed with approximations.

Will the debt scan modify or auto-fix my source code?

No. The scan is strictly read-only. Although fallow offers a `fix` command, this Skill never invokes it. Resolving any finding requires a separate, explicit decision by the owner, typically through a new goal.

Why does a re-run of the debt scan not duplicate findings?

Each finding gets a SHA-1 fingerprint computed from its source array key, file path, and serialized content. Before appending, the scan reads existing debt.nav entries and drops any finding whose fingerprint is already tracked.

What happens if fallow is not installed or npx cannot fetch it?

The scan reports the failure explicitly and stops. It does not proceed with partial results or fabricate findings when the analyzer cannot run, such as in offline environments or blocked registries.