[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74GD0Y9JR8GNDVRVFMP9SVG":3,"skill-same:01M74GD0Y9JR8GNDVRVFMP9SVG":44},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M74GD0Y9JR8GNDVRVFMP9SVG","code-walkthrough",null,"Explain a piece of code in execution order — entry point, branches, side effects, the surprising line; cite file:line; not a line-by-line rewrite.","MohammadBafkar\u002Fpolymath","MohammadBafkar","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F34940462?v=4","01M74G540TQFZWK6KVAPKFVGNR","Mohammad Bafkar","01M74G541HG19QP9V5DQCJVKYE",0,"MIT","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-learning\u002Fskills\u002Fcode-walkthrough\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: code-walkthrough\ndescription: Explain a piece of code in execution order — entry point, branches, side effects, the surprising line; cite file:line; not a line-by-line rewrite.\n---\n\n# code-walkthrough\n\n> Trace one execution path through real code. Output is a guided narrative the reader can follow with the source open beside them.\n\n**Mode:** analytical — judgment inside a fixed frame. Keep the output shape; every verdict cites its evidence; unknowns are marked `[TBD]` or `[VERIFY]`, never filled in.\n\n## When to use\n\n- A new contributor needs to understand how X works.\n- A code-review reviewer wants the diff narrated.\n- A workflow needs onboarding-ready text.\n\n## Inputs\n\n- Path\u002Fglob into the code (required).\n- Audience tier (per the `explain` skill).\n- Optional: a specific entry point (a function, a route, a test).\n\n## Procedure\n\n1. **Find the entry point**. The CLI command, the HTTP route, the test that exercises the path.\n2. **Trace execution in order**. Each step: file:line → what happens there → why (if non-obvious).\n3. **Call out side effects** — when the path touches the DB, the filesystem, the network, a global, a cache. These are where bugs live.\n4. **Find the surprising line**. Every walkthrough has one. Name it and explain why it's there (often a workaround for something).\n5. **Skip the obvious**. Loops over arrays don't need narration. Custom error handling does.\n6. **Audience tier**: for less-experienced audiences, expand prerequisites inline; for peer audiences, link them.\n\n## Output\n\n```text\nCode walkthrough: \u003Centry point> — audience: \u003Ctier>\n\nStep 1: [file.py:42] receives the request\n  Inputs: …\n  What it does: …\n\nStep 2: [file.py:78] validates the auth\n  Why this not in middleware: \u003Creason, often a quirk>\n\nStep 3: [util.py:15] formats the output\n  Side effect: writes to \u003Ccache key>\n\nSurprising line:\n  [file.py:103] — `if x is None or x == \"\":` looks redundant; it's there\n  because legacy callers in pre-1.0 send \"\" while new callers send None.\n\nWhere the bugs tend to live:\n  - \u003Cfile:line> — race between cache write and read.\n  - \u003Cfile:line> — silent fallthrough when auth missing.\n```\n\n## Quality bar\n\n- Every step cites file:line.\n- Side effects called out specifically (cache key, DB table, file path).\n- One \"surprising line\" called out per walkthrough.\n- Doesn't narrate obvious code; skips to the interesting parts.\n\n## Anti-patterns to avoid\n\n- \"Line-by-line\" narration of the whole file. Skim what's obvious.\n- No file:line citations. The reader can't follow.\n- Hiding the surprising line. That's the one the reader most needs to know about.\n- Walkthrough that tries to cover three execution paths at once.\n","# code-walkthrough\n\n> Trace one execution path through real code. Output is a guided narrative the reader can follow with the source open beside them.\n\n**Mode:** analytical — judgment inside a fixed frame. Keep the output shape; every verdict cites its evidence; unknowns are marked `[TBD]` or `[VERIFY]`, never filled in.\n\n## When to use\n\n- A new contributor needs to understand how X works.\n- A code-review reviewer wants the diff narrated.\n- A workflow needs onboarding-ready text.\n\n## Inputs\n\n- Path\u002Fglob into the code (required).\n- Audience tier (per the `explain` skill).\n- Optional: a specific entry point (a function, a route, a test).\n\n## Procedure\n\n1. **Find the entry point**. The CLI command, the HTTP route, the test that exercises the path.\n2. **Trace execution in order**. Each step: file:line → what happens there → why (if non-obvious).\n3. **Call out side effects** — when the path touches the DB, the filesystem, the network, a global, a cache. These are where bugs live.\n4. **Find the surprising line**. Every walkthrough has one. Name it and explain why it's there (often a workaround for something).\n5. **Skip the obvious**. Loops over arrays don't need narration. Custom error handling does.\n6. **Audience tier**: for less-experienced audiences, expand prerequisites inline; for peer audiences, link them.\n\n## Output\n\n```text\nCode walkthrough: \u003Centry point> — audience: \u003Ctier>\n\nStep 1: [file.py:42] receives the request\n  Inputs: …\n  What it does: …\n\nStep 2: [file.py:78] validates the auth\n  Why this not in middleware: \u003Creason, often a quirk>\n\nStep 3: [util.py:15] formats the output\n  Side effect: writes to \u003Ccache key>\n\nSurprising line:\n  [file.py:103] — `if x is None or x == \"\":` looks redundant; it's there\n  because legacy callers in pre-1.0 send \"\" while new callers send None.\n\nWhere the bugs tend to live:\n  - \u003Cfile:line> — race between cache write and read.\n  - \u003Cfile:line> — silent fallthrough when auth missing.\n```\n\n## Quality bar\n\n- Every step cites file:line.\n- Side effects called out specifically (cache key, DB table, file path).\n- One \"surprising line\" called out per walkthrough.\n- Doesn't narrate obvious code; skips to the interesting parts.\n\n## Anti-patterns to avoid\n\n- \"Line-by-line\" narration of the whole file. Skim what's obvious.\n- No file:line citations. The reader can't follow.\n- Hiding the surprising line. That's the one the reader most needs to know about.\n- Walkthrough that tries to cover three execution paths at once.\n",{"name":5,"description":7},"main","23f6e21841a39580c9da2b5ec941f39dda17cd86","plugins\u002Fpolymath-learning\u002Fskills\u002Fcode-walkthrough","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath","https:\u002F\u002Fgithub.com\u002FMohammadBafkar","2026-10-29 18:34:59",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add MohammadBafkar\u002Fpolymath --skill code-walkthrough",{"tool":36,"command":37},"bunx","bunx skills add MohammadBafkar\u002Fpolymath --skill code-walkthrough",{"tool":39,"command":40},"pnpm","pnpm dlx skills add MohammadBafkar\u002Fpolymath --skill code-walkthrough","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-learning\u002Fskills\u002Fcode-walkthrough\u002FSKILL.md",true,[],[45,52,59,66,73,80],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":19},"01M74GN87EBRHM9N87M7AP1HDD","runbook","Write or refresh an operational runbook for an alert\u002Fsymptom; structured as TL;DR + Pre-checks + Steps + Verification + Rollback + Escalation.","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-writing\u002Fskills\u002Frunbook\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M74GN5GPKEC1JEKP2DFQNEQJ","rfc","Draft a lightweight design RFC to docs\u002Frfcs\u002F\u003Cslug>.md; Summary, Motivation, Detailed design, Drawbacks, Alternatives, Unresolved questions. A proposal to debate, not a recorded decision (adr).","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-writing\u002Fskills\u002Frfc\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M74GN2F4CWPMV4X09TG4E304","editorial-pass","Review and tighten prose in a Markdown artifact for a target tone (terse, formal, friendly) without dropping information; preserve quotations and load-bearing constraints.","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-writing\u002Fskills\u002Feditorial-pass\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M74GMZWGYMZ37C4DYGT6P23G","architecture-review-facilitation","Run an architecture review as a process — entry criteria, reviewer checklist, decision log, and follow-up actions — pairing the design artifact with a red-team pass.","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-writing\u002Fskills\u002Farchitecture-review-facilitation\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M74GMXVX0YX3ETDXS527XDGM","architecture-doc","Write a C4-style architecture document; System Context + Containers (+ Components when interesting) with mermaid diagrams. Describes structure, not a decision (adr) or proposal (rfc).","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-writing\u002Fskills\u002Farchitecture-doc\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M74GMVG1WSMCK066S3KE6V5K","adr","Write an Architecture Decision Record (Michael Nygard format) to docs\u002Fadrs\u002FNNNN-\u003Cslug>.md; frontmatter validated by the ADR artifact schema. Records a made decision, not a proposal to debate (rfc).","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-writing\u002Fskills\u002Fadr\u002FSKILL.md",[],[]]