Skip to content
Skills Library
Programming · Writing

code-review-requests

/code-review-requests

Request effective code reviews-specify focus areas, provide context, ask for architectural feedback, reference Laravel conventions

Licence
MIT
Last repository change
13.08.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 13.08.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Request effective code reviews-specify focus areas, provide context, ask for architectural feedback, reference Laravel conventions

Original author description

Request effective code reviews-specify focus areas, provide context, ask for architectural feedback, reference Laravel conventions

How it works

  1. Syarif Defaults
  2. Workflow
  3. Checkpoints
  4. Related Skills
Original SKILL.md headings · 39 lines, 249 words
SKILL.md preview
---
name: code-review-requests
description: Request effective code reviews-specify focus areas, provide context, ask for architectural feedback, reference Laravel conventions
tags:
  - laravel
  - php
---

# 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

1. Detect the Laravel version, PHP version, runner, package manager, and existing project conventions.
2. Identify the smallest local skill set that overlaps this topic.
3. Implement or review the change using Laravel-native APIs first.
4. Add abstractions only when they reduce real complexity or protect a meaningful boundary.
5. 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`

Versions

The database has no other skills named code-review-requests.

Database snapshot: 13.11.2026 · package version 6bfdd7c2f2a8 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90laravel:code-review-requests
    Request effective code reviews—specify focus areas, provide context, ask for architectural feedback, reference Laravel conventions
  • 100laravel-conventions
    Consolidated Laravel project conventions: Action pattern, Form Requests, Policies, routing, Inertia integration, code style. Apply when: writing or reviewing Laravel backend code (controllers, actions, requests, policies, providers). Activated automatically by…
  • 95code-review
    Code review best practices and workflow skill. Use when: reviewing pull requests, performing peer code review, setting up code review standards, or improving code quality processes. Triggers: code review, PR review, pull request review, peer review, code quality, review…
  • 90laravel-review
    Review a Laravel pull request for bugs and rule breaches, then post the findings as inline GitHub comments. Use for "review PR 12", "re-review", or "post the review".
  • 90laravel-best-practices
    Apply this skill whenever writing, reviewing, or refactoring Laravel PHP code. This includes creating or modifying controllers, models, migrations, form requests, policies, jobs, scheduled commands, service classes, and Eloquent queries. Triggers for N+1 and query performance…
  • 90laravel-best-practices
    Apply this skill whenever writing, reviewing, or refactoring Laravel PHP code. This includes creating or modifying controllers, models, migrations, form requests, policies, jobs, scheduled commands, service classes, and Eloquent queries. Triggers for N+1 and query performance…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.