Stop being lost in a codebase. CLI + Claude Code skill that builds an import graph, runs PageRank to find the files h...
Copy the install, test the workflow, then decide if it earns a permanent slot.
The signal is softer here. Treat it like a pattern source unless it solves a very specific gap.
Copy the install, test the workflow, then decide if it earns a permanent slot.
Not hard to test, not trivial to unwind. Worth trying if it closes a sharp gap.
GitHub health unknown. no security policy. 0 open issues make this testable, but not something to trust blind.
AI Agent
Claude Code
Model
Claude
Fastest way to find out if wtfismyrepo belongs in your setup.
Copy the install command, run a real test, and back it out cleanly if it slows you down.
# Visit: https://github.com/nandnijaiswal/wtfismyrepoRun this first. You will know quickly if the workflow earns a permanent slot.
# No automated removal — visit https://github.com/nandnijaiswal/wtfismyrepoNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
~/ └─ .claude/ ├─ commands/ ├─ agents/ │ └─ wtfismyrepo/ ← installs here └─ settings.json
Stop being lost in a codebase. CLI + Claude Code skill that builds an import graph, runs PageRank to find the files holding a repo together, scores fragility from git churn, and reads GitHub PRs/issues to show you exactly where to start.
Source: GitHub repository
Source check: No source check recorded
Repository state: Not marked archived
Honeystax upvotes are community interest signals, not star ratings. GitHub stars and repository health are source measurements; editorial risk and trial-cost notes are Honeystax analysis.