Skip to content
cccskills
FreePublished on GitHub

learn-quiz

Check your understanding of code you recently wrote, edited, or accepted from AI. Answer questions one at a time, receive explanations, and finish with a score, strengths, review topics, and suggested practice.

OriginalShow the original description

Test understanding of recently written or accepted code

See how to install

Good for

  • Checking understanding of code accepted from AI
  • Reviewing error handling in recent code
  • Explaining trade-offs through harder questions
  • Identifying topics to revisit after coding

Files included (1)

  • SKILL.md3.7 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Quiz me

Test understanding of recently written or accepted code.

Usage

/learn:quiz                     # Quiz on last code worked with
/learn:quiz error handling      # Focus on specific aspect
/learn:quiz --hard              # More challenging questions

Instructions

  1. Identify the last code I worked with (wrote, edited, or accepted from AI)
  2. Generate 3-5 questions that test understanding at different levels:
    • Recall: What does this code do?
    • Understanding: Why was this approach chosen?
    • Application: What would happen if X changed?
    • Analysis: What are the trade-offs of this approach?
    • Synthesis: How would you extend this?
  3. Present questions one at a time
  4. Wait for my answer before revealing the correct response
  5. Provide explanations with each answer, not just "correct/incorrect"

Question types

Level 1: Recall

  • "What does the function X return?"
  • "What parameters does Y accept?"
  • "What happens when Z is called?"

Level 2: Understanding

  • "Why do we use X instead of Y here?"
  • "What problem does this pattern solve?"
  • "Why is this line necessary?"

Level 3: Application

  • "What would happen if we removed line X?"
  • "How would you add feature Y to this code?"
  • "What would break if input Z was provided?"

Level 4: Analysis

  • "What are the performance implications of this approach?"
  • "What edge cases might cause issues?"
  • "How does this compare to alternative X?"

Level 5: Synthesis

  • "How would you refactor this for better testability?"
  • "What would need to change to support X?"
  • "Design an extension that adds Y"

Focus areas

When focus is specified (e.g., /learn:quiz error handling), prioritize questions about:

FocusQuestion Themes
error handlingTry/catch, error types, recovery strategies
performanceBig-O, optimization, bottlenecks
securityInput validation, XSS, injection
testingTest cases, edge cases, mocking
architecturePatterns, separation of concerns, SOLID
typesTypeScript types, inference, generics

Difficulty modes

Default

  • 3 questions
  • Mix of Level 1-3
  • Focus on understanding current code

--hard

  • 5 questions
  • Levels 3-5
  • Include hypothetical modifications
  • Ask about trade-offs and alternatives

Response format

For each question:

## Question 1 of 3

[Question text]

What's your answer?

---
(After user responds)

### Feedback

[Whether correct and why]

**Key insight**: [The concept this tests]

**Related concept**: [Something to explore further]

Ready for the next question?

After quiz complete

Summarize:

  • Score: X/Y correct
  • Strengths: [Topics understood well]
  • Review needed: [Topics to revisit]
  • Suggested practice: [Specific exercise]

Example session

User: /learn:quiz

Claude: Looking at your last code - the useEffect hook for data fetching.

## Question 1 of 3

In your useEffect, you have an empty dependency array [].
What does this mean for when the effect runs?

User: It runs only once when the component mounts

Claude: ### Feedback
Correct! An empty dependency array means the effect runs only on mount
(and cleanup on unmount).

**Key insight**: The dependency array controls WHEN effects re-run.

**Related concept**: What happens with no array vs. [someValue]?

Ready for Question 2?

Tips for users

  1. Be honest: Wrong answers are learning opportunities
  2. Explain your reasoning: Helps identify gaps even in correct answers
  3. Ask follow-ups: If feedback is unclear, dig deeper
  4. Track weak areas: Note topics that need more practice

$ARGUMENTS

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Evaluate Claude Code agents, skills, and commands with weighted quality criteria. Get scores, readiness grades, template comparisons, and practical improvement suggestions in Markdown or JSON reports to guide reviews before release.

  • Review skills before release
  • Compare agent definitions with reference templates
  • Quickly check critical quality criteria
FlorianBruniaux/claude-code-ultimate-guide6.2KUpdated Oct 20, 2026

audit-codebase

FreeSummary

Assess a codebase across seven areas, including exposed credentials, security, dependencies, structure, and tests. Receive category scores, findings tied to file locations, and a prioritized improvement plan with smaller tasks that can be completed quickly.

  • Assessing the overall health of an inherited project
  • Reviewing exposed credentials and security risks
  • Identifying dependency and test coverage gaps
FlorianBruniaux/claude-code-ultimate-guide6.2KUpdated Oct 20, 2026

autoresearch

FreeSummary

Measure code patterns such as casts to any or disabled lint rules, then run repeated, targeted edits. Keep changes that improve the chosen metric, revert unsuccessful changes, and track results for each improvement loop.

  • Finding code patterns to prioritize for cleanup
  • Preparing measurement files for an improvement loop
  • Repeating targeted edits to reduce casts to any
FlorianBruniaux/claude-code-ultimate-guide6.2KUpdated Oct 20, 2026

best-of-n

FreeSummary

Generate several separate solutions, compare them against criteria fixed in advance, and verify the selected result through executable checks or an independent reviewer. Keep a proof log documenting candidates, evidence, failures, and remaining limits.

  • Comparing implementation options before choosing one
  • Verifying a solution when a wrong choice would be costly
  • Keeping evaluation evidence for delivery or audit
FlorianBruniaux/claude-code-ultimate-guide6.2KUpdated Oct 20, 2026

canary

FreeSummary

Monitor a live application after deployment and compare it with a saved baseline, a record of its earlier state. Check page responses, loading times, and new errors, flag persistent changes, and produce a per-page health report.

  • Recording a healthy baseline before deployment
  • Monitoring production immediately after deployment
  • Checking key pages for slower responses or failures
FlorianBruniaux/claude-code-ultimate-guide6.2KUpdated Oct 20, 2026

catchup

FreeSummary

Rebuild project context after clearing a conversation or returning to work. Review recent Git history, uncommitted changes, and TODO markers to get a structured summary of project status and suggested next steps.

  • Restoring project context after /clear
  • Reviewing recent changes after a long break
  • Checking unfinished work before choosing the next task
FlorianBruniaux/claude-code-ultimate-guide6.2KUpdated Oct 20, 2026

See all skills by FlorianBruniaux

Report a problem with this skill