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

json-output-review

Review JSON output changes for schema stability, determinism, and downstream usability.

4.4k|154|Updated Mar 17, 2026
Search Tags:#API contracts#snapshots#determinism#Json#Code review#schema stability
One-click install
npx skills add https://github.com/fallow-rs/fallow --skill json-output-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: json-output-review
Source: https://github.com/fallow-rs/fallow/tree/main/.agents/skills/json-output-review
Command: npx skills add https://github.com/fallow-rs/fallow --skill json-output-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Changes to machine-readable JSON output can silently break downstream consumers, snapshots, and integrations. This Skill provides a structured review checklist to catch schema drift, unstable ordering, and inconsistent field behavior before changes ship.

Core Features & Use Cases

  • Schema Stability Review: Evaluates compatibility and drift risk when result fields or output contracts change.
  • Determinism Checks: Verifies stable ordering, null/empty behavior, and field naming consistency across outputs.
  • Downstream Usability: Assesses whether output remains friendly to automation, snapshots, and integration contracts.
  • Use Case: When a pull request modifies CLI JSON output fields or snapshot files, use this Skill to review the diff and end with a clear APPROVE, CONCERN, or BLOCK verdict.

Quick Start

Review the JSON output changes in this pull request for schema stability, ordering, and downstream compatibility.

Frequently Asked Questions about json-output-review

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

FAQPage Schema
How do I review JSON output changes for breaking changes?▼

Review JSON output changes by checking field additions, removals, and renames against existing consumers, then verifying ordering stability and null/empty behavior. This Skill guides that review and ends with an APPROVE, CONCERN, or BLOCK verdict.

What should I check when CLI JSON output schema changes?▼

Check compatibility and drift risk, stable ordering of arrays and objects, null versus empty value handling, and field naming consistency. Also inspect related snapshots, schema files, and output documentation for mismatches.

Why does deterministic JSON output ordering matter?▼

Unstable ordering breaks snapshot tests, diffs, and downstream automation that compare serialized output byte-for-byte. Deterministic ordering ensures integrations and CI checks produce reproducible results across runs.

When should a JSON output change be blocked in review?▼

Block a change when it breaks existing integration contracts, removes or renames fields without migration, or introduces nondeterministic output. Use CONCERN for risky but recoverable issues and APPROVE when compatibility is preserved.

Related Skills

Explore More Software Engineering Skills→
snowplowsnowplow
123

schema-review

Analyze JSON Schema files in iglu-central for quality and compatibility issues.

Official
Advanced
meta-pytorchmeta-pytorch
3

process-cherry-picks

Extract cherry-pick entries from tracker issues into release notes worksheets and cherrypicks.md.

Official
Advanced
cenjiecenjie

api-contract-testing

Validate API contracts between consumers and providers in CI.

Community
Intermediate
constellizeconstellize
1

write-contract-tests

Generate strict contract tests from constellation-map.md and code-generation-plan files.

Official
Advanced