Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →jamestorrevillas/code-explanation
Use this skill when writing code comments, explaining code decisions, documenting the "why" behind implementation choices, or narrating technical reasoning in PRs or architecture docs. Trigger on keywords: explain this code, why did you write it this way, add comments, document this, write inline comments, explain my decision.
Passed 22 of 24 test cases with the skill, and 20 of 24 without it.
2 fixed20 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
We recently decided to switch our primary database from MongoDB to PostgreSQL for better relational integrity across user accounts. Please draft an Architecture Decision Record documenting this switch for our engineering team's documentation repository.
| Checked | Without skill | With skill |
|---|---|---|
| The ADR includes a 'Reasoning' section. | Missed | Passed |
| The ADR includes a 'Trade-offs' section. | Missed | Passed |
| The ADR includes a 'Consequences' section. | Passed | Passed |
The instructions your model reads when the skill loads.
Comments explain WHY. Code explains WHAT.
If you need a comment to explain what the code does, the code should be cleaner. If you need a comment to explain why it's done this way — write that comment.
| Level | Where | Explains |
|---|---|---|
| Inline comment | Next to specific line | Non-obvious logic or gotcha |
| Function docstring | Top of function | What it does, parameters, returns, side effects |
| Module header | Top of file | What this module is responsible for |
| Architecture note | README / ADR | Why this approach was chosen over alternatives |
// Using exponential backoff here because the payment API
// has a 429 rate limit that triggers on burst traffic
await retryWithBackoff(() => paymentAPI.charge(amount))
// Intentionally not validating here — validation happens
// upstream in the middleware layer (see auth.middleware.ts)
const user = req.user
// This looks backwards but the API returns results
// in reverse chronological order — newest = index 0
const latest = results[0]
test cases passed, vs 20 / 24 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.