skills.rest
laionazeredo
laionazeredoCOMMUNITY
Explore all skills by this author →
GitHub

che-decisions-query

Queries, filters, and exports decision history from a worktree's decisions.log.jsonl file.

Updated May 12, 2026
Search Tags:#cli#audit#query#decision log#filter#export#jsonl
One-click install
npx skills add https://github.com/laionazeredo/che-ai --skill che-decisions-query-laionazeredo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: che-decisions-query
Source: https://github.com/laionazeredo/che-ai/tree/main/skills/che-decisions-query
Command: npx skills add https://github.com/laionazeredo/che-ai --skill che-decisions-query-laionazeredo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams using the Che harness accumulate decision events in a JSONL log file, but manually reading raw JSONL lines is slow and error-prone. This Skill provides a structured, read-only query layer over decisions.log.jsonl so users can inspect, filter, summarize, and export decision history without parsing JSON by hand. ## Core Features & Use Cases - Summary Mode: Groups decision events by type, newest first, in a human-readable English bullet list (default when the user asks to "show decisions"). - Filter Mode: Narrows entries by spec_id, event type, date range, or keyword grep across data fields. - Export & Tail Modes: Exports results to CSV/TSV via a centralized output path helper, or returns the last N entries. - Use Case: A user asks "what happened to SPEC-API-HEALTH-1?" and the Skill runs filter mode with --spec SPEC-API-HEALTH-1 against the canonical decisions file resolved via the che CLI. ## Quick Start Ask the assistant to show the decision history for the current worktree, optionally filtered by a spec ID, event type, or date range.

Frequently Asked Questions about che-decisions-query

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

FAQPage Schema
How do I query decision history from a JSONL log file?▼

Run the decisions query in summary mode against the decisions.log.jsonl path resolved from $CHE_DECISIONS_PATH. It groups entries by event type, newest first, and renders a human-readable English bullet list instead of raw JSONL.

How to filter decision log entries by spec ID or event type?▼

Use filter mode with --spec SPEC-XXX for a specific spec_id, --event for case-insensitive event matching, --after/--before for date ranges, or --grep for keyword search across data fields. Arguments can be combined.

Can I export decision history to CSV or a spreadsheet?▼

Yes, export mode supports --format csv or tsv with columns ts, event, spec_id, session_id, and data_json_str. The output path is built via the che output_path helper, never written into the worktree.

Why does the decisions query say no decisions are registered?▼

This happens when decisions.log.jsonl does not exist for the worktree, meaning no decision events have been appended yet. The Skill is read-only; new entries must be written with che decision_append first.

What are the limitations of the decisions query skill?▼

It is strictly read-only and cannot write new decision entries. It also requires the che CLI on PATH, a known absolute worktree path, and the canonical session contracts; without these preconditions it aborts rather than guessing.

Related Skills

Explore More Software Engineering Skills→
ryan-nguyen-01ryan-nguyen-01
4

skill-arch-audit-log

Capture immutable audit events with structured schemas and retention policies.

Community
Advanced
DaniloUnicamDaniloUnicam

csv-workbench

Analyze CSV files to generate numeric summaries like totals and counts.

Community
Basic
Analog-LabsAnalog-Labs

freeze

Restrict file edits to a designated directory during a session.

Official
Intermediate
czueczue

session-logs

Search and analyze session JSONL files with jq.

Community
Intermediate