Devtools
CI Pipeline Speed Analyzer
Find which CI steps waste time and how to speed them up
Intermediate14h1–2
GitHub APIEChartsNode.js
17/20Pull Request Risk Score
Score each PR for risk so reviewers focus where it matters.
Intermediate16h1–2 people18/20 fit
Build Pull Request Risk Score for engineering teams in ~16h with 1–2 people. Stack: GitHub API + Node.js + LLM.
Why it wins: Directly useful for every team.
Build flow
01 · Problem
Reviewers spend equal time on trivial and dangerous changes.
02 · Solution
Combine diff size, touched hot files, test coverage changes and ownership into a risk score with an LLM summary posted on the PR.
03 · Build
- 1Fetch PR data
- 2Compute factors
- 3Summarise
- 4Post comment
04 · Demo
Open a PR touching payment code and show a high-risk comment.
MVP checklist
- Risk factors
- PR comment
- Reviewer suggestions
- Trends
Tech stack
| Tech | Role | |
|---|---|---|
| GitHub API | Repo + PR data | API |
| Node.js | Backend runtime | Backend |
| LLM | Language model | AI |
Related ideas
More DevtoolsDevtools
OpenAPI Breaking Change Detector
Detect breaking API changes in pull requests before clients break
Intermediate14h1–2OpenAPINode.jsGitHub Actions17/20Devtools
Unit Tests from Diffs
Generate missing unit tests for the code changed in a PR
Intermediate16h1–2LLMNode.jsVitest17/20