skills.rest
fallow-rs
fallow-rsOFFICIAL
Explore all skills by this author →
WebsiteGitHub

cli-output-review

Review CLI human-readable output for scanability, hierarchy, and terminal compatibility.

4.4k|154|Updated Mar 17, 2026
Search Tags:#CLI#Rust#ux#terminal output#no_color#Code review#scanability
One-click install
npx skills add https://github.com/fallow-rs/fallow --skill cli-output-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cli-output-review
Source: https://github.com/fallow-rs/fallow/tree/main/.agents/skills/cli-output-review
Command: npx skills add https://github.com/fallow-rs/fallow --skill cli-output-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Changes to a CLI's human-readable output can silently degrade readability, break terminal rendering, or produce confusing empty states. This Skill provides a structured review checklist so output changes in the fallow CLI are evaluated consistently before shipping.

Core Features & Use Cases

  • Output Quality Review: Evaluates information hierarchy, scanability, and progressive disclosure in CLI output.
  • Terminal Compatibility Checks: Verifies NO_COLOR support and terminal compatibility for formatted text.
  • Empty State Validation: Ensures commands produce sensible output when there is nothing to report.
  • Use Case: After modifying a reporter in crates/cli/, run this review to confirm the new output remains scannable, respects NO_COLOR, and ends with a clear APPROVE, CONCERN, or BLOCK verdict.

Quick Start

Review the CLI output changes in crates/cli for scanability, empty states, and NO_COLOR terminal compatibility.

Frequently Asked Questions about cli-output-review

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

FAQPage Schema
How do I review CLI output changes for readability?▼

Read the reviewer guidance in .agents/agents/cli-output-reviewer.md and the rules in .agents/rules/cli-crate.md, then inspect the concrete output path under crates/cli. Evaluate information hierarchy, scanability, and progressive disclosure before issuing a verdict.

What should a CLI output review check for terminal compatibility?▼

Verify NO_COLOR support so output renders correctly when colors are disabled, and confirm formatting works across terminals. The review also covers empty states and progressive disclosure of detail.

When should I run a CLI output review?▼

Run it whenever changes affect human-readable output, command UX, or text formatting in the CLI, including modifications to reporters, snapshots, or related tests under crates/cli.

What verdict does the CLI output review produce?▼

The review ends with one of three explicit verdicts: APPROVE, CONCERN, or BLOCK. This gives a clear, actionable signal on whether the output change is acceptable to ship.

Does the review cover empty command output states?▼

Yes, empty states are an explicit focus area. The review checks that commands produce sensible, well-formatted output even when there is nothing to report.

Related Skills

Explore More Software Engineering Skills→
fractaryfractary

cache-metrics

Analyze codex cache metrics and return JSON or formatted output.

Official
Advanced
p-o-ke-naep-o-ke-nae

github-flow

Guide GitHub Flow branching, commits, testing, pull requests, and squash merges.

Community
Intermediate
Open-PawsOpen-Paws
3

code-review

Automate layered code review for pull requests in CI pipelines.

Official
Advanced
refined-prunrefined-prun
35

review-pr

Review GitHub pull requests against project guidelines and produce a structured review artifact.

Official
Advanced