本文へ移動
cccskills
無料GitHub で公開

code-explainer

Explain what a piece of code does in plain English, at the depth the reader needs. Use when asked to explain code, walk through a function, understand an unfamiliar snippet, or onboard to a file. Produces a one-line summary, a step-by-step walkthrough, the non-obvious parts called out, and any bugs or smells spotted along the way.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md2.3 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Code Explainer Skill

Make unfamiliar code understandable — fast — without dumbing it down.

Working from a brief

Infer the language and intent from the code itself; label assumptions (assumed — confirm). Always produce a complete explanation even from a fragment. Match depth to the apparent level of the question.

Input

Ask for these if not provided:

  • The code — the snippet or file to explain (paste it, or point at the path)
  • The language or runtime — if it is not obvious from the code
  • The reader — who this is for and how much they already know
  • What they are trying to understand — the bug, the review, the handover; infer the rest

Output Structure

In one line

What this code does, in a single sentence a busy reader can repeat.

Step by step

A walkthrough of the logic in order — group by block/function. Explain why, not just what, for anything non-trivial. Reference line ranges where helpful.

Worth knowing

The non-obvious bits: clever tricks, gotchas, side effects, complexity, dependencies, or assumptions the code makes.

Anything off?

Bugs, edge cases, or smells you noticed while reading — with the fix. (If it's clean, say so.)

Quality Checks

  • The one-line summary stands alone
  • The walkthrough explains why, not just restating the code in words
  • Non-obvious behaviour (side effects, complexity, edge cases) is surfaced
  • Any bug/smell spotted is flagged with a fix

Anti-Patterns

  • Do not narrate line-by-line in English ("this line sets x to 5") — explain intent and structure
  • Do not skip the gotchas — the value is in the non-obvious parts
  • Do not assume expert level if the question reads like a beginner's (or vice-versa)
  • Do not ignore a bug you can see just because you weren't asked to review it

Example Trigger Phrases

  • "Explain code."
  • "Walk through a function."
  • "Understand an unfamiliar snippet."
  • "Onboard to a file."

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Decode a 401k or workplace retirement plan — the real cost of its funds, the match's fine print, vesting math, and the plan features worth using or avoiding. Use when someone asks 'is my 401k any good', 'decode my 401k plan', 'which funds should I look at', or 'what fees am I paying'. Produces a fee decode in dollars-over-time, match and vesting math, a fund-lineup triage by cost, and the questions for HR or the plan administrator.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Analyse a finished A/B test and write the readout — the result, whether it's statistically and practically significant, what it means, and the ship/no-ship call. Use when asked to analyse experiment results, write an A/B test readout, interpret test data, or decide whether to ship a variant. Produces a clear verdict with the lift and confidence, segment cuts, the risks (peeking, novelty, sample), and a recommendation. Distinct from planning a test — this reads results.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Build or tailor an academic CV for faculty, postdoc, research or fellowship applications: publications, grants, teaching, supervision and service in the order the field expects, with consistent citations. Use when asked to write my academic CV, update my CV for a lectureship, tenure-track or postdoc application, format my publications list, or adapt my academic CV for an industry research role. Produces the full academic CV, a field-appropriate section order, a clean publications list in one citation style, and a two-page summary version when asked.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

mohitagw15856 のスキルをすべて見る

このスキルの問題を報告する