↓ Skip to main content
Xianpeng Shen Build & release engineer since 2009 · Vilnius

Open-source guardrails for software delivery.

The checks that run between a commit and a release, whether a person or an AI agent wrote the code.

From commit to release

  1. commit commit-check, Conventional Branch Commit message, branch name and AI-attribution policy
  2. review cpp-linter flagship clang-format and clang-tidy on every pull request
  3. build explain-error, Agent8 AI diagnosis of Jenkins failures; Java 8 hosts on a current Jenkins
  4. release release-ledger SBOM, signed provenance, exploited-CVE watch for the EU CRA
downloads of the clang-tools static binaries
750,000+
GitHub repositories depend on cpp-linter
1,000+
PyPI downloads of commit-check a month
55,000+
member, two projects under jenkinsci
Jenkins org
in Lithuania for public contributions
Top 3

cpp-linter is used by projects from

AWSApacheSamsungQualcommBloombergLLNLNextcloud

cpp-linter

Lint every pull request.

clang-format and clang-tidy on each PR, as a GitHub Action, a pre-commit hook and a Python package. Fixes arrive as review suggestions you can commit in one click.

  • thread comment
  • PR review suggestions
  • step summary
  • auto-fix

commit-check

Commit policy as code.

Commit messages, branch names, authors, sign-offs, tags, files and AI attribution, checked from one config file. In CI, as a pre-commit hook, or by an AI agent reading its JSON output.

  • GitHub Action
  • pre-commit hook
  • --format json
  • AI attribution

Infrastructure you own.

Jenkins agents for Java 8 build hosts, and Mac backups to your own storage.

Also: keelapps, admin apps for Jira and Confluence Cloud, on the Atlassian Marketplace.

Writing.

Since 2017, in Chinese and English.

All posts ›

If one of these tools saves you time, sponsoring keeps it maintained. Sponsor on GitHub ›