Spec Consistency Guard

automationDev tools

Spec Consistency Guard is an automation that checks spec files for consistency problems before code merges. When a spec is the source of truth, small edits can quietly violate invariants, such as a rubric weight that no longer sums, a version marker left un-bumped, or a frontmatter field dropped. A push or pull request guard runs the whole battery of consistency assertions so a broken spec never merges.

Unavailable. Delivery for this kind is on the roadmap — not serving yet.

Add to setup to save this item as a reference. Ahel cannot run it, and signing in will not install it.

What your AI can do with it

  • Runs consistency assertions on spec files during push or pull request
  • Detects rubric weights that no longer sum correctly
  • Flags version markers that were not bumped
  • Catches frontmatter fields that were dropped
  • Prevents merging when a spec consistency check fails

Getting started

  1. Save this item in Your setup as a reference.
  2. Read the source or reference documentation for its setup requirements. Saving it here does not connect it to your AI.
  3. Check this page for availability before trying to install it through Ahel.

Signals

GitHub stars
50k
Forks
4k
Last commit
Sep 2026

Questions

What kinds of consistency problems does it check for?
It checks for unsatisfied rubric sums, missing version bumps, dropped frontmatter fields, and other invariants defined in your spec files.
When does the guard run?
It runs on push or pull request, before code merges.
Can it fix the problems it finds?
No, it only runs consistency assertions and reports failures. Fixing the spec is up to you.
Does it work with any spec format?
It works with spec files that contain invariants like rubric sums, version markers, or frontmatter fields. Other formats are not supported.
Advanced
Item type
automation
Key
spec-consistency-guard
Source
github.com/imbad0202/academic-research-skills