home / skills / bear2u / my-skills / workthrough-v2

workthrough-v2 skill

safe

This skill automatically summarizes completed development work in Korean and proposes future improvements with concise, actionable notes.

npx playbooks add skill bear2u/my-skills --skill workthrough-v2

Review the files below or copy the command above to add this skill to your agents.

Files (6)

SKILL.md

1.6 KB

---
name: workthrough
description: "Use this skill proactively and automatically after completing ANY development work. AI agent summarizes: what was done, what was changed/improved, and suggests future additions/improvements - all concisely in Korean."
license: MIT
---

**AI 에이전트가 개발 작업을 간략하게 요약하고 추가/개선 제안을 작성합니다.**

## ⚡ 핵심

1. **자동 실행**: 개발 완료 시 자동 실행
2. **간략 요약**: AI가 작업 내용 간단히 정리
3. **제안 포함**: 추가/개선할 내용 제안
4. **한국어**: 모든 문서 한국어
5. **위치**: `<project-root>/workthrough/YYYY-MM-DD_HH_MM_description.md`

## 📝 문서 내용 (간결하게!)

```markdown
# [작업 제목]

## 개요
2-3문장으로 무엇을 했는지 요약

## 주요 변경사항
- 개발한 것: XXX 기능 추가
- 수정한 것: YYY 버그 수정
- 개선한 것: ZZZ 성능 향상

## 핵심 코드 (필요시만)
```typescript
// 핵심 로직만 간단히
const key = value
```

## 결과
- ✅ 빌드 성공
- ✅ 테스트 통과

## 다음 단계
- 다음에 구현해야 할 기능
- 다음에 수정해야 할 부분
```

## 🚀 VitePress 처리

### 첫 실행시 (workthrough 폴더 없을 때)
1. VitePress 초기 설정
2. `pnpm install && pnpm dev` 테스트

### 이후 실행시 (workthrough 폴더 있을 때)
1. 새 워크스루 문서만 생성
2. `pnpm build`로 빌드 확인만

## ⚠️ 중요

- **간결**: 긴 설명 ❌
- **핵심만**: 중요 코드만 발췌
- **요약**: 무엇을 개발/수정/개선했는지
- **다음 단계**: 다음에 해야 할 작업 제안

끝.

Overview

This skill automatically runs after any development work and produces a concise walkthrough document in Korean. It summarizes what was done, what changed or improved, and suggests next steps, saving the file under <project-root>/workthrough/YYYY-MM-DD_HH_MM_description.md. The output is intentionally brief and focused on actionable items.

How this skill works

After detecting completion of development tasks (commit, build success, or developer signal), the agent collects key metadata: changes, added features, bug fixes, and test/build results. It generates a short markdown document in Korean with sections for overview, major changes, essential code snippets (if needed), results, and next steps. On first run it initializes VitePress and tests a dev run; on subsequent runs it only creates new walkthrough files and validates build when required.

When to use it

Immediately after finishing a feature, bugfix, or refactor
Before pushing or opening a pull request to document changes
When you want a quick, shareable changelog entry in Korean
During regular development to keep a running log of progress
When onboarding reviewers who need a concise summary

Best practices

Keep summaries to 2–3 sentences for clarity and fast review
Include only essential code snippets — avoid large dumps
Use consistent file names and timestamps under workthrough folder
Run the skill after successful build and test to ensure accurate status
Treat suggested next steps as prioritized TODOs, not exhaustive tasks

Example use cases

Add a new API endpoint: document implemented route, validation, and tests, then propose caching or pagination improvements
Fix a UI bug: summarize the fix, show the minimal CSS/JS change, and recommend regression tests
Refactor a module: state what was refactored, performance benefits, and next refactor targets
Small performance tweak: note measurements, modified code, and suggest broader profiling
Initial project setup: record VitePress initialization steps and follow-up tasks for documentation

FAQ

Can I change the output language?

This skill produces the walkthrough content in Korean by design; adjust the agent configuration if you need a different language.

Where are files stored?

Walkthrough files are saved to <project-root>/workthrough/YYYY-MM-DD_HH_MM_description.md with consistent naming for easy tracking.