Automated summary
Reviews the project against a specific AI system rubric and generates structured feedback with scores, findings, and action items.
Strengths
- Structured output with per-criterion scores, findings, and a checklist.
- Grounds evaluation in an explicit rubric for more objective review.
- Cites concrete evidence from the repository for each finding.
Limitations
- Dependent on external rubric URLs being accessible.
- Tailored to a specific course project, so not fully generic.
When preparing for a project checkpoint that requires rubric-based code review.
For open-ended code review without a rubric or for casual feedback.
Security analysis
SafeThe skill is a text-based instruction for code review; it does not declare or use any tools, and there are no destructive, exfiltrating, or obfuscated actions. It only provides guidance for a manual review process.
No concerns found
How this analysis is madeExamples
Review the current module against the AI System rubric (https://csc-343.path.app/projects/project-2-ai-system/ai-system.rubric.md) and give scores and findings.Run a rubric-based code review for the checkpoint, focusing on the latest changes, and list critical issues and action items.Check the repository against the Elegance Rubric at https://csc-343.path.app/rubrics/code-elegance.rubric.md and provide structured feedback.AI System Code Review (Rubric-Based)
Use this skill to review the project against the AI System rubric and provide actionable feedback before each checkpoint.
Required Inputs
- Repository context (current module spec, recent changes, test results).
- Elegance Rubric: https://csc-343.path.app/rubrics/code-elegance.rubric.md
- AI System Rubric: https://csc-343.path.app/projects/project-2-ai-system/ai-system.rubric.md
Review Process
- Identify the module(s) included in the current checkpoint.
- Read the module spec and README updates.
- Inspect implementation, tests, and documentation.
- Score each rubric criterion with short justification.
- List concrete fixes or improvements needed before submission.
Output Format
Summary
One short paragraph describing overall readiness.
Rubric Scores
Provide a score and justification for each criterion in the rubric.
Findings
List issues by severity (critical, major, minor). Each finding must include:
- Evidence (file paths, function names, or README sections)
- Impact on rubric scoring
- Suggested fix
Action Items
Checklist of next steps to address issues.
Questions
Any missing information needed to finalize the review.
Style Guidelines
- Cite evidence from the repository.
- Be concise and direct.
- Prefer clear, actionable feedback over general advice.
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/ai-system-code-review-rubric-msh3us48/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/ai-system-code-review-rubric-msh3us48' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/ai-system-code-review-rubric-msh3us48/download' --output '.skill-downloads/ai-system-code-review-rubric-msh3us48/SKILL.md.part' && mv '.skill-downloads/ai-system-code-review-rubric-msh3us48/SKILL.md.part' '.skill-downloads/ai-system-code-review-rubric-msh3us48/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/ai-system-code-review-rubric-msh3us48/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.