Skip to main content

🧪 Repo CLI Agent — For Repository-Wide Coverage

The Early CLI for Repository lets you generate unit tests for individual files or entire folders in your codebase — making it the fastest way to raise coverage across legacy code, specific modules, or large areas of your app.

📌 When to Use​

Use the Repo CLI Agent when:

  • You want a one-time coverage boost across a folder
  • You're onboarding a legacy service or utility layer
  • You want to run weekly or monthly coverage maintenance
  • You’re using GitHub, Bitbucket, or another supported SCM
  • You want to integrate with Jenkins, CircleCI, or GitHub Actions

→ When to Use Which Agent →

⚙️ How It Works​

  1. You specify a target file or folder using --target-directory ./src/utils or --target-directory ./src/utils/math.ts
  2. The CLI scans the target recursively if it’s a folder, or focuses on the single file if specified
  3. Runs your configured coverage command
  4. Identifies low or zero-covered functions
  5. Generates tests using AI (Jest, Mocha, etc.)
  6. Optionally commits results (AUTO_COMMIT=true)

→ Command: early generate-for-project
→ Configure via CLI flags or environment variables

🔐 Requirements​

To use this agent:

🧪 First Integration Step​

See full setup here → Integration Guide

early generate-for-project \
  --target-directory ./src/api \
  --token $TOKEN \
  --api-key $API_KEY \
  --ref-name main

📦 Supported CI/CD Platforms​

  • ✅ GitHub Actions
  • ✅ Jenkins
  • ✅ CircleCI
  • ✅ GitLab CI
  • ✅ Self-hosted CI tools

All platforms must support Node.js 20 and repo access.

⏭️ What’s Next?​