repowarden

repowarden guards the entrance to your Git repositories: commit messages, branch naming, secrets, formatting and tests, whatever the language. The same rules apply on developer machines (hooks) and in CI, and main is protected on the server side. Unsure how it compares with pre-commit, commitlint, gitleaks or Danger? Comparison and measurements.

flowchart LR
    A["Developer machine<br/>repowarden hooks"] -->|git push| B["CI<br/>GitHub action · GitLab template"]
    B -->|required checks| C["Protected main branch"]
    A -. "immediate feedback<br/>automatic fixes" .-> A
    B -. "authoritative<br/>cannot be bypassed" .-> B

Level	Role	Can be bypassed?
Developer machine	Formats the code, prefixes the commit message, rejects a badly named branch, tests before the push	yes (--no-verify)
CI	Re-runs every check on each PR / MR	no
Server	Merge blocked if the CI fails, direct push to main forbidden	no

What repowarden does

• Commit messages — Conventional Commits enforced; the prefix is derived from the branch (feat/cart → feat(cart): …).
• Branches — <type>/<topic> format, with a suggested rename command; merged branches deleted automatically, on the server and on developer machines.
• Secrets — detected by gitleaks before the commit and in CI.
• Formatting — only the staged content is formatted, with the project's own tool (prettier, ruff, gofmt, Spotless…); work in progress is preserved.
• Tests — on push, only the affected projects are tested, on the pushed commit.
• Dead code — only new dead code is reported: proven (blocking) or candidate (to check); definition.
• Releases — version computed from the commits, changelog, tag and release, with no token and no manual step; reusable by your projects, with human approval when needed.

More than 25 technologies detected automatically — Java, JavaScript/TypeScript, Python, Go, Rust, PHP, Ruby, .NET, Flutter, Swift, Elixir, C/C++, Terraform, Helm, Kubernetes, Ansible, Docker… → the full list.

In VS Code — the repowarden-vscode extension applies the same rules in the editor: commit assistant, branch name checked in the status bar, alert if the hooks no longer run.

In 30 seconds

Developer machine — once, for every repository

npm install -g repowarden
repowarden install --global

.github/workflows/repowarden.yml — CI (excerpt)

- uses: actions/checkout@v7
  with: { fetch-depth: 0 }
- uses: simdevWarden/repowarden@v4
  with: { strict: true }

→ Quick start · full example: repowarden-demo

Reliability

• Each language and tool is checked in CI on a real project with its own tooling.
• Tested on Linux, macOS and Windows; signed releases (verify a release).
• Project assessed by OpenSSF Scorecard.