One-click install
npx skills add https://github.com/selfagency/agentsy --skill fallow-selfagency
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fallow
Source: https://github.com/selfagency/agentsy/tree/main/.agents/skills/fallow
Command: npx skills add https://github.com/selfagency/agentsy --skill fallow-selfagency

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you clean and stabilize JavaScript/TypeScript codebases by identifying dead code, unused exports/types/dependencies, duplication, circular dependencies, boundary violations, and stale feature-flag suppressions, then (optionally) merging runtime coverage evidence into the same health view.

Core Features & Use Cases

  • Static dead-code intelligence: Detect unreachable files, unused exports, unused types, unused enum/class members, unresolved imports, and unused/unlisted dependencies.
  • Structure and quality checks: Surface circular dependencies, architecture boundary violations, complexity/health hotspots, and duplication patterns.
  • Runtime confidence for safe cleanup: Merge production execution/coverage data into fallow health reports to prioritize hot-path safety and cold-path deletion confidence.
  • Guided maintenance workflows: Support baselines/regressions for incremental adoption and a safe auto-fix workflow (dry-run first, then apply).

Quick Start

Run dead-code analysis with machine-readable JSON by executing: fallow dead-code --format json --quiet --changed-since main.

Frequently Asked Questions about fallow

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

FAQPage Schema
How do I detect unused code and dead exports in a JavaScript or TypeScript project?

You can detect unused code by scanning JavaScript and TypeScript projects for unreachable files, unused exports, types, and dependencies. This static analysis identifies dead code and structural issues to guide safe cleanup decisions.

What is the best way to find circular dependencies and architecture boundary violations?

Finding circular dependencies and architecture boundary violations involves analyzing your project's import structure to surface quality hotspots. This structural code-health check detects boundary breaches and duplication patterns to stabilize your codebase.

Can I use runtime coverage data to safely remove dead code?

Yes, you can merge runtime coverage data into your code health reports to safely remove dead code. Combining production execution evidence with static analysis prioritizes hot-path safety and increases cold-path deletion confidence.

Does dead code detection support incremental CI scoping for pull requests?

Dead code detection supports incremental CI scoping by limiting analysis to changed files since a base branch. This PR-scoped approach outputs machine-readable JSON to enforce quality gates without evaluating the entire workspace.

How do I auto-fix unused dependencies without breaking my project?

To auto-fix unused dependencies safely, execute commands in a dry-run mode before applying changes. This guided maintenance workflow ensures safe command execution patterns, allowing you to verify removals before committing fixes.