HammerCLI scores every git commit for R&D tax credit relevance — SR&ED, IRS Section 41 — silently, in the background. Your team doesn't change a thing. The evidence is already there.
Available on PyPI · Works with any git repo · macOS, Linux, Windows (Git Bash)
60-Second Install
# 1. Install from PyPI $ pip install hammer-cli # 2. Register (email-verified) and set up your global hook $ hammer init → Enter email: dev@company.com → Code sent. Enter the 6-digit code from your inbox: ✓ API key saved to ~/.hammer/config.json # 3. Install the post-commit hook in any repo (or scan an entire directory) $ cd ~/my-project && hammer install ✓ Hook installed. Every commit will be scored silently.
That's it. From now on, every commit is scored in the background.
See your data with hammer status or hammer log.
How It Works
Your team runs git commit exactly like they always have.
HammerCLI's post-commit hook fires in the background — non-blocking, no UI, no prompts.
The commit metadata is sent to our managed scoring API and rated by an LLM with a prompt tailored to your domain — SR&ED today, PCI and SOC 2 next. Scores: Strong, Moderate, Weak, Minimal.
When tax season hits, run hammer push
to send qualifying commits into HammerLedger — where they become part of a cryptographically-sealed evidence chain ready for the auditor.
Commands
| Command | What it does |
|---|---|
hammer init |
Register via email verification, save API key to ~/.hammer/ |
hammer install |
Install per-repo post-commit hook. Use --scan to bulk-install across all repos under a folder. |
hammer status |
Summary of scored commits in the current repo (or all repos with --all). |
hammer log |
List scored commits with category and confidence. |
hammer flush |
Retry any commits that failed to score (offline queue). |
hammer override |
Per-repo domain or ledger override — e.g. score one repo against PCI, another against SR&ED. |
hammer export |
Dump scored commits to JSON or CSV. |
hammer push |
Send qualifying commits into your HammerLedger instance. |
hammer doctor |
Diagnostic checks: git, API connectivity, hooks, storage. |
Run hammer --help for the full list (15 commands including scan, prune, migrate, exclude, uninstall, config).
Why HammerCLI
Every year, finance teams ask developers to remember what they worked on twelve months ago. That's how qualifying work gets missed — and how unsupported claims get filed.
Per-repo post-commit hook, non-blocking, runs in the background. Your developers don't see it. Doesn't conflict with any other git hooks you've installed.
Git is where engineering work actually happens. Scoring at commit-time means the evidence is timestamped and immutable — not reconstructed from a JIRA archive twelve months later.
1,000 scored commits per month, free. Most early-stage engineering teams never hit it. Heavier use upgrades to CLI Pro; serious tax-credit work upgrades to HammerLedger.
Today: Canadian SR&ED and US IRS Section 41. Coming: PCI compliance evidence, SOC 2 change-management trails, audit-ready records for regulated engineering work.
$ pip install hammer-cli && hammer init
Part of the HammerAI Ecosystem