[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6QZQTNF815AWYMAMJ3B25GY":3,"skill-same:01M6QZQTNF815AWYMAMJ3B25GY":72},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":54,"ownerHtmlUrl":55,"ownerBlogUrl":6,"ownerDescription":56,"updatedAt":57,"install":58,"resources":71},"01M6QZQTNF815AWYMAMJ3B25GY","sync-claude-md",null,"커밋·푸시·PR\u002FMR 직전에 이번 변경이 프로젝트 CLAUDE.md 를 낡게 만드는지 검토하고, 필요할 때만 갱신 diff 를 제안한다 — 아키텍처·디렉터리 구조, 새 통합\u002FMCP, 컨벤션, 빌드·CI·도구, 주요 의존성 변화가 대상. 해당 없으면 한 줄로 끝낸다.\nReviews whether pending changes make the project CLAUDE.md stale (architecture, integrations, conventions, build\u002FCI\u002Ftooling, major dependencies) and proposes a minimal update diff only when needed.\nUse when: \"CLAUDE.md 갱신 필요해?\", \"CLAUDE.md 동기화\", 커밋\u002F푸시\u002FMR 전에 구조·도구가 바뀐 변경을 정리할 때, sync CLAUDE.md, check CLAUDE.md before commit or PR.","Dokkabei97\u002Fdokkabei-harness","Dokkabei97","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F69792585?v=4","01M6QYPVTYK6CGF609W541QNSD","JangMK","01M6QYPVYXBP1GRYHZ7ZABCZC6",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FDokkabei97\u002Fdokkabei-harness\u002Fblob\u002Fmain\u002Fplugins\u002Fworkflow\u002Fskills\u002Fsync-claude-md\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"sync claude md","sync","claude md","only","when","mr","pending","reviews","make","project","minimal","MCP","diff","use","integrations","ci","update","pr","architecture","commit","2026-11-10 10:12:30",false,"---\nname: sync-claude-md\ndescription: |\n  커밋·푸시·PR\u002FMR 직전에 이번 변경이 프로젝트 CLAUDE.md 를 낡게 만드는지 검토하고, 필요할 때만 갱신 diff 를 제안한다 — 아키텍처·디렉터리 구조, 새 통합\u002FMCP, 컨벤션, 빌드·CI·도구, 주요 의존성 변화가 대상. 해당 없으면 한 줄로 끝낸다.\n  Reviews whether pending changes make the project CLAUDE.md stale (architecture, integrations, conventions, build\u002FCI\u002Ftooling, major dependencies) and proposes a minimal update diff only when needed.\n  Use when: \"CLAUDE.md 갱신 필요해?\", \"CLAUDE.md 동기화\", 커밋\u002F푸시\u002FMR 전에 구조·도구가 바뀐 변경을 정리할 때, sync CLAUDE.md, check CLAUDE.md before commit or PR.\n---\n\n# Sync CLAUDE.md — 변경 기반 CLAUDE.md 유지보수\n\n## Overview\n\nBefore a commit\u002Fpush or PR\u002FMR, check whether the pending change makes the project CLAUDE.md\nstale, and if so propose a minimal update. Creation and stack facts of a project's CLAUDE.md\nbelong to `workflow:project-rules`; this skill **maintains** it afterwards.\n\nThe workflow plugin ships a non-blocking `PreToolUse(Bash)` hook that adds a one-line reminder\nto context on the session's first `git commit`\u002F`git push` (kill switch `CLAUDE_MD_SYNC_REMIND=0`).\nThe reminder arrives with the command's result, so a needed update usually goes into a follow-up\ncommit (or `--amend` if the user prefers and the commit is not pushed).\n\n## 1. When it helps\n\n| Situation | Suggested depth |\n|-----------|-----------------|\n| Explicit request (\"CLAUDE.md sync\", \"CLAUDE.md 갱신 필요해?\") | Phase 1~5, always report the verdict |\n| About to commit\u002Fpush\u002Fopen an MR, and the change touched structure\u002Ftooling\u002Fconventions | Phase 1~3; if no update needed, one line at most |\n| Reminder from the hook after the first commit\u002Fpush | Phase 1~3 on the just-committed range (`git diff HEAD~1`) |\n\nSkip it for changes that clearly stay within existing patterns (bug fix, feature in an existing\nlayout, tests, docs) — the check should cost nothing when nothing changed.\n\n## 2. Behavioral Flow\n\n### Phase 1: Locate CLAUDE.md\n1. Look for `CLAUDE.md` > `claude\u002FCLAUDE.md` > `.claude\u002FCLAUDE.md` at the project root.\n2. If none exists: say so and point to `workflow:project-rules` (creation is not this skill's job).\n3. Read it and note the existing sections, plus any `\u003C!-- project-rules:start -->…\u003C!-- project-rules:end -->`\n   block — that block is owned by `workflow:project-rules`; suggest `\u002Fproject-rules --check` instead of editing it.\n4. `git diff --cached -- '**\u002FCLAUDE.md'` — mention if CLAUDE.md is already staged.\n\n### Phase 2: Collect the change scope\n\n| Condition | Target |\n|-----------|--------|\n| Staged changes exist | `git diff --cached` |\n| PR\u002FMR context | `git diff \u003Cdefault-branch>...HEAD` (detect default branch, do not assume `main`) |\n| Just committed (hook reminder) | `git diff HEAD~1` |\n| Fallback | `git diff HEAD` |\n\nUse `--name-only` and `--stat` first; read the full diff only for files that look structural.\n\n### Phase 3: Classify\n\n**Update likely needed:**\n\n| Category | Signals |\n|---|---|\n| Architecture | new top-level\u002Fmodule directories, changed module boundaries, new layers |\n| Integration\u002FMCP | `.mcp.json`\u002F`mcp\u002F` changes, new external service clients |\n| Conventions | linter\u002Fformatter config, new shared base classes or utilities that others must use |\n| Build\u002Ftooling\u002Fenv | Dockerfile, compose, CI config (`.gitlab-ci.yml`, `.github\u002Fworkflows\u002F`), Makefile\u002Fjustfile, new verify commands |\n| Major dependency | new framework\u002Flibrary (not version bumps) in build.gradle(.kts), go.mod, pyproject.toml, package.json |\n| Claude assets | new `skills\u002F`, `commands\u002F`, `agents\u002F`, `.claude\u002F` config |\n\n**Usually not needed:** bug fixes, features inside existing patterns, tests, docs, renames.\n\nA version bump of the JDK\u002FKotlin\u002FGo\u002FSpring\u002FNext toolchain is a stack fact — route it to\n`workflow:project-rules --check` rather than editing the managed block here.\n\n### Phase 4: Propose\n- No update needed → manual invocation: report briefly; reminder\u002Fcommit context: one line or nothing.\n- Update needed → show the target section(s) and a minimal diff (add\u002Fmodify\u002Fremove lines).\n  Prefer removing stale lines over adding new ones; keep the file under ~200 lines\n  (official guidance: longer files consume more context and reduce adherence).\n  Content that matters only for part of the codebase belongs in a path-scoped `.claude\u002Frules\u002F` file.\n\n### Phase 5: Apply (after the user agrees)\n1. Edit CLAUDE.md.\n2. Stage it with the change if a commit is about to happen; otherwise leave it for a follow-up commit.\n3. Summarize in 1–2 lines: \"CLAUDE.md 갱신: {sections}\".\n\n## 3. Section mapping\n\n| Category | CLAUDE.md section |\n|---|---|\n| Architecture | Architecture \u002F Structure |\n| Integration\u002FMCP | Integrations \u002F MCP |\n| Conventions | Conventions \u002F Coding Standards |\n| Build\u002Ftooling\u002Fenv | Commands \u002F Development Setup |\n| Major dependency | Tech Stack |\n| Claude assets | Skills \u002F Commands |\n\n## 4. Examples\n\n### Commit with a structural change\n```\nUser: \"커밋 푸시 해줘\"\n[Phase 2] git diff --cached → docker-compose.yml added, .gitlab-ci.yml modified\n[Phase 3] Build\u002Ftooling change → update likely needed\n[Phase 4] Proposed diff: Commands section +2 lines (docker compose up, CI stage name)\nUser agrees → [Phase 5] CLAUDE.md staged with the commit\n```\n\n### Commit within existing patterns\n```\nUser: \"커밋해줘\"\n[Phase 2] src\u002F...\u002FOrderService.kt 1 file, 3 lines\n[Phase 3] Bug fix → no update; continue with the commit (no extra output)\n```\n\n### Manual check\n```\nUser: \"CLAUDE.md 갱신 필요해?\"\n→ \"필요 없음 — 변경 유형: 버그 수정, 1 file, 기존 구조 내\"\n```\n\n## 5. Boundaries\n\n**Will:**\n- Review pending changes and propose minimal CLAUDE.md diffs; apply after agreement\n- Stay quiet when nothing structural changed\n\n**Will Not:**\n- Modify `~\u002F.claude\u002FCLAUDE.md` (global) — project-level only\n- Create CLAUDE.md from scratch or rewrite the `project-rules` managed block (→ `workflow:project-rules`)\n- Run `git commit`\u002F`git push` itself or modify files other than CLAUDE.md\n\n## 6. Related\n\n| Component | Relationship |\n|-----------|-------------|\n| `workflow:project-rules` | Creates CLAUDE.md stack facts and `.claude\u002Frules\u002F`; `--check` audits version drift |\n| `workflow:retro` (`\u002Fretro`) | Routes convention-change lessons here |\n| `hooks\u002Fremind-claude-md-sync.js` | Non-blocking first-commit reminder (`CLAUDE_MD_SYNC_REMIND=0` to disable) |\n","# Sync CLAUDE.md — 변경 기반 CLAUDE.md 유지보수\n\n## Overview\n\nBefore a commit\u002Fpush or PR\u002FMR, check whether the pending change makes the project CLAUDE.md\nstale, and if so propose a minimal update. Creation and stack facts of a project's CLAUDE.md\nbelong to `workflow:project-rules`; this skill **maintains** it afterwards.\n\nThe workflow plugin ships a non-blocking `PreToolUse(Bash)` hook that adds a one-line reminder\nto context on the session's first `git commit`\u002F`git push` (kill switch `CLAUDE_MD_SYNC_REMIND=0`).\nThe reminder arrives with the command's result, so a needed update usually goes into a follow-up\ncommit (or `--amend` if the user prefers and the commit is not pushed).\n\n## 1. When it helps\n\n| Situation | Suggested depth |\n|-----------|-----------------|\n| Explicit request (\"CLAUDE.md sync\", \"CLAUDE.md 갱신 필요해?\") | Phase 1~5, always report the verdict |\n| About to commit\u002Fpush\u002Fopen an MR, and the change touched structure\u002Ftooling\u002Fconventions | Phase 1~3; if no update needed, one line at most |\n| Reminder from the hook after the first commit\u002Fpush | Phase 1~3 on the just-committed range (`git diff HEAD~1`) |\n\nSkip it for changes that clearly stay within existing patterns (bug fix, feature in an existing\nlayout, tests, docs) — the check should cost nothing when nothing changed.\n\n## 2. Behavioral Flow\n\n### Phase 1: Locate CLAUDE.md\n1. Look for `CLAUDE.md` > `claude\u002FCLAUDE.md` > `.claude\u002FCLAUDE.md` at the project root.\n2. If none exists: say so and point to `workflow:project-rules` (creation is not this skill's job).\n3. Read it and note the existing sections, plus any `\u003C!-- project-rules:start -->…\u003C!-- project-rules:end -->`\n   block — that block is owned by `workflow:project-rules`; suggest `\u002Fproject-rules --check` instead of editing it.\n4. `git diff --cached -- '**\u002FCLAUDE.md'` — mention if CLAUDE.md is already staged.\n\n### Phase 2: Collect the change scope\n\n| Condition | Target |\n|-----------|--------|\n| Staged changes exist | `git diff --cached` |\n| PR\u002FMR context | `git diff \u003Cdefault-branch>...HEAD` (detect default branch, do not assume `main`) |\n| Just committed (hook reminder) | `git diff HEAD~1` |\n| Fallback | `git diff HEAD` |\n\nUse `--name-only` and `--stat` first; read the full diff only for files that look structural.\n\n### Phase 3: Classify\n\n**Update likely needed:**\n\n| Category | Signals |\n|---|---|\n| Architecture | new top-level\u002Fmodule directories, changed module boundaries, new layers |\n| Integration\u002FMCP | `.mcp.json`\u002F`mcp\u002F` changes, new external service clients |\n| Conventions | linter\u002Fformatter config, new shared base classes or utilities that others must use |\n| Build\u002Ftooling\u002Fenv | Dockerfile, compose, CI config (`.gitlab-ci.yml`, `.github\u002Fworkflows\u002F`), Makefile\u002Fjustfile, new verify commands |\n| Major dependency | new framework\u002Flibrary (not version bumps) in build.gradle(.kts), go.mod, pyproject.toml, package.json |\n| Claude assets | new `skills\u002F`, `commands\u002F`, `agents\u002F`, `.claude\u002F` config |\n\n**Usually not needed:** bug fixes, features inside existing patterns, tests, docs, renames.\n\nA version bump of the JDK\u002FKotlin\u002FGo\u002FSpring\u002FNext toolchain is a stack fact — route it to\n`workflow:project-rules --check` rather than editing the managed block here.\n\n### Phase 4: Propose\n- No update needed → manual invocation: report briefly; reminder\u002Fcommit context: one line or nothing.\n- Update needed → show the target section(s) and a minimal diff (add\u002Fmodify\u002Fremove lines).\n  Prefer removing stale lines over adding new ones; keep the file under ~200 lines\n  (official guidance: longer files consume more context and reduce adherence).\n  Content that matters only for part of the codebase belongs in a path-scoped `.claude\u002Frules\u002F` file.\n\n### Phase 5: Apply (after the user agrees)\n1. Edit CLAUDE.md.\n2. Stage it with the change if a commit is about to happen; otherwise leave it for a follow-up commit.\n3. Summarize in 1–2 lines: \"CLAUDE.md 갱신: {sections}\".\n\n## 3. Section mapping\n\n| Category | CLAUDE.md section |\n|---|---|\n| Architecture | Architecture \u002F Structure |\n| Integration\u002FMCP | Integrations \u002F MCP |\n| Conventions | Conventions \u002F Coding Standards |\n| Build\u002Ftooling\u002Fenv | Commands \u002F Development Setup |\n| Major dependency | Tech Stack |\n| Claude assets | Skills \u002F Commands |\n\n## 4. Examples\n\n### Commit with a structural change\n```\nUser: \"커밋 푸시 해줘\"\n[Phase 2] git diff --cached → docker-compose.yml added, .gitlab-ci.yml modified\n[Phase 3] Build\u002Ftooling change → update likely needed\n[Phase 4] Proposed diff: Commands section +2 lines (docker compose up, CI stage name)\nUser agrees → [Phase 5] CLAUDE.md staged with the commit\n```\n\n### Commit within existing patterns\n```\nUser: \"커밋해줘\"\n[Phase 2] src\u002F...\u002FOrderService.kt 1 file, 3 lines\n[Phase 3] Bug fix → no update; continue with the commit (no extra output)\n```\n\n### Manual check\n```\nUser: \"CLAUDE.md 갱신 필요해?\"\n→ \"필요 없음 — 변경 유형: 버그 수정, 1 file, 기존 구조 내\"\n```\n\n## 5. Boundaries\n\n**Will:**\n- Review pending changes and propose minimal CLAUDE.md diffs; apply after agreement\n- Stay quiet when nothing structural changed\n\n**Will Not:**\n- Modify `~\u002F.claude\u002FCLAUDE.md` (global) — project-level only\n- Create CLAUDE.md from scratch or rewrite the `project-rules` managed block (→ `workflow:project-rules`)\n- Run `git commit`\u002F`git push` itself or modify files other than CLAUDE.md\n\n## 6. Related\n\n| Component | Relationship |\n|-----------|-------------|\n| `workflow:project-rules` | Creates CLAUDE.md stack facts and `.claude\u002Frules\u002F`; `--check` audits version drift |\n| `workflow:retro` (`\u002Fretro`) | Routes convention-change lessons here |\n| `hooks\u002Fremind-claude-md-sync.js` | Non-blocking first-commit reminder (`CLAUDE_MD_SYNC_REMIND=0` to disable) |\n",{"name":5,"description":7},"main","e9f37e996e3d2b1b6ac9c879e9dfba1223b597c3","plugins\u002Fworkflow\u002Fskills\u002Fsync-claude-md",0,"https:\u002F\u002Fgithub.com\u002FDokkabei97\u002Fdokkabei-harness","https:\u002F\u002Fdokkabei97.github.io\u002Fdokkabei-harness\u002F","https:\u002F\u002Fgithub.com\u002FDokkabei97","Contact: wkdrn970@gmail.com","2026-10-29 06:49:16",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add Dokkabei97\u002Fdokkabei-harness --skill sync-claude-md",{"tool":64,"command":65},"bunx","bunx skills add Dokkabei97\u002Fdokkabei-harness --skill sync-claude-md",{"tool":67,"command":68},"pnpm","pnpm dlx skills add Dokkabei97\u002Fdokkabei-harness --skill sync-claude-md","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FDokkabei97\u002Fdokkabei-harness\u002Fblob\u002Fmain\u002Fplugins\u002Fworkflow\u002Fskills\u002Fsync-claude-md\u002FSKILL.md",true,[],[73,104,127,148,171,197],{"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":85,"publishedAt":44},"01M6QZQEK94G00N955VQH9EFQN","spec-driven-dev","새 기능·프로젝트·큰 변경을 코드보다 스펙 먼저로 진행하는 게이트 워크플로(SPECIFY → PLAN → TASKS → IMPLEMENT) — 가정 명시, 측정 가능한 성공 기준, Always\u002FAsk\u002FNever 경계, 단계별 사람 검토로 범위 이탈과 재작업을 줄인다.\nSpec-before-code gated workflow for new features or significant changes: explicit assumptions, measurable success criteria, boundaries, and a human review between stages.\nUse when: \"스펙 먼저\", \"기능 명세\", \"요구사항 정리\", starting a new feature or project, a significant change with vague requirements. 단순 버그 수정·1~2줄 변경엔 불필요.","https:\u002F\u002Fgithub.com\u002FDokkabei97\u002Fdokkabei-harness\u002Fblob\u002Fmain\u002Fplugins\u002Fworkflow\u002Fskills\u002Fspec-driven-dev\u002FSKILL.md",[79,80],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":81,"categoryName":82,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[86,87,88,89,90,91,92,93,94,95,96,97,98,99,33,100,101,102,103,28],"spec","spec driven","dev","spec driven dev","driven","review","workflow","change","tasks","code","plan","ask","never","human","feature","for","vague","features",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":44},"01M6QZQA9F6QVGTVDMJ28YQGDV","shipping-guide","프로덕션 배포 전후 가이드 — 배포 전 체크리스트, 피처 플래그 수명주기, 단계적 롤아웃과 진행\u002F보류\u002F롤백 임계값, 롤백 계획 템플릿, 배포 후 모니터링.\nProduction shipping guide: pre-launch checklist, feature-flag lifecycle, staged rollout with go\u002Fhold\u002Frollback thresholds, rollback plan template, post-launch monitoring.\nUse when: \"배포 준비\", \"릴리즈 전 점검\", \"롤아웃 계획\", \"롤백 계획\", preparing a production deploy, staged rollout, feature flags.","https:\u002F\u002Fgithub.com\u002FDokkabei97\u002Fdokkabei-harness\u002Fblob\u002Fmain\u002Fplugins\u002Fworkflow\u002Fskills\u002Fshipping-guide\u002FSKILL.md",[],[111,112,113,114,115,116,117,96,118,119,37,120,121,100,122,123,124,125,126,28],"shipping","guide","shipping guide","launch","monitoring","lifecycle","feature flags","template","rollback","rollout","flags","thresholds","post","with","pre-launch","rollback plan",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":44},"01M6QZQ3M962PCWYM6YH62D76Z","retro","세션 회고·교훈 컴파운딩 — 이번 세션의 교정·실수·발견을 추출해 품질 기준(재현·일반화·판정 가능성)으로 거르고, 컨벤션 변화는 sync-claude-md 위임, 반복 실수는 tasks\u002Flessons.md(#가드-훅-후보 태그), 스킬 지식 갱신은 수정 제안으로 나눈다. 모든 적용은 승인 후.\nSession retrospective that turns corrections, mistakes, and discoveries into vetted lessons routed to CLAUDE.md sync, tasks\u002Flessons.md, or skill-edit proposals, with user approval before any write.\nUse when: \"회고\", \"레트로\", \"교훈 정리\", \"같은 실수 반복\", \"재발 방지 규칙\", retrospective, lessons learned, wrapping up a task, review, or loop. 여러 실행에 걸친 하네스 개선은 harness:evolve.","https:\u002F\u002Fgithub.com\u002FDokkabei97\u002Fdokkabei-harness\u002Fblob\u002Fmain\u002Fplugins\u002Fworkflow\u002Fskills\u002Fretro\u002FSKILL.md",[],[129,91,25,94,134,135,136,137,138,139,140,141,27,142,143,144,145,146,147,28],"run","harness","loop","evolve","write","edit","proposals","session","up","dry","learned","Session Retrospective","lessons","mistakes",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":155,"publishedAt":44},"01M6QZPPDATJ7DAGNP0JCXFGRV","project-rules","현재 프로젝트의 스택(빌드 파일 버전, 마이그레이션 도구, ORM 유무, ES 사용, git 호스트)을 감지해 프로젝트 루트 AGENTS.md 의 마커 블록(스택 사실 + 항상 적용되는 스페셜리스트 핵심 ≤15줄 — Claude Code·Codex·Antigravity 공통)과 CLAUDE.md 의 `@AGENTS.md` 연결, Claude 전용 경로 한정 .claude\u002Frules\u002F\u003Cstack>-specialist.md(해당 버전에 실제로 맞는 상세 함정)를 diff 로 제안하고, 스택 플러그인을 런타임별로 프로젝트 범위에서 켜는 법을 안내한다. 이전 버전 출력(CLAUDE.md 블록·specialist-core.md)은 AGENTS.md 로 이전을 제안. --check 는 버전 불일치·사라진 ID·크기 한도·연결 누락을 점검.\nDetects the project's stack and proposes a cross-runtime AGENTS.md block (stack facts + always-on specialist core) linked from CLAUDE.md via @AGENTS.md, plus Claude-only path-scoped specialist rules; migrates the older CLAUDE.md-block layout; --check audits drift.\nUse when: \"이 프로젝트 세팅\", \"프로젝트 규칙 생성\", \"AGENTS.md\u002FCLAUDE.md 점검\", project setup, generate project rules, audit AGENTS.md or CLAUDE.md drift.","https:\u002F\u002Fgithub.com\u002FDokkabei97\u002Fdokkabei-harness\u002Fblob\u002Fmain\u002Fplugins\u002Fworkflow\u002Fskills\u002Fproject-rules\u002FSKILL.md",[154],{"categoryNo":81,"categoryName":82,"taxonomyType":83,"taxonomyTypeDesc":84},[156,33,157,158,159,95,160,161,162,163,36,27,164,165,166,167,168,169,170,28],"Rules","project rules","core","generate","git","audit","stack","orm","es","drift","layout","runtime","-specialist","path","scoped",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":175,"categories":176,"keywords":181,"publishedAt":44},"01M6QZPF3S8YAM27F297F6GVD7","post-merge","MR 머지 완료 후 Plane 이슈 종료와 Outline 문서 업데이트를 자동으로 처리하는 오케스트레이터 스킬입니다.\nissue-tracker와 document-latest 스킬을 연계 실행하여 머지 후 후속 작업을 일괄 처리합니다.\nOrchestrates post-merge follow-up after an MR is merged: chains the issue-tracker and document-latest skills to close the Plane issue and update Outline wiki docs in a single batch. Use when: an MR was just merged, closing tickets and syncing documentation after a merge, post-merge cleanup.","https:\u002F\u002Fgithub.com\u002FDokkabei97\u002Fdokkabei-harness\u002Fblob\u002Fmain\u002Fplugins\u002Fworkflow\u002Fskills\u002Fpost-merge\u002FSKILL.md",[177,180],{"categoryNo":178,"categoryName":179,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[182,183,123,184,185,40,186,187,188,142,189,190,191,192,193,194,195,196,29,28],"merge","post merge","documentation","cleanup","batch","wiki","just","issue","tracker","close","closing","follow-up","true","plane","single",{"skillNo":198,"name":199,"nameZh":6,"description":200,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":201,"categories":202,"keywords":203,"publishedAt":44},"01M6QZPA69ZMNE613JWW6QE6EY","planning-guide","모호한 아이디어를 원페이저 계획과 실행 가능한 태스크로 바꾸는 가이드 — 문제 재진술, 가정 명시, 의존성 순서, 수직 슬라이싱, 태스크 크기(XS~XL)와 분해 기준, 태스크 템플릿.\nTurns vague ideas into a one-page plan and implementable tasks: problem restatement, explicit assumptions, dependency order, vertical slicing, task sizing.\nUse when: \"계획 세워줘\", \"태스크로 쪼개줘\", \"작업 분해\", \"범위 정리\", breaking down a feature, planning a vague request.","https:\u002F\u002Fgithub.com\u002FDokkabei97\u002Fdokkabei-harness\u002Fblob\u002Fmain\u002Fplugins\u002Fworkflow\u002Fskills\u002Fplanning-guide\u002FSKILL.md",[],[204,112,205,94,96,206,37,207,208,209,100,210,211,102,212,213,28],"planning","planning guide","page","dependency","task","ideas","problem","one-page","down","request"]