Skip to content

Add PR-ready change review reports#32

Open
sameer2191 wants to merge 1 commit into
mainfrom
feature/pr-review-report
Open

Add PR-ready change review reports#32
sameer2191 wants to merge 1 commit into
mainfrom
feature/pr-review-report

Conversation

@sameer2191

Copy link
Copy Markdown
Owner

Summary

  • Add review-report / pr-report CLI output for PR-ready Markdown or JSON change-impact reports.
  • Add the change_review_report MCP tool so agents can generate the same review artifact from graph context.
  • Improve detect_changes precision by asking Git for all untracked files, so security-sensitive paths such as workflow files are reported at file granularity.
  • Document the workflow in README, docs/agent-guide.md, docs/research-notes.md, and llms.txt.

Validation

  • npm run verify
  • npm run test:skip-gate
  • npm run package:check
  • npm run installer:audit
  • npm pack --dry-run
  • npm audit --omit=dev
  • CLI smoke: self-indexed to /private/tmp/repolens-pr-review.db, generated Markdown and JSON review reports, and confirmed Markdown starts with # RepoLens Change Review

Notes

  • The dashboard smoke remains covered by the existing skip policy in this sandbox because the local test environment cannot bind a dashboard port.

Comment thread src/core/review.ts Fixed
Comment thread src/core/review.ts Fixed

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a12c9cb13f

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread src/core/api.ts
}

export function changeReviewReport(root?: string, limit?: number, dbPath?: string) {
return buildChangeReviewReport(detectChanges(root, limit, dbPath));

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Default the report database to the selected repo

When review-report / change_review_report is run with a root outside the current working directory and no explicit --db/dbPath, this passes undefined through to detectChanges, so withStore opens the current directory's default .repolens/memory.db instead of the selected repo's default database. A common flow like repolens-mcp index /tmp/app followed by repolens-mcp review-report /tmp/app from another directory will therefore generate a report against the wrong graph or mark everything unindexed; default the DB to defaultDbPath(root) when a root is provided and no DB is supplied.

Useful? React with 👍 / 👎.

@sameer2191 sameer2191 force-pushed the feature/pr-review-report branch from a12c9cb to bf38c44 Compare June 19, 2026 16:24
Comment thread src/core/review.ts Fixed
@sameer2191 sameer2191 force-pushed the feature/pr-review-report branch from bf38c44 to 5e8a2da Compare June 19, 2026 16:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants