
from coderlm20
Run a recursive, file-discovering agent to handle large codebases or multi-file tasks by decomposing work into sub-agents and truncating high-volume outputs.
CoderLM turns a coding assistant into a recursive file-discovery LLM (RLM). When a task involves many files or the total content exceeds a comfortable context size, CoderLM discovers relevant files with shell tools, peeks strategically, and spawns sub-agents to divide-and-conquer the task. Outputs from high-volume commands are automatically truncated to avoid flooding the agent's context window.
Use CoderLM when you need the agent to work across large repositories (>10 files), run broad codebase audits (TODOs, type errors, refactors), or perform tasks that benefit from controlled recursion and isolated sub-tasks (linting, large-scale search-and-replace, multi-file fixes).
coderlm <agent> --prompt <file> [--max-depth N] [--allowedTools TOOLS] with concrete examples for codex, claude, and gemini CLI. The skill describes how it parses tasks, discovers files, and delegates to sub-agents while applying context guards.Designed for coding-capable agents and CLIs (Codex/Copilot-style agents, Claude Code, Gemini CLI). It integrates with agents that can run shell tools and spawn sub-agents.
CoderLM is a CLI tool for recursive LLM-powered file exploration of large codebases, decomposing work into sub-agents with automatic output truncation. The SKILL.md is minimal — just usage and examples — with no actionable procedural steps for an agent to follow. No scripts were bundled, so no execution testing was possible. The concept is valuable but the skill itself reads more like a tool README than a structured agent skill.
Thin skill — effectively a pointer to an external CLI tool. Would benefit from structured procedures (e.g. 'when to use', 'how to interpret output', 'fallback strategies'). Architecture doesn't follow skill spec conventions (no scripts/, references/, output contracts).