--- title: "Student code project reviewer" type: "skill" url: "https://useaiblocks.com/skills/student-coding-project-review" updated: "2026-10-28" first_published: "2026-10-25" job: "Study and check your understanding" tested: true licence: "MIT" source: "https://github.com/yugash007/edu-agent-skills/tree/e75f44303570bb2eae37a8f7536c0358be2502ee/skills/projects/project-review" instructions: "https://useaiblocks.com/skills/student-coding-project-review/SKILL.md" --- # Student code project reviewer > Get a student coding project review: specific strengths, up to five ranked fixes with code references, and a next step for each. Share your project, requirements and what you hoped to learn. It starts with your own review, then checks the work and the learning behind it. You get specific strengths, up to five priority issues and a next step for each. Free skill for the job "Study and check your understanding" · Level: beginner · Thinking: medium · Tested · Updated 2026-10-28 ## Links - Page: https://useaiblocks.com/skills/student-coding-project-review - Instructions (SKILL.md): https://useaiblocks.com/skills/student-coding-project-review/SKILL.md - All files (zip): https://useaiblocks.com/skills/student-coding-project-review.zip - JSON version: https://useaiblocks.com/skills/student-coding-project-review.json - In your AI: connect https://useaiblocks.com/mcp and ask "Use AI Blocks to get student-coding-project-review" ## What it does Share your project, requirements and what you hoped to learn. It starts with your own review, then checks the work and the learning behind it. You get specific strengths, up to five priority issues and a next step for each. ## What you give it - Project code, notes and original requirements. - Your learning goals and your own view of the work. ## What you get - Specific strengths tied to your project. - Up to five ranked issues with code references. - Next steps and a reflection question. ## Example: what goes in and what comes out ### What goes in - Your project code and any notes - The original requirements or assignment - Your learning goals (optional) - Your own view of what went well and what you would change ### What comes out - **Self-assessment prompt**: Two questions asked before any feedback: what went well, and what you would change. - **Praise**: Two or three strengths that point to real choices in your code. - **Critique**: Up to five issues in priority order, each with its area, how serious it is and a code reference. - **Grow**: One concrete next action for each major issue, plus a skill or idea to revisit. - **Retrospective question**: One closing question about the most important thing you learned from building this. ## Skip it when - You are stuck on a bug right now: ask your AI to help you debug it step by step, then come back for a review. - You need a concept explained first: ask your AI to teach that idea, then share your project. - You want your code rewritten for you: this review points to issues and leaves the fixing to you. ## How to use it 1. Open Claude, ChatGPT or Gemini and paste in the skill instructions. 2. Paste your project code, the original requirements and your learning goals. 3. Answer the first two questions honestly: what went well, and what you would change. 4. Read the praise and the ranked issues. Fix them yourself, starting with the top one. 5. Answer the closing question and keep your answer as a note. Other skills it names are optional, so you can skip them. ## What to do next - [Student confidence task planner](https://useaiblocks.com/skills/confidence-building-task-ladder): Student confidence task planner ## Sources and credits - From edu-agent-skills contributors: https://github.com/yugash007/edu-agent-skills/tree/e75f44303570bb2eae37a8f7536c0358be2502ee/skills/projects/project-review, shared under the MIT licence (original name: project-review). - [project-review skill](https://github.com/yugash007/edu-agent-skills/tree/e75f44303570bb2eae37a8f7536c0358be2502ee/skills/projects/project-review), edu-agent-skills contributors: Copied under the MIT licence. We gave it a plain name. We added Before you start and After this sections that link to other AI Blocks steps. ## Instructions (SKILL.md) ## Purpose Provide structured, constructive review of a learner's project at a milestone or completion checkpoint. Combines technical evaluation with learning-outcome assessment. Uses Praise-Critique-Grow to maintain learner motivation while surfacing real issues. ## Activation - Milestone reached in `build-with-me`. Feature or project completed. Learner asks for feedback on their work. Pre-submission review (assignment, portfolio, interview take-home). - **Skip if**: project hasn't started. Learner needs concept help → `teach-concept`. Active debugging in progress → `debug-teacher`. - **Routing**: issues found → use `challenge-generator` for targeted practice. Concept gaps → `teach-concept`. Design issues → `architecture-review`. Log weak areas to `weak-area-tracker`. ## Inputs - Project/feature code and documentation, original requirements/scope, learner's stated goals, relevant assessment criteria. ## Review Dimensions - **Scope**: does it meet stated requirements? Scope creep? Missing features? - **Correctness**: does it produce correct results? Edge cases handled? - **Code Quality**: readability, naming, structure, DRY, separation of concerns. - **Testing**: test coverage, test quality, edge case testing. - **Learning Outcomes**: what did the learner demonstrate they understand? What gaps remain? ## Workflow 1. **Self-Assessment** — Ask learner first: "What do you think went well? What would you change?" This surfaces their self-awareness before external feedback. 2. **Review** — Evaluate across all 5 dimensions. Note strengths and issues with specific code/design references. 3. **Praise** — Start with 2–3 specific strengths. Reference actual decisions/code, not generic compliments. 4. **Critique** — List issues priority-ordered. Each: dimension, description, severity, specific code reference. Max 5 issues per review — more overwhelms. 5. **Grow** — For each major issue: one concrete next action. Frame as growth opportunity, not failure. Include a learning recommendation (skill or concept to revisit). 6. **Retrospective** — Ask one synthesis question: "What's the most important thing you learned from building this?" Record answer for `learning-memory`. ## Rules - DO: require self-assessment before giving feedback. - DO: praise specific decisions, not generic effort. - DO: limit critique to top 5 issues — prioritize by impact. - DO: frame growth actions as opportunities, not failures. - DO: end with a retrospective question and record the answer. - DON'T: start with criticism — always Praise first. - DON'T: give vague feedback ("good job" / "needs work"). - DON'T: rewrite the learner's code — point to issues and let them fix. - DON'T: skip the self-assessment — it builds metacognitive skill. ## Output Responses should contain: self-assessment prompt, praise (2–3 specific strengths), critique (issues with dimension + severity + code reference), grow (next actions + learning recommendations), and retrospective question. Format naturally. ## Checklist - [ ] Self-assessment requested before external feedback. - [ ] Praise references specific code/decisions. - [ ] Critique limited to top 5 issues, priority-ordered. - [ ] Retrospective question asked and answer recorded. ### Before you start Use the material below to do this job. If facts or tool access are missing, explain what you can finish and what must wait. **What you need** (use your own material or the linked skill): - **A codebase** (yours): a project's code, in a folder or repo the AI can open. - **Your question** (yours): the decision or problem, and what a good outcome looks like. How to start: 1. **Look first.** Use what they've already attached, pasted or put in their about-me note. In a coding assistant with file access, look in the project too for these by name. 2. **Check what's missing.** Look for a codebase, your question. They can attach files, paste the details, or share a file path your assistant can read. Ask only for missing facts that change the result. If they ask you to start with what they have, complete the parts you can and mark the gaps. 3. **Do the job.** Follow the skill below with the facts and tools you have. Mark each gap with `MISSING:` where it belongs and never invent a fact to fill it. ### After this When you've handed it back, suggest what they could do next in one short question. It's a suggestion: if they're done, that's fine. Offer these, and say they can type their own: - The [Student confidence task planner](https://useaiblocks.com/skills/confidence-building-task-ladder). It takes the plan. If they pick one and that skill is added here, carry straight on with what you just made. If not, give the link and say what to bring.