Checks

A Warestack Check works like a protection rule, but with far more flexibility and intelligence.

Instead of static conditions, you create checks using natural language, and Warestack’s agentic engine translates them into executable logic. You can apply them per team, per repository, or across entire workspace groups.

PR example

Imagine asking teammates to always add the right migration whenever they edit a SQL file. Instead of reviewing every detail, Warestack automates these small but critical rules, making them active checks that run on every PR.

Warestack translates natural language prompts into deterministic checks represented in a YAML file. This makes every check traceable, versioned, and easy to share across teams.

checks:
- description: "PRs changing .sql files must include .migration.sql files."
  enabled: false
  severity: "medium"
  event_types: ["pull_request"]
  parameters:
    file_pattern_dependency:
      source_pattern: "*.sql"
      dependent_pattern: "*.migration.sql"

Types of Checks

Warestack supports two types of checks:

1. Enterprise-ready checks from open standards and best practices used by regulated software teams. Examples include checks for SOC-2 and ISO-27001 review requirements, commit and merge approval rules, access control validations, and more.

2. Custom rules created in natural language.
   Warestack supports custom rules for GitHub issues, Linear issues (coming soon), pull requests, deployment reviews, and workflow runs. Each rule is evaluated for effectiveness before being applied to ensure stability and safety.