CrowdStrike / CrowdStrike/codestrike
feat: include PR description and commit messages in review context
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 3
- Forks
- 0
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 9
Description
Summary
Enrich the review prompt with the pull request's description (body) and commit messages, giving the LLM reviewer access to the author's stated intent — not just the raw diff.
Problem
Today, codestrike reviews diffs in isolation. The LLM sees what changed but not why. This leads to:
- False positives: flagging intentional trade-offs the author already explained in the PR body
- Shallow comments: the reviewer can't distinguish a bug from a deliberate design choice
- Missed context: commit messages often explain constraints ("had to use X because Y doesn't support Z") that change what a correct review looks like
Human reviewers always read the PR description first. Our AI reviewer should too.
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 by tracing how codestrike currently builds the review context from a pull request and diff. Add the PR description and commit messages to that context, then verify that the reviewer receives all three sources of information.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- ai, devtools
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100