agentleFS
sandochesandoche/agentic-code-unpacked/skills/walkthrough/SKILL.md

walkthrough

Skill1 starsChanged 4 days agoMITView on GitHub

Create a source-linked HTML code tour for a PR, branch, codebase, or selected code; optionally export a silent video with captions.

34 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use chips, redo and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • udecodeSkill

    chips

    Run the project's suggested-task ledger, the chips. /chips alone brings this session's open tasks up to date: it applies what the ledger helper says, settles stale and split tasks, cards what can start and reports the board, and /chips all also takes the ship-list tasks and the ones no live session owns, and merges duplicate tasks across the board. Use for /chips, /chips offer, start or drop, \"what chips are open\", \"suggest a task for X\", \"update the chips\", \"clean up the chips\", \"which chips are stale\", \"is this chip still worth doing\", \"merge duplicate chips\", at the last hand-back of a run that offered a task, and whenever pstack would file a tracked issue, a follow-up, a reflect Backlog item or an out-of-band PR.

    Also in 3 projects that use this

  • Scylla23Skill

    redo

    Re-run the last routed task one model tier up (haiku → sonnet → opus → fable). User-invoked escalation when the previous result missed. Pass --dry-run to preview without running.

    Also in 3 projects that use this

  • Aetheria-Labs1Skill

    plan-page

    Plan one storefront page from strategy through final copy, section order, proof, offers, template direction, responsive layout, and production asset requirements. Stops at an approved execution-ready specification.

    Also in 3 projects that use this

  • SocialKit-APISkill

    video-transcripts

    Extract transcripts from social videos through SocialKit across YouTube, TikTok, Instagram, Facebook, X/Twitter, LinkedIn, and direct video file URLs. Use when the user asks to transcribe, get captions or subtitles, pull the spoken text, or read what a video says, including one video or many at once. Returns full text plus timestamped segments. Not for posting, private accounts, or unrelated website scraping.

    Also in 3 projects that use this

  • MicrosoftSkill

    cleanup

    Also in 3 projects that use this

  • BlockSkill

    test-audit

    Invoke whenever writing, changing, reviewing, or sweeping tests in buzz-app. Authoring gate for new tests plus audit workflow for low-value, implementation-coupled, or duplicative tests and the test-only production seams they demand.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 33 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the bundled source and delivery guide, then capture the target through this skill's runtime.

    line 24
  2. Distinctive:

    Follow the walkthrough workflow and content schema.

    line 25

“Common” is measured: kept by at least 6 in 10 of the 33 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Walkthrough

Explain purpose, before/after behavior, review priorities, and relevant source through an offline code tour. Use chapters for meaningful deep dives.

Use

/walkthrough pr https://github.com/owner/repo/pull/123 --draft
/walkthrough branch feature/login --base main
/walkthrough video codebase

Accept natural-language requests too. Interpret a PR URL as pr, named branches as branch, selected files or pasted code as a named docs target, and the whole current repository as codebase. Honor the harness's native invocation syntax.

Generate

  1. Read the bundled source and delivery guide, then capture the target through this skill's runtime. Resolve paths from this installed skill folder, independently of the current working directory.
  2. Follow the walkthrough workflow and content schema. Read source before authoring explanations; preserve evidence, source limitations, and existing artifact behavior.
  3. Generate and inspect the HTML. For video requests, reuse the same content and export the silent MP4 plus captions. Return usable artifact paths and a short explanation of any missing capabilities.

Dependencies and Chromium are set up automatically when needed. Video requires FFmpeg. The user should not need to run renderer scripts or author JSON. Use available source and browser tools; fall back to direct source when graph tools are unavailable. PR comments require requested live delivery; --draft always stays local.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.