Record evidence for
AI-assisted development
AIDA records scoped evidence, declared autonomy, and repository change signals— with assumptions and limits kept visible.
npm install -g @aida-dev/cli
Core Metrics
Repository Change Signals
How often eligible files are touched again within fixed horizons. Too-recent files stay visible and outside the denominator; retouch is not presented as a defect.
Quality Over Time
The repo compared with its own past — the comparator that still works once AI touches nearly every commit. Every period measured through the same window; periods too recent to judge are never compared.
Autonomy, not the binary
Two orthogonal axes: what level of AI participated (autocomplete / assisted / agent) and how we know. Cohort tables render only where real evidence backs them — an assumption never becomes a table.
Declared provenance
The commit hook stamps a mode when AIDA_MODE, a supported agent environment, or a team-configured default determines it. When AIDA cannot know, it writes nothing — unknown remains honest.
PR Comments
Post AIDA reports directly on pull requests and merge requests. GitHub Actions and GitLab CI are supported; comments are explicit network operations that require a token.
CI/CD Ready
Use the documented workflow with full Git history and scoped token permissions. It runs on every PR and updates its own comment automatically.
Get Started
Install globally
npm install -g @aida-dev/cli
Navigate to your Git repo
cd /path/to/your/repo
Run analysis
aida collect --since 30d && aida analyze && aida report
Supported AI Tools
Known tool and trailer signals can establish AI involvement. They do not, by themselves, prove an autonomy mode; absent evidence remains visible as unknown.
CI/CD Integration
Add the documented workflow to create a scoped report on every pull request. PR comments require explicit token permissions.
Ready to make AI evidence auditable?
Start with the repository signals Git can support — and keep their limits visible.