pr-review
Workflow
Step 1 — Parse the PR URL
Extract owner, repo, pr_number from the URL:
https://github.com/{owner}/{repo}/pull/{pr_number}
Step 2 — Fetch PR metadata + diff
Use the GitHub API. If a token is available in context or provided by user, use it.
# PR metadata
curl -s -H "Authorization: Bearer {token}" \
-H "Accept: application/vnd.github.v3+json" \
"https://api.github.com/repos/{owner}/{repo}/pulls/{pr_number}"
# Diff
curl -s -H "Authorization: Bearer {token}" \
-H "Accept: application/vnd.github.v3.diff" \
"https://api.github.com/repos/{owner}/{repo}/pulls/{pr_number}"
More from masterfermin02/agent-skills
laravel-money
Use the cknow/laravel-money package for Laravel projects that need to model, persist, cast, format, compare, or calculate money safely. Trigger when working on Laravel apps that handle currency, prices, totals, invoices, billing, checkout, discounts, taxes, balances, monetary casts, or any request mentioning money handling, currency formatting, integer minor units, Money value objects, or 'laravel-money'. Prefer this over raw floats for monetary values in Laravel.
2unit-testing
Write, review, and improve unit tests using best practices. Framework-agnostic — applies to any language or test framework (xUnit, Jest, PHPUnit, Pest, JUnit, etc.). Use when writing new unit tests, reviewing existing tests for quality, refactoring fragile or brittle tests, choosing between mocks/stubs/fakes/spies, naming tests, structuring test files, identifying anti-patterns, generating test doubles, or applying patterns like AAA, Object Mother, Builder, or Assert Object. Also triggers on phrases like generate tests for this code, my tests are brittle, tests keep breaking, how do I mock this, what is the difference between mock and stub, write a test for, add tests to, test coverage, unit test this, improve my tests, tests are hard to maintain.
1php-update-with-rector
>
1ai-era-architecture
Define pragmatic software architecture for the AI era using rules like making important logic easy to find, keeping changes local, reducing coupling where it matters, protecting critical business rules, making debugging less painful, supporting safe iteration, and avoiding unnecessary ceremony. Use when designing project structure, evaluating whether clean architecture is worth it, or setting architecture principles for modern teams.
1php-the-right-way
PHP best practices skill based on phptherightway.com. Use whenever writing, reviewing, or refactoring PHP code to ensure it follows modern PHP standards and idioms. Triggers on: writing PHP code, reviewing PHP files, asking about PHP best practices, PHP code style (PSR-1/PSR-12/PSR-4), PHP OOP patterns, namespaces, Composer, dependency management, security (XSS, CSRF, SQL injection, password hashing), error handling, testing (PHPUnit/Pest), templating, databases, design patterns (Factory, Singleton, MVC, Strategy), functional PHP, or any question about 'the right way' to do something in PHP.
1frontend-pragmatic-architecture
Apply pragmatic AI-era architecture rules to frontend projects such as React, Next.js, or similar frameworks. Use when organizing pages, features, components, hooks, UI state, and frontend API calls so important logic stays easy to find and changes stay local.
1