Repotype
Repo-Level Linting Schema Validation CI-Ready

Linting for your entire repository.
Not just code.

ESLint checks your code. Repotype checks your repo. Enforce folder structure, file naming, markdown schemas, frontmatter, and documentation standards — keeping every repository clean, consistent, and maintainable.

View on GitHub Read Documentation
Terminal
$npx repotype init
✓ Created repotype.yaml

$npx repotype validate .
✗ docs/guide.md missing required frontmatter
⚠ src/Utils.ts should be kebab-case
✗ config/ missing required README.md

$npx repotype fix . && npx repotype validate .
✓ All 142 files valid. Repository standards enforced.

What Repotype Validates

Everything that makes a repository maintainable — beyond just code syntax.

📁

Folder Structure

Define required and allowed directories. Catch misplaced files before they become permanent.

  • Required folders per project type
  • Allowlists to prevent sprawl
  • Path patterns and glob rules
📋

File Standards

Enforce naming conventions, required files, and file-level schemas across the repo.

  • Naming conventions (kebab, camel, etc)
  • Required companion files
  • JSON/YAML schema validation
📝

Documentation Quality

Validate markdown structure, frontmatter schemas, and required sections in docs.

  • Frontmatter schema enforcement
  • Required sections per doc type
  • Template placeholder detection

How It Works

Add repo-level linting to any project in minutes.

1

Define your standards

Create a repotype.yaml defining your folder structure, file rules, and schemas.

2

Validate continuously

Run repotype validate locally, in pre-commit hooks, and in CI pipelines.

3

Auto-fix violations

Use repotype fix to automatically resolve fixable issues like naming and structure.

4

Generate reports

Export compliance reports with repotype report for audits and documentation.

Error: Structure violation Warning: Convention mismatch Pass: Standards enforced