Agent skill

Workthrough

Automatically document all development work and code modifications in a structured workthrough format.

MITAuto-check passedDevelopment

Install Workthrough

skills CLI

$ npx skills add bear2u/my-skills --skill workthrough -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install bear2u/my-skills workthrough --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/bear2u/my-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/workthrough .claude/skills/workthrough && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "workthrough" agent skill from https://github.com/bear2u/my-skills/tree/master/skills/workthrough into .claude/skills/workthrough/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workthrough", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/bear2u/my-skills/tree/master/skills/workthrough

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add bear2u/my-skills --skill workthrough -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install bear2u/my-skills workthrough --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/bear2u/my-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/workthrough .agents/skills/workthrough && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "workthrough" agent skill from https://github.com/bear2u/my-skills/tree/master/skills/workthrough into .agents/skills/workthrough/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workthrough", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add bear2u/my-skills --skill workthrough -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install bear2u/my-skills workthrough --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/bear2u/my-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/workthrough .cursor/skills/workthrough && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "workthrough" agent skill from https://github.com/bear2u/my-skills/tree/master/skills/workthrough into .cursor/skills/workthrough/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workthrough", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/bear2u/my-skills.git --path skills/workthrough

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add bear2u/my-skills --skill workthrough -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install bear2u/my-skills workthrough --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/bear2u/my-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/workthrough .gemini/skills/workthrough && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "workthrough" agent skill from https://github.com/bear2u/my-skills/tree/master/skills/workthrough into .gemini/skills/workthrough/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workthrough", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install bear2u/my-skills workthrough

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add bear2u/my-skills --skill workthrough -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/bear2u/my-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/workthrough .github/skills/workthrough && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "workthrough" agent skill from https://github.com/bear2u/my-skills/tree/master/skills/workthrough into .github/skills/workthrough/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workthrough", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add bear2u/my-skills --skill workthrough -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install bear2u/my-skills workthrough --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/bear2u/my-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/workthrough .opencode/skills/workthrough && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "workthrough" agent skill from https://github.com/bear2u/my-skills/tree/master/skills/workthrough into .opencode/skills/workthrough/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workthrough", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: workthrough
GitHub stars: 933
Token cost: ~1.3k tokens
SKILL.md length: 260 words
Files: 6
Skills in repo: 16
Repo updated: Jun 22, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Automatically document all development work and code modifications in a structured workthrough format.

Works in 5 steps: Capture Complete Context → Document All Changes Systematically → Show Code Examples → …
Tasks that involve Debugging
SKILL.md covers When to Use This Skill, Documentation Structure, Implementation Guidelines and Document Organization, plus 3 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Workthrough is an agent skill from bear2u/my-skills. Automatically document all development work and code modifications in a structured workthrough format. Use this skill after completing any development task, bug fix, feature implementation, or code refactoring to create comprehensive documentation.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files (for example `EXAMPLES.md`, `QUICKSTART.md` and `README.md`).

It sits in Development, covering Debugging and Refactoring. The repository describes itself as: 자주 사용하는 스킬들을 모은 나의 클로드 스킬들입니다. The licence is MIT.

When your agent uses it

Tasks that involve Debugging
Tasks that involve Refactoring

Example prompts

“/workthrough”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

Capture Complete Context
Document All Changes Systematically
Show Code Examples
Include Verification
Use Clear Formatting

What it can do on your machine

Read from SKILL.md and the folder at commit 8ed5784. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash, language and markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Workthrough loads about 1.3k tokens when it runs. Until then it costs about 65 tokens; SKILL.md has 260 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~65
When it runs · the whole SKILL.md, loaded when a task matches: ~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from bear2u/my-skills at commit 8ed5784, republished under its MIT licence (© bear2u). 260 words, ~1,303 tokens.

Download SKILL.mdSave it as .claude/skills/workthrough/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.

name: workthrough
description: Automatically document all development work and code modifications in a structured workthrough format. Use this skill after completing any development task, bug fix, feature implementation, or code refactoring to create comprehensive documentation.
license: MIT

This skill automatically generates detailed workthrough documentation for all development work, capturing the context, changes made, and verification results in a clear, structured format.

When to Use This Skill

Use this skill automatically after:

Implementing new features or functionality
Fixing bugs or errors
Refactoring code
Making configuration changes
Updating dependencies
Resolving build/compilation issues
Any significant code modifications

Documentation Structure

