Our review

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 to use it

When preparing for a project checkpoint that requires rubric-based code review.

When not to use it

For open-ended code review without a rubric or for casual feedback.

Examples

Review against AI System rubric

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.

Checkpoint rubric review

Run a rubric-based code review for the checkpoint, focusing on the latest changes, and list critical issues and action items.

Elegance rubric review

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.

AI System Code Review (Rubric)

Recommended for