Rigour FAQs

Question 1

Is Rigour cloud-dependent or local-first?

Accepted Answer

Rigour is strictly local-first with zero cloud dependency and zero telemetry. All code quality checks and enforcement happen entirely on your local machine, offering maximum privacy, speed, and control.

Question 2

What is Rigour and what problem does it solve?

Accepted Answer

Rigour is a developer tool that enforces stringent engineering standards on AI-generated code. It prevents the 'Vibe Coding' trap by requiring AI agents to meet local quality gates through an iterative fix-loop before marking tasks as complete, ensuring compliant and high-quality code.

Question 3

What specific code quality checks does Rigour perform?

Accepted Answer

Rigour performs comprehensive checks including limits on file size, code hygiene (e.g., disallowing TODO/FIXME comments), cyclomatic complexity, presence of required documentation (e.g., SPEC.md, ARCH.md), safety rails for protected paths, and context alignment to prevent drift.

Question 4

How does Rigour ensure AI-generated code meets quality standards?

Accepted Answer

Rigour leverages local-first quality gates and an iterative fix-loop mechanism. It checks code against predefined standards covering file size, code hygiene, complexity, required documentation, and safety rails, guiding AI agents to refine their output until it passes all checks.

Question 5

How does Rigour integrate with AI agents and CI/CD pipelines?

Accepted Answer

Rigour seamlessly integrates with various AI coding agents like Claude Code, Cursor, and Gemini via CLI commands or an MCP server. For CI/CD, it can be easily embedded using a `rigour check --ci` command to act as an enforcement gate, ensuring all AI-generated code meets standards before merging.

Rigour

Rigour

주요 기능

사용 사례

주요 기능

사용 사례