The workthrough documentation follows this structure:

Title: Clear, descriptive title of the work completed
Overview: Brief summary of what was accomplished and why
Changes Made: Detailed breakdown of all modifications
Code Examples: Key code snippets showing important changes
Verification Results: Build/test results confirming success

Implementation Guidelines

When generating workthrough documentation:

1. Capture Complete Context

What problem was being solved?
What errors or issues existed before?
What approach was taken?
Why were specific decisions made?

2. Document All Changes Systematically

List each file modified with full paths
Describe what changed in each file
Include before/after code snippets for significant changes
Note any dependencies added or removed
Document configuration updates

3. Show Code Examples

Use clear, well-formatted code blocks:

language

// file: src/path/to/file.tsx
<div className="example">
  {/* Show relevant code changes */}
</div>

4. Include Verification

Build output showing success
Test results
Error messages (if any remain)
Exit codes
Screenshots (if relevant)

5. Use Clear Formatting

Use markdown headers (##, ###)
Use bullet points and numbered lists
Use code blocks with syntax highlighting
Use blockquotes for output/logs
Keep paragraphs concise

Document Organization

Save workthrough documents with this naming convention:

workthrough/YYYY-MM-DD-brief-description.md

Or organize by feature/project:

workthrough/feature-name/implementation.md
workthrough/bugfix/issue-123.md

Example Workthrough Structure

markdown

# [Clear Descriptive Title]

## Overview
Brief 2-3 sentence summary of what was accomplished.

## Context
- Why was this work needed?
- What was the initial problem/requirement?
- Any relevant background information

## Changes Made

### 1. [First Major Change]
- Specific modification 1
- Specific modification 2
- File: `path/to/file.tsx`

### 2. [Second Major Change]
- Specific modification 1
- File: `path/to/another-file.ts`

### 3. [Additional Changes]
- Dependencies added: `package-name@version`
- Configuration updates: `config-file.json`

## Code Examples

### [Feature/Fix Name]
```typescript
// src/path/to/file.tsx
const example = () => {
  // Show the key code changes
}

Verification Results

Build Verification

bash

> build command output
✓ Compiled successfully
Exit code: 0

Test Results

bash

> test command output
All tests passed

Next Steps

Any follow-up tasks needed
Known limitations or future improvements


## Automation Instructions

After completing ANY development work:

1. **Gather Information**
   - Review all files modified during the session
   - Collect build/test output
   - Identify the main objective that was accomplished

2. **Create Document**
   - Generate workthrough document in `workthrough/` directory
   - Use timestamp or descriptive filename
   - Follow the structure guidelines above

3. **Be Comprehensive**
   - Include all relevant details
   - Don't assume future readers have context
   - Document decisions and reasoning
   - Show concrete examples

4. **Verify Completeness**
   - Confirm all changes are documented
   - Include verification results
   - Add any relevant warnings or notes

## Quality Standards

Good workthrough documentation should:
- Be readable by other developers
- Provide enough detail to understand changes
- Include verification that changes work
- Serve as a reference for similar future work
- Capture important decisions and context

Avoid:
- Overly verbose descriptions
- Unnecessary technical jargon
- Missing verification steps
- Vague or unclear explanations
- Incomplete code examples

## Output Location

Unless specified otherwise, save workthrough documents to:

workthrough/YYYY-MM-DD-brief-description.md


Create the `workthrough/` directory if it doesn't exist.

## Integration with Workflow

This skill should be triggered automatically at the end of development sessions. The documentation serves as:
- A development log/journal
- Knowledge base for the project
- Onboarding material for new developers
- Reference for debugging similar issues
- Record of architectural decisions

Remember: Good documentation is a gift to your future self and your team.

Files

SKILL.md and 5 other files in skills/workthrough of bear2u/my-skills.

SKILL.md
EXAMPLES.md
LICENSE.txt
QUICKSTART.md
README.md
TEMPLATE.md

Open the folder on GitHubat commit 8ed5784

Compare with similar skills

Workthrough next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Workthrough compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Workthrough this skillbear2u/my-skills	933	—	~1.3k	Automated safety check: Pass	MIT	3 mo ago
Code Review Graph Navigatorhandsontable/handsontable	22k	—	~939	Automated safety check: Pass	Custom licence	today
Analyze Projectlllllllama/RigorPilot-Skills	497	1 repos	~519	Automated safety check: Pass	MIT	16 days ago
Andrej Karpathy Skillduolahypercho/andrej-karpathy-skills	249	—	~793	Automated safety check: Pass	MIT	4 mo ago
Verdaccio Change Implementationverdaccio/verdaccio	18k	—	~1.3k	Automated safety check: Pass	MIT	yesterday
RoamCranot/roam-code	517	—	~2.4k	Automated safety check: Pass	Apache-2.0	6 days ago

Similar skills

Code Review Graph Navigator
handsontable/handsontable
Queries a pre-built, Tree-sitter-based code graph of the whole monorepo instead of grepping call chains, for exploring, debugging, refactoring or reviewing code.
22k GitHub stars~939 tokensUpdated today
DevelopmentAuto-check passed
Analyze Project
lllllllama/RigorPilot-Skills
Rigor Analyze / Rigor Audit read-only skill for deep learning research repositories.
497 GitHub starsUsed in 1 repo~519 tokens
DevelopmentAuto-check passed
Andrej Karpathy Skill
duolahypercho/andrej-karpathy-skills
Apply Andrej Karpathy-inspired coding-agent guidelines in Codex.
249 GitHub stars~793 tokensUpdated 4 mo ago
DevelopmentAuto-check passed
Verdaccio Change Implementation
verdaccio/verdaccio
A workflow for implementing a Verdaccio bug fix, feature or refactor: pick the release lines, check existing options, edit the owning layer, test and add a changeset.
18k GitHub stars~1.3k tokensUpdated yesterday
DevelopmentAuto-check passed
Roam
Cranot/roam-code
Codebase comprehension via roam-code CLI. An agent skill from Cranot/roam-code.
517 GitHub stars~2.4k tokensUpdated 6 days ago
DevelopmentAuto-check passed
Odoo Workflow
unclecatvn/agent-skills
Mandatory pre-code gate and definition-of-done for ANY Odoo change (add field, override method, inherit view/xpath, OWL/JS patch, wizard, cron, controller, report, security, migration, bug fix…
143 GitHub stars~4.7k tokensUpdated 15 days ago
DevelopmentAuto-check passed

Questions about Workthrough

What does Workthrough do?

Automatically document all development work and code modifications in a structured workthrough format. Workthrough is an agent skill from bear2u/my-skills. Automatically document all development work and code modifications in a structured workthrough format.

When should I use Workthrough?

Workthrough fits situations like: tasks that involve Debugging; tasks that involve Refactoring.

How do I install Workthrough in Claude Code?

Run `npx skills add bear2u/my-skills --skill workthrough -a claude-code`. Or copy the skill folder (skills/workthrough in bear2u/my-skills) into .claude/skills/workthrough in your project. Claude Code loads it when a task matches its description.

How do I install Workthrough in Codex?

Run `npx skills add bear2u/my-skills --skill workthrough -a codex`. Or copy the skill folder (skills/workthrough in bear2u/my-skills) into .agents/skills/workthrough in your project. Codex loads it when a task matches its description.

Can I use Workthrough in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add bear2u/my-skills --skill workthrough -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/workthrough, .gemini/skills/workthrough, .github/skills/workthrough and .opencode/skills/workthrough in your project.

What does Workthrough need to run?

SKILL.md names no scripts, command-line tools or credentials: Workthrough is instructions for the agent only.

Does Workthrough access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Workthrough safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Workthrough use?

Workthrough is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Workthrough use?

About 1.3k tokens (SKILL.md is roughly 5.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Workthrough?

Skills that share tags, products or a category with Workthrough: Code Review Graph Navigator (handsontable/handsontable, 22k stars), Analyze Project (lllllllama/RigorPilot-Skills, 497 stars), Andrej Karpathy Skill (duolahypercho/andrej-karpathy-skills, 249 stars) and Verdaccio Change Implementation (verdaccio/verdaccio, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Workthrough?

bear2u (a GitHub user) maintains it in bear2u/my-skills, which has 933 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on June 22, 2026.

Source: bear2u/my-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Workthrough

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

When to Use This Skill

Documentation Structure

Implementation Guidelines

1. Capture Complete Context

2. Document All Changes Systematically

3. Show Code Examples

4. Include Verification

5. Use Clear Formatting

Document Organization

Example Workthrough Structure

Verification Results

Build Verification

Test Results

Next Steps

Files

Compare with similar skills

Similar skills

More from bear2u/my-skills

Related

Questions about Workthrough