Add greenproof to Tools

[zxyasfas]

greenproof re-runs an agent's current code against the original tests (from before the agent touched anything) to check whether a claimed-green suite actually holds, or whether it only went green because the tests changed. Pytest-only, no network calls.

Summary by Sourcery

Documentation:

• Document the greenproof tool in the testing tools list, describing its purpose of validating that green pytest runs are due to code changes rather than modified tests.

[semanticdiff-com]

Review changes with  

[qodo-code-review]

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Adds the greenproof tool to the README tools list with a short description and link.

File-Level Changes

Change	Details	Files
Document the greenproof tool in the README tools section.	Add a new bullet entry for greenproof alongside other testing tools Link to the greenproof GitHub repository Describe greenproof as a pytest-based tool that verifies whether green test runs are due to real code changes rather than modified tests	README.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[gemini-code-assist]

Code Review

This pull request adds a new entry for greenproof to the list of Python testing resources in the README.md. The reviewer suggested a grammatical correction to improve clarity by changing "it still passes" to "they still pass" to correctly refer to the plural "tests".

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

The pronoun "it" in "to see if it still passes" is grammatically ambiguous because "them" refers to "the original tests" (plural). Changing "it still passes" to "they still pass" ensures grammatical agreement with "tests".

Suggested change

	- [greenproof](https://github.com/zxyasfas/greenproof) - Checks whether a coding agent's green pytest run was earned, not manufactured by editing the tests. Snapshots the original tests, then reruns the agent's current code against them to see if it still passes.
	- [greenproof](https://github.com/zxyasfas/greenproof) - Checks whether a coding agent's green pytest run was earned, not manufactured by editing the tests. Snapshots the original tests, then reruns the agent's current code against them to see if they still pass.

[sourcery-ai]

Hey - I've found 1 issue

Prompt for AI Agents

Please address the comments from this code review:

## Individual Comments

### Comment 1
<location path="README.md" line_range="250" />
<code_context>
- [Klara](https://github.com/usagitoneko97/klara) - Static analysis tools to automatic generate test case, based on SMT (z3) solver, with a powerful ast level inference system.
</code_context>
<issue_to_address>
**issue (typo):** Fix grammar in the Klara description ("automatic generate test case" phrasing).

Please update the wording to "Static analysis tools to automatically generate test cases". Also capitalize and hyphenate AST for clarity (e.g., "AST-level inference system").

```suggestion
- [Klara](https://github.com/usagitoneko97/klara) - Static analysis tools to automatically generate test cases, based on an SMT (z3) solver, with a powerful AST-level inference system.
```
</issue_to_address>

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[sourcery-ai]

issue (typo): Fix grammar in the Klara description ("automatic generate test case" phrasing).

Please update the wording to "Static analysis tools to automatically generate test cases". Also capitalize and hyphenate AST for clarity (e.g., "AST-level inference system").

Suggested change

	- [logot](https://github.com/etianen/logot) - Test whether your code is logging correctly.
	- [Klara](https://github.com/usagitoneko97/klara) - Static analysis tools to automatically generate test cases, based on an SMT (z3) solver, with a powerful AST-level inference system.

[llamapreview]

Auto Pull Request Review from LlamaPReview

Review Status: Automated Review Skipped

Dear contributor,

Thank you for your Pull Request. LlamaPReview has analyzed your changes and determined that this PR does not require an automated code review.

Analysis Result:

PR only contains documentation changes (1 files)

Technical Context:

Documentation changes typically include:

• Markdown/RST file updates
• API documentation
• Code comments
• README updates
• Documentation in /docs directory
• License and contribution files

We're continuously improving our PR analysis capabilities. Have thoughts on when and how LlamaPReview should perform automated reviews? Share your insights in our GitHub Discussions.

Best regards,
LlamaPReview Team

[mergify]

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

• Queue this pull request