logseq-review-workflow-eval

Compare two revisions of a review skill by running identical prompts against isolated snapshots.

44.7k|2.8k|Updated May 23, 2020
One-click install
npx skills add https://github.com/logseq/logseq --skill logseq-review-workflow-eval
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: logseq-review-workflow-eval
Source: https://github.com/logseq/logseq/tree/main/.agents/skills/logseq-review-workflow-eval
Command: npx skills add https://github.com/logseq/logseq --skill logseq-review-workflow-eval

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

When you modify the logseq-review-workflow skill, it is hard to know whether the change actually improved review quality or introduced regressions. This Skill runs the same review prompt against isolated before and after snapshots of the skill, collects both outputs, and produces a structured comparison so you can judge the delta objectively.

Core Features & Use Cases

  • Isolated Snapshot Setup: Extracts the old skill revision from a git ref and the new revision from a git ref or the working tree into separate snapshot directories, preventing cross-contamination between runs.
  • Deterministic Output Comparison: Parses findings (severity, category, location, issue, impact, suggestion) from both raw outputs and reports shared, lost, and added findings plus severity and category counts.
  • Qualitative Evaluation Rubric: Provides scoring criteria for finding quality, coverage, validation rigor, subagent orchestration, and final answer usability, with Improved/Regressed/Mixed/Inconclusive decision labels.
  • Use Case: After editing routing rules in logseq-review-workflow, run this Skill with the previous commit as the before ref and the working tree as the after revision to verify the new revision keeps true findings and does not fabricate validation claims.

Quick Start

Use the logseq-review-workflow-eval skill to compare the before and after behavior of logseq-review-workflow on the same review prompt.

Frequently Asked Questions about logseq-review-workflow-eval

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I evaluate whether changes to a review skill improved its output?

Run the same review prompt against isolated before and after snapshots of the skill in fresh agent sessions, save both raw outputs, then compare them with the compare_outputs.py script. Finish with the evaluation rubric to reach an improved, regressed, mixed, or inconclusive conclusion.

How do I set up before and after snapshots from git refs?

Run setup_eval.py with --before-ref pointing to the old revision and a prompt file. The after revision defaults to the current working tree; pass --after-ref only when comparing two committed revisions. The script extracts snapshots via git archive and generates run prompts.

Why must the before and after review runs be isolated?

Isolation prevents the intended outcome from leaking into the review runs, which would bias results. Neither run may read the other snapshot, the other output, or comparison notes, and both must use the same prompt, model, and tool availability.

What does the comparison report include?

The report includes word counts, text similarity, parsed finding counts, severity and category distributions, findings unique to each run, and verification section excerpts. It ends with manual judgment notes pointing to the evaluation rubric for the final qualitative conclusion.

When is more findings not better in a review evaluation?

More findings only count as improvement when they are concrete, correctly scoped, and validated. Added speculative noise, unverifiable claims, or stricter checks that were never actually run are treated as regressions or false positives under the rubric.