agentleFS
D-SheyD-Shey/autoharness/.agents/skills/history-search/SKILL.md

history-search

Skill10 starsChanged yesterdayMITView on GitHub

Search and retrieval across task history, runs, and reviews

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use when querying previous execution details in long-running tasks without loading massive logs into active context:

    line 9
  2. Very specific:

    Call harness_history_search(query, kind) where kind is runs, reviews, or all.

    line 16
  3. Distinctive:

    If a specific test error needs full inspection, fetch only that run's snippet rather than the entire 500-line pytest dump.

    line 20
  4. Very specific:

    Run harness_history_search with an assertion query and verify matched log snippets are returned.

    line 25
  5. Very specific:

    Verify filtering by kind (runs vs reviews) returns only relevant records.

    line 26

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

history-search

When to use

Use when querying previous execution details in long-running tasks without loading massive logs into active context:

  • Searching past test logs (runs/*.log) for specific assertion failures or stack traces.
  • Querying earlier critic reviews and arbitrator decisions.
  • Retrieving previous tool call outputs on demand.

Steps

  1. Targeted query dispatch:
    • Call harness_history_search(query, kind) where kind is runs, reviews, or all.
    • The search engine inspects task log files on disk and returns only matching lines with file coordinates and line numbers.
    • Reference: Reversible context retrieval (https://github.com/ranxianglei/billion-context).
  2. Context decompression:
    • If a specific test error needs full inspection, fetch only that run's snippet rather than the entire 500-line pytest dump.
  3. Bounded token return:
    • Limit search results to the top matching snippets with context windows (e.g., 3 lines before/after).

How to verify

  1. Run harness_history_search with an assertion query and verify matched log snippets are returned.
  2. Verify filtering by kind (runs vs reviews) returns only relevant records.

Facts found here

  • runs/ directory in task state holds output of every autoharness verify run.
  • answers/ directory holds exact responses of critic and quality reviewers.

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.