Now available SpecGuard — PR gating for specifications

Code review is broken.
SpecGuard fixes the first step.

Before any code can merge, it needs a spec.
SpecGuard is a GitHub Action that checks every pull request for an associated specification before merge. No spec, no merge. Simple, enforceable, automatic.

View on GitHub → See how it works
$ gh extension install jinter-ai/specguard
specguard · PR #2847 · acme/payments
→ Checking PR #2847 for specification...
→ Scanning linked tickets, description, docs folder...
linked: JIRA-441 — payments-v2 rate limiter found
spec: docs/specs/rate-limiter-v2.md found
match: diff scope vs spec scope pass
✓ Specification check passed — PR may proceed to review
specguard · PR #2851 · acme/payments
→ Checking PR #2851 for specification...
→ Scanning linked tickets, description, docs folder...
linked: no ticket linked
spec: no specification document found
✗ No specification found — merge blocked
→ Add a spec to docs/specs/ or link a ticket with a spec reference.
90%
of AI PRs have no
associated specification
5 min
GitHub Action
setup time
0
unspecified PRs
after SpecGuard
The problem

AI agents open PRs.
Nobody knows what they were supposed to do.

When a human writes code, intent lives in their head. When an AI agent writes code, intent lives nowhere — unless you capture it before merge. SpecGuard captures it.

No spec, no accountability
When an AI agent opens a PR with 800 changed lines and no description, reviewers are flying blind. When it breaks in production, nobody owns the decision. A specification is the minimum unit of accountability.
Review without context is noise
Code review catches typos. It rarely catches architectural mistakes — because the reviewer doesn't know what the code was supposed to do. A spec gives reviewers the context to make the right call.
Teams ask for specs. Nobody enforces them.
Every team has a "please add a description" rule. Almost no team enforces it at the gate. SpecGuard makes spec presence a hard requirement, not a soft guideline.
AI coding is accelerating the problem
AI agents like Cursor and Copilot generate code at a pace no team can manually verify. Without SpecGuard, that pace means more unverified decisions compounding daily.
SpecGuard

PR gating for specs.
Built on CoreSpec.

A GitHub Action that blocks merge until a specification exists. Works with your existing workflow — Jira, GitHub Issues, docs folders, ADRs. No new process required.

1
PR opened
Developer or AI agent opens a pull request. SpecGuard triggers automatically via GitHub Actions webhook.
2
Spec detection
SpecGuard uses CoreSpec's detection engine to find associated specifications — linked tickets, PR description, docs folder references, ADR files.
3
Gate decision
If a specification is found and matches the PR scope: pass. If not: blocked with a clear reason and remediation path.
4
PR comment with guidance
SpecGuard posts a structured comment explaining what's missing and how to fix it. Engineers aren't blocked — they're guided.
specguard check
PR #2851
Spec missing — merge blocked
No specification found for this pull request. The diff modifies 3 service boundaries and introduces a schema change on payments.amount — decisions that require documented intent before review.
no-spec schema-change 847 lines
→ Add docs/specs/payments-schema-v2.md or link a Jira ticket with spec reference.
specguard check
PR #2847
Spec verified — proceed to review
Specification found: docs/specs/rate-limiter-v2.md linked to JIRA-441. Diff scope matches spec scope. Proceed to code review with full context.
spec-found scope-match JIRA-441
→ Proceed to review. Specification available in PR comment.
CoreSpec

The foundation
everything builds on.

CoreSpec is the shared library that powers SpecGuard and every future Jinter product. Spec framework detection, LLM integration, GitHub API helpers, and common utilities — open source on GitHub.

Spec detection
Detects specification frameworks across formats — Markdown docs, ADRs, Jira tickets, GitHub Issues, RFC files, and custom patterns.
corespec.detect(pr)
LLM integration
Pluggable LLM interface for spec extraction, intent inference, and semantic matching. Works with OpenAI, Anthropic, or local models.
corespec.infer(diff)
GitHub API helpers
Pre-built utilities for PR metadata, comment posting, status checks, and webhook handling. Drop-in for any GitHub Action.
corespec.github.*
Quick start — add to your .github/workflows/
name: SpecGuard
on: pull_request
jobs:
  spec-check:
    runs-on: ubuntu-latest
    steps:
      - uses: jinter-ai/specguard@v1
        with:
          github-token: ${{ secrets.GITHUB_TOKEN }}
          block-merge: true
About Jinter

Built for a world where
machines write the code.

Every major shift in software development has produced a new accountability layer. Version control made collaboration possible. Code review made quality visible. CI/CD made delivery safe.

AI agents are producing code at a pace no team can manually verify. The next accountability layer needs to be built for that reality — not retrofitted from the last one.

Jinter is building that layer. Starting with specification. Extending to evidence, triage, and expert judgment. The goal: every line of AI-generated code that ships is verifiable, attributable, and accountable.

The problem we are solving
AI agents don't have judgment. They generate code. Jinter's mission is to build the infrastructure that makes AI-generated code as trustworthy as code written by your best engineer.
Beyond software
The judgment layer applies wherever AI agents are making consequential decisions. Software development is where we start — because the problem is acute, the feedback loop is fast, and the stakes are real.
Where we start
SpecGuard is step one — ensuring every PR has a specification before merge. Simple, enforceable, and the foundation everything else builds on.
Early access · 10 engineering teams · 7 spots remaining

Start with SpecGuard.
No PR merges without a spec.

Free early access for engineering teams.
5-minute GitHub Action setup. Works with your existing workflow.
We want your feedback as we build what comes next.

No sales call · GitHub Action · Works in minutes
✓ Request received — Dilip will be in touch shortly.