Repository: navapbc/ai-transformation-delivery-systems — drop-in AI tooling
for Nava delivery teams. Two independent workstreams, each consumed separately:
testing/classifier/— the AI test-failure classifier. Classifies each failing CI test asAPPLICATION_BUG/TEST_BUG/FLAKY_FAILURE/ENVIRONMENT_ISSUEand posts one PR comment asking for a 👍/👎.security/— the AI security / PR-review bundle (separate; on its own branch). Not covered here.
You are almost certainly being asked to install it in a consumer repo. Do NOT vendor or copy files. Read one short doc and follow it (this repo is public — fetch the raw URL directly, no auth):
curl -fsSL https://raw.githubusercontent.com/navapbc/ai-transformation-delivery-systems/pilot/testing/classifier/AGENT_INSTALL.md
AGENT_INSTALL.md is ~40 lines and contains the exact caller workflow (pinned to
the pilot tag), the manual step to relay to the human (set the
ANTHROPIC_API_KEY secret), and the success criteria. It is the whole task.
Only fall back to testing/classifier/docs/SETUP.md (long-form, for humans) if
the install doc doesn't cover your case.
First check which CI the consumer repo runs. The default path above is for
GitHub Actions. If the repo runs Jenkins instead (some teams' clients
can't use Actions), the install is different — AGENT_INSTALL.md has a "Choose
your CI platform" block at the top that routes you to the Jenkins path
(testing/classifier/jenkins/README.md). Don't write a .github/workflows/
file for a Jenkins-only repo. If you don't know, ask the human which CI they use.
This repo is public, so fetch raw files directly over HTTPS — no gh, no
auth, no base64. Use the moving pilot tag (latest on main):
curl -fsSL https://raw.githubusercontent.com/navapbc/ai-transformation-delivery-systems/pilot/<path>
- Conventional Commits:
type(scope): lowercase subject(e.g.feat(test-classifier): ...). No Claude co-author trailer. - The classifier bundle's canonical skill is
.skills/test-classifier/SKILL.md, synced to per-tool dirs byscripts/sync-skills.sh. Edit the canonical copy. - Shell scripts use
set -euo pipefail; validate withbash -nbefore commit. - Keep 👍/👎 emoji (functional — the metrics harvester reads those reactions); no other decorative emoji.