Automated summary
Performs an initial local review of service changes by comparing the current branch with master.
Strengths
- Detects potential regressions and bugs in the changes.
- Identifies incompatible API/contract modifications.
- Checks for missing or weak tests.
- Highlights security, configuration, and performance issues.
Limitations
- Only reviews changes between branches, not the entire codebase.
- May require clarifications if the service context is unclear.
- Does not replace a thorough human review.
When preparing a pull request to get quick initial feedback on service changes.
For a comprehensive analysis of existing code or production services.
Security analysis
SafeThe skill only instructs an AI agent to perform a code review by comparing branches, with no declared execution tools or dangerous commands. It does not involve running code, accessing secrets, or any destructive actions.
No concerns found
How this analysis is madeExamples
Compare the current branch to master and perform an initial local review of the changes in services. List critical issues, risks, quality notes, missing tests, and any questions.Review the changes in this branch compared to master, paying special attention to API contract changes and potential incompatibilities. Also note any missing tests for new endpoints.Instructions for the AI agent: initial local review of services
Goal: perform an initial local review of changes in services by comparing the current branch with master.
What to do
- Compare the current branch with the base: list the changed files and their key changes.
- Review only the changes between branches, not the entire codebase.
- Pay attention to:
- potential regressions and bugs;
- incompatible changes to APIs/contracts;
- missing or weak tests;
- security, configuration, secrets;
- performance and error handling issues.
- If the service context is unclear, note assumptions and ask for clarification.
Output format
- Critical issues (if any).
- Risks/possible regressions.
- Quality/maintainability notes.
- Missing tests.
- Questions and assumptions.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/initial-local-service-review-mm78nnwl/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/initial-local-service-review-mm78nnwl' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/initial-local-service-review-mm78nnwl/download' --output '.skill-downloads/initial-local-service-review-mm78nnwl/SKILL.md.part' && mv '.skill-downloads/initial-local-service-review-mm78nnwl/SKILL.md.part' '.skill-downloads/initial-local-service-review-mm78nnwl/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.
Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/initial-local-service-review-mm78nnwl/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.