- Home
- Skills
- Code Quality & Review
- t2s pull request review
Works with the AI Agents you already use
t2s pull request review
- **Prioritized Checklists** generates a structured review list categorized by HIGH, MEDIUM, and LOW priority items.
$1.99
t2s pull request review
Example session with this skill installed
Please review this PR diff: 500 lines added to auth_service.go, 10 lines changed in readme.md, and no new test files were added.
- Read your context and instructions
- Compiled the t2s pull request
I have analyzed the provided diff data and calculated the risk profile for this pull request.
Pull Request Review — Development Team, 2024-05-20
1. Summary
- PR Risk Score: 85 (CRITICAL)
- Files Analyzed: 2
- Total Lines: 510
- Test Coverage Indicator: 0% (Missing paired tests)
2. File Analysis
| Path | Category | Additions | Deletions | Risk Score | Level |
|---|---|---|---|---|---|
auth_service.go | logic/security | 500 | 0 | 85 | CRITICAL |
readme.md | documentation | 5 | 5 | 5 | LOW |
3. Review Checklist
- HIGH: Validate all 500 additions in
auth_service.gofor authentication bypass vulnerabilities. - HIGH: Verify why no test files were created or modified for a major logic change.
- LOW: Ensure
readme.mdupdates accurately reflect the changes in the service.
4. Test Coverage
- Source files without paired tests:
auth_service.go - Source files with paired tests: None
5. Warnings and Data Quality
- W001: No test files detected in diff for high-risk logic changes.
6. Recommendations and Items for Human Review
The change to auth_service.go is extensive and lacks supporting tests, resulting in a CRITICAL risk score. This requires a deep dive into the logic flow.
Management decision required
Next steps
- Request unit tests for the new logic in
auth_service.go. - Assign a senior security engineer to review the authentication logic.
- Confirm if the
readme.mdchanges cover the new service parameters.
Connects securely to your tools. The creator never sees your data.
About this skill
Manual pull request reviews often suffer from inconsistent depth or missed edge cases in high-risk files. This skill automates the risk assessment of PR diffs, calculating scores based on change size, file sensitivity, and test coverage indicators to prioritize human attention.
What it does
- Risk Scoring calculates individual file and total PR risk levels based on deterministic weightings of additions, deletions, and file types.
- Diff Analysis parses pull request metadata and file changes to categorize the scope of work.
- Prioritized Checklists generates a structured review list categorized by HIGH, MEDIUM, and LOW priority items.
- Coverage Auditing identifies missing test file pairings for modified source files.
- Decision Support provides a standardized summary to help teams decide if a PR requires senior oversight or immediate merging.
How it works
- The user provides a PR diff or a list of file changes including line counts.
- The skill constructs a
request.jsonpayload mapped to the change data. - A self-contained Python script processes the input to calculate scores and identify patterns.
- The findings are returned in a structured report including a file analysis table and a prioritized checklist.
Frameworks & tools
This skill uses a Python-based logic engine to process JSON-formatted diff data. It is platform-agnostic and works with outputs from GitHub, GitLab, Bitbucket, or local Git diffs.
Why this beats prompting it yourself
Generic prompts often hallucinate risk or fail to consistently apply weighting logic across large diffs. This skill uses a deterministic calculation script to ensure that a 500-line change in a controller always receives the same risk score, removing subjective bias from the initial triage.
Use cases
- Identify high-risk logic changes that require senior dev approval.
- Detect modified source files that lack corresponding test updates.
- Generate a standardized review checklist for team leads.
- Quantify PR complexity to better estimate review time.
Known limitations
This skill assesses risk and priority, not code quality or stylistic correctness. It does not perform actual test execution or security vulnerability scanning.
Assessments are based on diff metadata, not code logic or runtime behavior. Does not execute tests or scan for security vulnerabilities. Requires file paths and line counts.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed today