ci-formats-review

Reviews SARIF, CodeClimate, and other CI output formats for correctness and integrator compatibility.

4.4k|154|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/fallow-rs/fallow --skill ci-formats-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci-formats-review
Source: https://github.com/fallow-rs/fallow/tree/main/.agents/skills/ci-formats-review
Command: npx skills add https://github.com/fallow-rs/fallow --skill ci-formats-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Changes to machine-consumed report formats can silently break CI integrations, dashboards, and downstream tooling. This Skill provides a structured review checklist for CI-facing output formats so format regressions are caught before merge.

Core Features & Use Cases

  • Format Correctness Review: Validates SARIF, CodeClimate, compact, markdown, and badge output formats against their specifications.
  • Integrator Compatibility Checks: Ensures output remains consumable by CI platforms and external tools that parse the reports.
  • Edge-Case Coverage: Focuses on empty-input handling, stable snapshots, and deterministic ordering.
  • Use Case: After modifying the SARIF reporter in a static analysis tool, run this review to confirm the output still validates against the SARIF schema and renders correctly in GitHub code scanning.

Quick Start

Review my changes to the SARIF and CodeClimate output formatters for correctness and CI consumer compatibility.

Frequently Asked Questions about ci-formats-review

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

FAQPage Schema
How do I review SARIF output changes before merging?

Check that the SARIF output conforms to the schema, remains compatible with CI consumers like GitHub code scanning, and handles empty result sets correctly. Verify snapshot stability and deterministic ordering, then conclude with an APPROVE, CONCERN, or BLOCK verdict.

What should I check when modifying CodeClimate report format?

Verify the CodeClimate JSON structure matches the specification expected by consumers, test empty-input behavior, and confirm snapshot tests remain stable. Changes affecting field names or severity mappings can break downstream CI integrations.

Why does CI report output break integrations after format changes?

CI consumers parse reports against fixed schemas, so renamed fields, reordered keys, or changed severity values cause parsing failures. Reviewing format correctness and integrator expectations before merge prevents these regressions.

Does this review cover empty analysis results?

Yes, empty-input handling is an explicit focus area. The review checks that SARIF, CodeClimate, markdown, and badge outputs produce valid, consumable output even when the analysis finds zero issues.

When should snapshot tests be updated during format review?

Update snapshots only when the format change is intentional and verified correct. The review requires stable snapshots and deterministic ordering, so unexpected snapshot diffs signal a regression that should block the change.