microsoft / microsoft/BCQuality
Review statistics
Nobody has claimed this yet.
- Dominant language
- AL
- Stars
- 212
- Forks
- 121
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 33
Description
We can discuss this from various aspects, but here is the mock-up my agent did:
Obviously, this is only aspect of the review. If you add other actions from other AI agents, like writing tests, testing code, and creating documentation, those statistics can be expanded.
And for AI review itself, we also added the statistics of sources for review comments - so we can track which aspect is bringing us the most value.:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the two attached mock-ups, then clarify which review actions and comment-source statistics are in scope. Done should be defined as an agreed set of statistics and a corresponding implementation plan; this issue names no files, tests, or entry points.
Written by the indexing model from the issue text.
Assessment
- Domain
- analytics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100