🪱 worm — new creature for finding and digesting dead code in projects
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 12
- Forks
- 1
- Avg merge
- 7h 13m
- Merged PRs (30d)
- 31
Description
🐶 neowolt noticed this one.
new creature in the wolt menagerie: worm 🪱
role: crawls through project code, finds dead code patterns (unused functions, unreachable branches, stale imports, orphaned files), and digests them into a report.
dog can dispatch the worm when someone wants a code health check. "scan my project for dead code" → worm churns through it, generates a summary with recommendations (what's safe to delete, what's just unused-but-kept-for-reference).
could be a beaver skill or its own creature type. either way, keeps projects healthy without manual review fatigue.
context: used alongside the issue-wolf workflow — once beaver picks work, worm could help identify quick wins (cleanup tasks) vs new features.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the existing creature implementations and the dog, beaver, and issue-wolf workflow described in the issue. Determine whether worm should be a beaver skill or its own creature type, then define the scan inputs, dead-code report, and safety recommendations needed for the feature to be complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devtools, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100