Code review requests

Skill soden46/syarif-laravel-ai-skills/skills/code-review-requests

Request effective code reviews-specify focus areas, provide context, ask for architectural feedback, reference Laravel conventionsFrom its SKILL.md

Install

npx -y skills add soden46/syarif-laravel-ai-skills --skill code-review-requests

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.0 KB, 347 tokens by cl100k_base, as published. Nobody here has run it

Code Review Requests

Use this skill when a Laravel task involves code review requests.

This skill is adapted to the personal Laravel standards in this repository. It maps the public code-review-requests topic from jpcaparas/superpowers-laravel into the local code-review-requests catalog without copying third-party skill body text.

Syarif Defaults

Follow Laravel conventions before introducing custom abstractions.
Prefer project-local patterns when they are explicit and tested.
Keep controllers focused on HTTP orchestration.
Put validation, authorization, transactions, side effects, and integrations at clear boundaries.
Keep client names, credentials, internal URLs, provider secrets, and project-specific business rules out of reusable standards.
Verify important behavior with the smallest meaningful tests and quality checks.

Workflow

Detect the Laravel version, PHP version, runner, package manager, and existing project conventions.
Identify the smallest local skill set that overlaps this topic.
Implement or review the change using Laravel-native APIs first.
Add abstractions only when they reduce real complexity or protect a meaningful boundary.
Run targeted tests and available quality checks before handoff.

Checkpoints

Authorization and validation boundaries are explicit.
Query shape, transactions, queues, cache, files, and external calls are intentional when touched.
User-facing behavior has feature, unit, browser, or integration tests at the right level.
Logs and errors are useful without exposing secrets or unnecessary personal data.
Documentation or proposals avoid importing source-project names or one-off business rules.

Related Skills

using-laravel-standards
architecture
testing
security

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most code review skills give in 347 tokens

Counted across 668 of the 814 authors here whose files we hold, read 2026-09-06

Provide technical reasoning when pushing backin 84 of 668, across 70 files
Fix critical issues immediatelyin 77 of 668, across 60 files
Dispatch a code reviewer subagentin 76 of 668, across 59 files
Fix important issues before proceedingin 73 of 668, across 56 files
Ask for clarification on unclear itemsin 68 of 668, across 56 files
Verify feedback against codebase before implementationin 66 of 668, across 55 files
Implement fixes one at a timein 64 of 668, across 53 files
Test each fix individuallyin 62 of 668, across 51 files
Restate technical requirements in own wordsin 57 of 668, across 46 files
Reply to inline comments in the specific threadin 51 of 668, across 40 files
Note minor issues for laterin 49 of 668, across 34 files
Group findings by severityin 48 of 668, across 47 files

Said here and by no other author read

Follow Laravel conventions
Prefer project-local patterns
Keep controllers focused on HTTP
Use Laravel-native APIs first
Add abstractions to reduce complexity
Run targeted tests before handoff

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.