본문으로 건너뛰기
cccskills
무료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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

Test understanding of recently written or accepted code

설치 방법 보기

이럴 때 유용합니다

  • 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

포함된 파일(1)

  • SKILL.md3.7 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

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

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

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.2천2026년 10월 20일 업데이트

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.2천2026년 10월 20일 업데이트

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.2천2026년 10월 20일 업데이트

best-of-n

무료

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.2천2026년 10월 20일 업데이트

canary

무료

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.2천2026년 10월 20일 업데이트

catchup

무료

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.2천2026년 10월 20일 업데이트

FlorianBruniaux의 스킬 모두 보기

이 스킬의 문제 신고