Affected areas: 📝 Version Control ⚙️ CI / Build 📦 Dependencies
Based on 2 prior commits
5 connected, 3 available
pytest --junitxml=junit.xml or equivalent, then re-run analysis. Setup guide →pytest --cov --cov-report=xml or equivalent, then re-run analysis. Setup guide →SENTRY_AUTH_TOKEN to pull error tracking data from Sentry. Setup guide →We've detected 3 changes that differ from your project's normal patterns. Each change shows what typically happens versus what we observed this time.
a1b2c3d4 refactor: split auth migration into focused modulesWhen many files change in a single commit, CI build times increase proportionally due to broader test coverage being triggered.
Large commits that touch many files tend to also introduce new dependencies, suggesting feature branches that bundle dependency additions with implementation.
Development pattern shift detected in Version Control.\n\nSIGNAL: Files Changed is 2.1x above the typical baseline (observed: 8, typical: 3.00).\nTRIGGER COMMIT: a1b2c3d4 — refactor: split auth migration into focused modules\n\nRECENT COMMITS (2 total, showing top 5):\n a1b2c3d4 — refactor: split auth migration into focused modules Broke t (8 files)\n b2c3d4e5 — fix: optimize CI pipeline caching for auth deps (2 files)\n\nCORRELATED PATTERNS:\n [WATCH] When many files change in a single commit, CI build times increase proportionally due to broader test coverage being triggered.\n → Monitor PR sizes. If this persists, investigate whether large refactors need better decomposition.\n [WATCH] Large commits that touch many files tend to also introduce new dependencies, suggesting feature branches that bundle dependency additions with implementation.\n → Monitor PR sizes. If this persists, investigate whether large refactors need better decomposition.\n\nINVESTIGATE:\n1. Was this change intentional or did the AI drift from goals?\n2. Review commit a1b2c3d4 — what specifically caused the deviation?\n3. Suggest a course correction (not a bug fix — a realignment).\n\nAFTER FIX:\nRun `evo analyze . --verify` to re-analyze and compare against this run.\nIf the change was intentional, no fix needed — accept it in the report.
The files touched for this change was 8. Historically, similar changes had a value of 3.00 ± 1.50.
a1b2c3d4 refactor: split auth migration into focused modulesWhen many files change in a single commit, CI build times increase proportionally due to broader test coverage being triggered.
When CI pipelines run longer, the time between releases shortens — teams may be rushing releases to meet deadlines despite slower builds.
Adding dependencies increases CI build time as package installation and resolution steps take longer.
Development pattern shift detected in CI / Build.\n\nSIGNAL: Build Duration is 3.9x above the typical baseline (observed: 340, typical: 165.0).\nTRIGGER COMMIT: a1b2c3d4 — refactor: split auth migration into focused modules\n\nRECENT COMMITS (2 total, showing top 5):\n a1b2c3d4 — refactor: split auth migration into focused modules Broke t (8 files)\n b2c3d4e5 — fix: optimize CI pipeline caching for auth deps (2 files)\n\nCORRELATED PATTERNS:\n [WATCH] When many files change in a single commit, CI build times increase proportionally due to broader test coverage being triggered.\n → Monitor PR sizes. If this persists, investigate whether large refactors need better decomposition.\n [INFO] When CI pipelines run longer, the time between releases shortens — teams may be rushing releases to meet deadlines despite slower builds.\n → Confirm test coverage hasn't decreased alongside faster builds.\n [WATCH] Adding dependencies increases CI build time as package installation and resolution steps take longer.\n → Audit new dependencies for necessity, maintenance status, and known vulnerabilities.\n\nINVESTIGATE:\n1. Was this change intentional or did the AI drift from goals?\n2. Review commit a1b2c3d4 — what specifically caused the deviation?\n3. Suggest a course correction (not a bug fix — a realignment).\n\nAFTER FIX:\nRun `evo analyze . --verify` to re-analyze and compare against this run.\nIf the change was intentional, no fix needed — accept it in the report.
The run duration for this change was 340. Historically, similar changes had a value of 165.0 ± 30.00.
a1b2c3d4 refactor: split auth migration into focused modulesLarge commits that touch many files tend to also introduce new dependencies, suggesting feature branches that bundle dependency additions with implementation.
Adding dependencies increases CI build time as package installation and resolution steps take longer.
Development pattern shift detected in Dependencies.\n\nSIGNAL: Total Dependencies is 4.0x above the typical baseline (observed: 104, typical: 86.00).\nTRIGGER COMMIT: a1b2c3d4 — refactor: split auth migration into focused modules\n\nRECENT COMMITS (2 total, showing top 5):\n a1b2c3d4 — refactor: split auth migration into focused modules Broke t (8 files)\n b2c3d4e5 — fix: optimize CI pipeline caching for auth deps (2 files)\n\nCORRELATED PATTERNS:\n [WATCH] Large commits that touch many files tend to also introduce new dependencies, suggesting feature branches that bundle dependency additions with implementation.\n → Monitor PR sizes. If this persists, investigate whether large refactors need better decomposition.\n [WATCH] Adding dependencies increases CI build time as package installation and resolution steps take longer.\n → Audit new dependencies for necessity, maintenance status, and known vulnerabilities.\n\nINVESTIGATE:\n1. Was this change intentional or did the AI drift from goals?\n2. Review commit a1b2c3d4 — what specifically caused the deviation?\n3. Suggest a course correction (not a bug fix — a realignment).\n\nAFTER FIX:\nRun `evo analyze . --verify` to re-analyze and compare against this run.\nIf the change was intentional, no fix needed — accept it in the report.
The dependency count for this change was 104. Historically, similar changes had a value of 86.00 ± 3.00.
What are patterns? Patterns are recurring correlations between different areas of your project. When a change in one area (e.g. a deployment) consistently coincides with unusual behavior in another (e.g. code dispersion), we flag it so you can decide if it needs attention.
What should you do? Focus on items marked ⚠️ Action Required or 🔍 Needs Attention first. These indicate patterns that are most likely to affect code quality, stability, or security. Items marked 👁️ Worth Monitoring don't need immediate action but should be reviewed if they persist. ✅ Healthy Pattern and ℹ️ Informational confirm that things are working as expected.
When code changes are scattered across many directories, releases tend to be pushed out faster — possibly to ship hotfixes before the next planned release.
Development drift analysis for demo-repo (Dec 01, 2025 at 12:00 AM to Mar 21, 2026 at 10:00 AM).
DEVIATIONS FROM BASELINE:
- Version Control / Files Changed: 8 (typical: 3.00, 2.1x above)
- CI / Build / Build Duration: 340 (typical: 165.0, 3.9x above)
- Dependencies / Total Dependencies: 104 (typical: 86.00, 4.0x above)
RISK PATTERNS (actionable only):
- [Worth Monitoring] 2 patterns:
* When many files change in a single commit, CI build times increase proportionally due to broader test coverage being triggered.
* Large commits that touch many files tend to also introduce new dependencies, suggesting feature branches that bundle dependency additions with implementation.
Impact: Commits are touching more files than usual, increasing review burden and risk of regressions.
Action: Monitor PR sizes. If this persists, investigate whether large refactors need better decomposition.
- [Worth Monitoring] Adding dependencies increases CI build time as package installation and resolution steps take longer.
Impact: The dependency count is growing, expanding the supply-chain attack surface and potential for version conflicts.
Action: Audit new dependencies for necessity, maintenance status, and known vulnerabilities.
COMMITS (2):
a1b2c3d4 — refactor: split auth migration into focused modules (8 files)
b2c3d4e5 — fix: optimize CI pipeline caching for auth deps (2 files)
SOURCE FILES CHANGED (4):
- src/auth/oauth2.py (modified)
- src/auth/middleware.py (modified)
- .github/workflows/test.yml (modified)
- requirements.txt (modified)
TASKS:
1. ROOT CAUSE: For each deviation, identify the commit(s) that caused it.
Focus on [Action Required] and [Needs Attention] items first.
2. FIXES: Provide concrete fixes with file paths and code changes.
Goal: bring metrics back toward baseline without disrupting velocity.
3. PRIORITY: Rank fixes by urgency (immediate vs. next sprint).
4. AFTER FIXING: Run `evo analyze . --verify` to confirm deviations decreased.
If a change was intentional, accept it: `evo accept . <N>`.
5. FINDING SUMMARIES: At the end, include a section like this:
## Finding Summaries
- [family/metric]: One plain-English sentence for a non-technical reader.
(This lets the user run `evo enrich . --from response.txt` to store friendly descriptions.)
Evolution Engine has 44 universal patterns learned from 200+ open-source repositories. The more signal families you connect, the more cross-family patterns can be detected.