agentleFS
searlscosearlsco/prove_it/.claude/skills/session-log/SKILL.md

session-log

Skill198 starsChanged 8 months agoMITView on GitHub

Inspect prove_it session logs—review history, reviewer verdicts, and session state. Use when asked about session logs, reviewer results, or "what did the last hook say".

19 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ml-training-recipe, replication and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • getcompanion-aiSkill

    ml-training-recipe

    Find implementable ML training recipes from papers, datasets, docs, and code. Use when the user wants to fine-tune, train, reproduce, or choose a practical ML method, dataset, hyperparameter setup, or benchmark recipe.

    Also in 3 projects that use this

  • getcompanion-aiSkill

    replication

    Plan a replication of a paper, claim, or benchmark, and execute only after an explicit environment choice. Use when the user asks to replicate results, reproduce an experiment, verify a claim empirically, or build a replication package.

    Also in 3 projects that use this

  • brainbytes-devSkill

    alpha-research

    Also in 3 projects that use this

  • JaimeParkerSkill

    paper-code-audit

    Perform three-way cross-validation of a research paper by comparing the original paper text (via Zotero), official code implementation (via Git), and personal Obsidian notes. Use this skill whenever the user wants to "audit a paper", "verify paper claims against code", "cross-check notes with implementation", "triangulate paper + code + notes", "find discrepancies between paper and code", or mentions wanting a deep, structured comparison of a paper's claims against its implementation and their own notes. Also trigger when the user asks to "analyze this paper thoroughly" with code available, or when they want to systematically reconcile what the paper says, what the code does, and what their notes claim.

    Also in 3 projects that use this

  • JimLiuSkill

    pdf-explore

    Use this skill when the user has attached a PDF, paper, report, or other document and the answer needs content from more than one place in it: summarize the methods or any other section, compare sections, find where a topic is discussed, read a value or label off a figure or chart, or find/list/extract every instance of something across the whole document (datasets, benchmarks, citations, figures, table rows, accession numbers — including appendices). Skip it only for a single lookup of 1–4 pages quoted in your very next response — `read_file(pages=[...])` attaches pages as images that are dropped from context after one turn, so multi-section answers end up re-reading the same ranges repeatedly. Parses the PDF once in the Python kernel: `pdf_pages` (pages as persistent text), `pdf_outline` (TOC), `pdf_scan` (rank pages by relevance), `pdf_map`/`pdf_extract` (per-page summary / structured fields via parallel haiku calls). For PDF creation/manipulation, use reportlab/pypdf directly.

    Also in 3 projects that use this

  • KISHOR403Skill

    session-search

    This skill should be used when searching Claude Code session transcripts with semantic understanding. Triggers on queries like "find sessions about X", "when did I work on Y", "search previous conversations". Supports natural language queries with synonym matching.

    Also in 4 projects that use this

  • +1 more from getcompanion-ai

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 14 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read it and display each entry as a table or formatted list showing:

    line 27
  2. Very specific:

    Read <session_id>.jsonl and <session_id>.json and display both the session state and reviewer entries.

    line 35
  3. Distinctive:

    Use the reviewer name as-is (e.g., "coverage-review", "fast-tests")

    line 49

“Common” is measured: kept by at least 6 in 10 of the 14 edited versions of this file we could read. “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

Inspect prove_it session logs

Session data lives in ~/.claude/prove_it/sessions/. Two file types per session:

  • <session_id>.json—session state (project dir, git HEAD, started_at)
  • <session_id>.jsonl—reviewer log (one JSON object per line: at, reviewer, status, reason, projectDir, sessionId)
  • _project_<hash>.jsonl—project-level reviewer log (when session_id was null)

Determine the current session ID

The current Claude Code session ID is passed in hook input. To find it for the active conversation, check the most recently modified .jsonl file:

ls -t ~/.claude/prove_it/sessions/*.jsonl | head -5

What to show

Default (no args): show the current session's reviewer log

  1. Find the most recently modified .jsonl file (excluding _project_* and test-session* files).
  2. Read it and display each entry as a table or formatted list showing:
    • Time (human-readable from the at timestamp)
    • Reviewer name
    • Status (PASS/FAIL/SKIP/BOOM)
    • Reason (the reviewer's rationale)

With a session ID arg: show that specific session

Read <session_id>.jsonl and <session_id>.json and display both the session state and reviewer entries.

With --all or all: list all sessions

List all session .json files sorted by modification time, showing session ID, project, and started_at.

With --stats or stats: aggregate reviewer stats

Count PASS/FAIL/SKIP/BOOM across all .jsonl files and show totals.

Formatting

  • Show timestamps as relative times (e.g., "2 min ago") or HH:MM:SS
  • Truncate long reasons to ~120 chars in table view, show full text if only one session
  • Use the reviewer name as-is (e.g., "coverage-review", "fast-tests")

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.