agentleFS
Piebald-AIPiebald-AI/splitrail/.claude/skills/new-analyzer/SKILL.md

new-analyzer

Skill228 starsChanged 5 months agoMITView on GitHub

Guide for adding a new AI coding agent analyzer to Splitrail. Use when implementing support for a new tool like Copilot, Cline, or similar.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 0 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Add variant to Application enum in src/types.rs

    line 12
  2. Very specific:

    Create src/analyzers/{agent_name}.rs implementing Analyzer trait from src/analyzer.rs

    line 13
  3. Very specific:

    Add tests in src/analyzers/tests/{agent_name}.rs, export in src/analyzers/tests/mod.rs

    line 16
  4. Very specific:

    Test fixtures go in src/analyzers/tests/source_data/.

    line 20
  5. Very specific:

    Use discover_vscode_extension_sources() and get_vscode_extension_tasks_dirs() helpers from src/analyzer.rs.

    line 24

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Adding a New Analyzer

Splitrail tracks token usage from AI coding agents. Each agent has its own "analyzer" that discovers and parses its data files.

Checklist

  1. Add variant to Application enum in src/types.rs
  2. Create src/analyzers/{agent_name}.rs implementing Analyzer trait from src/analyzer.rs
  3. Export in src/analyzers/mod.rs
  4. Register in src/main.rs
  5. Add tests in src/analyzers/tests/{agent_name}.rs, export in src/analyzers/tests/mod.rs
  6. Update README.md
  7. (Optional) Add model pricing to src/models.rs if agent doesn't provide cost data

Test fixtures go in src/analyzers/tests/source_data/. See src/types.rs for message and stats types.

VS Code Extensions

Use discover_vscode_extension_sources() and get_vscode_extension_tasks_dirs() helpers from src/analyzer.rs.

Reference Analyzers

  • Simple JSONL CLI: src/analyzers/pi_agent.rs, src/analyzers/piebald.rs
  • VS Code extension: src/analyzers/cline.rs, src/analyzers/roo_code.rs
  • Complex with dedup: src/analyzers/claude_code.rs
  • External data dirs: src/analyzers/opencode.rs

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.