agentsclimarketplace

Research codebase

Skill NilsWidal/loobster/.agents/skills/research-codebase

Document the existing codebase exactly as it is today (no suggestions, no fixes). Use as the first phase, before proposing changes.From its SKILL.md

Install
npx -y skills add NilsWidal/loobster --skill research-codebase

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.

SKILL.md

1.9 KB, as published. Nobody here has run it

<!-- GENERATED from commands/research-codebase.md by bin/build-codex-skills.py — do not edit here. -->

Research and document the existing codebase exactly as it is today; no suggestions or evaluations.

Behavior contract

  • Only document what exists today; do not suggest improvements, RCA, or future work.
  • Provide concrete file paths and line references in findings.
  • Read any user-mentioned files fully before decomposing work.

Steps after receiving the research query

  1. Read directly mentioned files fully.
  2. Decompose the query into focused research areas and create an internal checklist.
  3. Explore relevant directories and files in parallel when areas are independent. If necessary, inspect git history for additional context.
    • Token discipline (see .agents/skills/token-discipline/SKILL.md): for broad or deep exploration, delegate the heavy reading to Explore/Agent subagents — one per independent area — and bring back only their findings. The main thread should accumulate conclusions and code references, not raw file contents, so later phases inherit a lean context window. Apply the research model preference from .claude/loobster.json to these readers (see run.md "Preferred subagents"); no config → inherit the session model.
  4. Synthesize after all exploration completes; prioritize live code findings over historical docs.
  5. Produce a structured research document.
    • If Linear MCP tools are available, save it as a Linear document.
    • Also save a copy to the local research/ directory for reference during later phases.

Output format

  • High-level summary (3-6 sentences)
  • Detailed findings grouped by component/area
  • Code references in the form path/to/file.py:123-145

Keep looking

Skills are one crate of 614,194. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.