[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72T1EQKFGKGK1K2NJGGCJJS":3,"skill-same:01M72T1EQKFGKGK1K2NJGGCJJS":84},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":28,"commitSha":29,"skillDirectory":30,"forksCount":31,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":34,"ownerDescription":6,"updatedAt":35,"install":36,"resources":49},"01M72T1EQKFGKGK1K2NJGGCJJS","ywc-changelog-release-notes",null,"(ywc) Use when you need to generate CHANGELOG.md entries or user-facing release notes from git history, merged PRs, or ywc-release-pr-list output after completing a release or sprint. Trigger phrases: \"changelog 작성\", \"릴리즈 노트 생성\", \"release notes\", \"変更履歴\", \"リリースノート作成\", \"changelog\", \"what changed in this release\", \"ywc-changelog-release-notes\". Do not use for listing merged PRs as a summary table (use ywc-release-pr-list), committing the changelog file (use ywc-commit), creating the release PR (use ywc-create-pr), writing a postmortem after a patch release (use ywc-incident-postmortem), or general project docs (use ywc-project-docs).","yongwoon\u002Fywc-agent-toolkit","yongwoon","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9317029?v=4","01M72SZSF6VKANKG5QTMV4V95S","01M72SZSG8HHC3W2CV5P7EJ5AH",8,"MIT","https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fclaude-code\u002Fskills\u002Fywc-changelog-release-notes\u002FSKILL.md",[],[],"2026-11-10 22:39:42",false,"---\nname: ywc-changelog-release-notes\ndescription: >\n  (ywc) Use when you need to generate CHANGELOG.md entries or user-facing\n  release notes from git history, merged PRs, or ywc-release-pr-list output\n  after completing a release or sprint. Trigger phrases: \"changelog 작성\",\n  \"릴리즈 노트 생성\", \"release notes\", \"変更履歴\", \"リリースノート作成\", \"changelog\",\n  \"what changed in this release\", \"ywc-changelog-release-notes\". Do not use for\n  listing merged PRs as a summary table (use ywc-release-pr-list), committing\n  the changelog file (use ywc-commit), creating the release PR (use ywc-create-pr),\n  writing a postmortem after a patch release (use ywc-incident-postmortem), or general project docs (use ywc-project-docs).\nversion: 1.0.0\ncategory: release\nphase: release\nrequires: []\nadvisor_budget: 0\n---\n\n**Announce at start:** \"I'm using the ywc-changelog-release-notes skill to generate CHANGELOG entries and release notes.\"\n\n## Rationalization Defense\n\n| Excuse | Reality |\n|---|---|\n| \"git log is good enough for release notes\" | Raw commits are too technical for users and inconsistently formatted even for developers. |\n| \"My project is too small for a CHANGELOG\" | Even small projects benefit from structured history when debugging regressions or onboarding users. |\n| \"I'll write it manually — it's faster\" | Manual writing misses commits, inconsistently categorizes, and skips security entries. |\n| \"ywc-release-pr-list already covers this\" | ywc-release-pr-list *lists* PRs in a table; this skill *formats* them as readable, categorized changelog entries. |\n| \"Release notes and CHANGELOG are the same thing\" | Technical CHANGELOG targets developers (breaking changes, API diffs); release notes target users (features in plain language). |\n| \"Keep a Changelog format is too rigid\" | The format is a starting template. Categories prevent omitting security entries and ensure consistent grouping. |\n| \"I can just tag and push without notes\" | Undocumented releases create support burden. Users ask what changed; a changelog prevents repetitive questions. |\n\n## Arguments\n\n| Flag | Description |\n|---|---|\n| `--changelog` | Generate CHANGELOG.md entry in Keep a Changelog format (default) |\n| `--release` | Generate user-facing release notes in plain language |\n| `--both` | Generate both CHANGELOG entry and user-facing release notes |\n| `--from \u003Ctag>` | Start diff from this git tag (default: last tag from `git describe`) |\n| `--to \u003Cref>` | End diff at this ref (default: HEAD) |\n| `--version \u003Cv>` | Set the release version string (e.g., `1.2.0`) |\n| `--pr-list \u003Cfile>` | Read PR list from ywc-release-pr-list output instead of git log |\n| `--dry-run` | Print to stdout only — do not modify CHANGELOG.md |\n\n## Dynamic Context\n\n```bash\n# Last tag to determine version range\ngit describe --tags --abbrev=0 2>\u002Fdev\u002Fnull || echo \"(no tags yet)\"\n\n# Commits since last tag\ngit log $(git describe --tags --abbrev=0 2>\u002Fdev\u002Fnull)..HEAD --oneline 2>\u002Fdev\u002Fnull | head -30\n\n# Merged PRs if gh CLI is available\ngh pr list --state merged --limit 30 --json number,title,mergedAt,labels 2>\u002Fdev\u002Fnull | head -c 3000\n```\n\n## Workflow\n\n**Step 1 — Detect version range**\nDetermine `from` (last tag or `--from`) and `to` (HEAD or `--to`). If no prior tag exists (first release), set `from` to the repository's root commit (`git rev-list --max-parents=0 HEAD`) so the range spans the entire history. If `--version` is not provided, use AskUserQuestion to ask for it, then **immediately continue to Step 2 in the same turn** — do not end the turn or wait for further input after receiving the answer.\n\n**Step 2 — Parse commits**\nGroup by conventional commit type: `feat` → Added, `fix` → Fixed, `refactor`\u002F`chore` → internal (omit from user notes and the CHANGELOG entry, but log each as `Omitted: \u003Cshort-sha> \u003Csubject>` in the run summary), `security` → Security, `BREAKING CHANGE` → Changed.\n\n**Step 3 — Enrich from PRs**\nIf gh CLI is available or `--pr-list` is provided, use PR titles and labels for richer descriptions than raw commit messages.\n\n**Step 4 — Generate CHANGELOG entry**\nKeep a Changelog format: Added \u002F Changed \u002F Deprecated \u002F Removed \u002F Fixed \u002F Security. Insert below `## [Unreleased]`, above the previous release, in CHANGELOG.md (or `--dry-run` to stdout).\n\n**Step 5 — Generate release notes (if --release or --both)**\nPlain language summary: remove technical jargon, omit internal refactors and dependency bumps, frame features from user perspective.\n\n**Step 6 — Suggest git tag command**\nOutput: `git tag -a v1.2.0 -m \"Release v1.2.0\"` for the developer to run.\n\n## Output Format\n\n### CHANGELOG.md entry (Keep a Changelog)\n\n```markdown\n## [1.2.0] - 2026-05-01\n\n### Added\n- User profile photo upload\n\n### Fixed\n- Login redirect loop after password reset (#42)\n\n### Security\n- Upgraded dependency X to address CVE-YYYY-XXXXX\n```\n\n### User-facing release notes\n\n```markdown\n# What's new in v1.2.0\n\n**Profile photos**: You can now upload a photo from Settings → Profile.\n\n**Bug fixes**: Fixed an issue where users were sent back to the login page\nafter resetting their password.\n```\n\nSee [references\u002Fchangelog-format.md](references\u002Fchangelog-format.md) for the full Keep a Changelog spec and category definitions.\nSee [references\u002Frelease-notes-format.md](references\u002Frelease-notes-format.md) for user-facing writing guidelines and examples.\n\n## Integration\n\n- **After `ywc-release-pr-list`**: Feed the PR table output via `--pr-list` for richer, PR-linked descriptions.\n- **Before `ywc-create-pr`**: Include the CHANGELOG.md update as part of the release PR.\n- **After `ywc-commit`**: Run this skill to document the batch of changes before tagging.\n- **After `ywc-incident-postmortem`**: If an incident led to a patch release, key action items inform the Security or Fixed entry.\n\n## Banned Output Patterns\n\n| Pattern | Problem | Replace with |\n|---|---|---|\n| \"Various bug fixes and improvements\" | Meaningless to users | List each specific fix |\n| Commit hashes in user-facing notes | Users don't use git | PR numbers or feature names |\n| Internal code names or module paths | Users don't know internal structure | User-visible feature names |\n| Security entries only in user notes | Developers need CVE details | CVE reference in CHANGELOG; plain summary in release notes |\n| Refactor\u002Fchore entries in user notes | Not relevant to users | Omit from release notes (internal; also omitted from CHANGELOG per `references\u002Fchangelog-format.md`), but log each as `Omitted: \u003Cshort-sha> \u003Csubject>` in the run summary |\n","**Announce at start:** \"I'm using the ywc-changelog-release-notes skill to generate CHANGELOG entries and release notes.\"\n\n## Rationalization Defense\n\n| Excuse | Reality |\n|---|---|\n| \"git log is good enough for release notes\" | Raw commits are too technical for users and inconsistently formatted even for developers. |\n| \"My project is too small for a CHANGELOG\" | Even small projects benefit from structured history when debugging regressions or onboarding users. |\n| \"I'll write it manually — it's faster\" | Manual writing misses commits, inconsistently categorizes, and skips security entries. |\n| \"ywc-release-pr-list already covers this\" | ywc-release-pr-list *lists* PRs in a table; this skill *formats* them as readable, categorized changelog entries. |\n| \"Release notes and CHANGELOG are the same thing\" | Technical CHANGELOG targets developers (breaking changes, API diffs); release notes target users (features in plain language). |\n| \"Keep a Changelog format is too rigid\" | The format is a starting template. Categories prevent omitting security entries and ensure consistent grouping. |\n| \"I can just tag and push without notes\" | Undocumented releases create support burden. Users ask what changed; a changelog prevents repetitive questions. |\n\n## Arguments\n\n| Flag | Description |\n|---|---|\n| `--changelog` | Generate CHANGELOG.md entry in Keep a Changelog format (default) |\n| `--release` | Generate user-facing release notes in plain language |\n| `--both` | Generate both CHANGELOG entry and user-facing release notes |\n| `--from \u003Ctag>` | Start diff from this git tag (default: last tag from `git describe`) |\n| `--to \u003Cref>` | End diff at this ref (default: HEAD) |\n| `--version \u003Cv>` | Set the release version string (e.g., `1.2.0`) |\n| `--pr-list \u003Cfile>` | Read PR list from ywc-release-pr-list output instead of git log |\n| `--dry-run` | Print to stdout only — do not modify CHANGELOG.md |\n\n## Dynamic Context\n\n```bash\n# Last tag to determine version range\ngit describe --tags --abbrev=0 2>\u002Fdev\u002Fnull || echo \"(no tags yet)\"\n\n# Commits since last tag\ngit log $(git describe --tags --abbrev=0 2>\u002Fdev\u002Fnull)..HEAD --oneline 2>\u002Fdev\u002Fnull | head -30\n\n# Merged PRs if gh CLI is available\ngh pr list --state merged --limit 30 --json number,title,mergedAt,labels 2>\u002Fdev\u002Fnull | head -c 3000\n```\n\n## Workflow\n\n**Step 1 — Detect version range**\nDetermine `from` (last tag or `--from`) and `to` (HEAD or `--to`). If no prior tag exists (first release), set `from` to the repository's root commit (`git rev-list --max-parents=0 HEAD`) so the range spans the entire history. If `--version` is not provided, use AskUserQuestion to ask for it, then **immediately continue to Step 2 in the same turn** — do not end the turn or wait for further input after receiving the answer.\n\n**Step 2 — Parse commits**\nGroup by conventional commit type: `feat` → Added, `fix` → Fixed, `refactor`\u002F`chore` → internal (omit from user notes and the CHANGELOG entry, but log each as `Omitted: \u003Cshort-sha> \u003Csubject>` in the run summary), `security` → Security, `BREAKING CHANGE` → Changed.\n\n**Step 3 — Enrich from PRs**\nIf gh CLI is available or `--pr-list` is provided, use PR titles and labels for richer descriptions than raw commit messages.\n\n**Step 4 — Generate CHANGELOG entry**\nKeep a Changelog format: Added \u002F Changed \u002F Deprecated \u002F Removed \u002F Fixed \u002F Security. Insert below `## [Unreleased]`, above the previous release, in CHANGELOG.md (or `--dry-run` to stdout).\n\n**Step 5 — Generate release notes (if --release or --both)**\nPlain language summary: remove technical jargon, omit internal refactors and dependency bumps, frame features from user perspective.\n\n**Step 6 — Suggest git tag command**\nOutput: `git tag -a v1.2.0 -m \"Release v1.2.0\"` for the developer to run.\n\n## Output Format\n\n### CHANGELOG.md entry (Keep a Changelog)\n\n```markdown\n## [1.2.0] - 2026-05-01\n\n### Added\n- User profile photo upload\n\n### Fixed\n- Login redirect loop after password reset (#42)\n\n### Security\n- Upgraded dependency X to address CVE-YYYY-XXXXX\n```\n\n### User-facing release notes\n\n```markdown\n# What's new in v1.2.0\n\n**Profile photos**: You can now upload a photo from Settings → Profile.\n\n**Bug fixes**: Fixed an issue where users were sent back to the login page\nafter resetting their password.\n```\n\nSee [references\u002Fchangelog-format.md](references\u002Fchangelog-format.md) for the full Keep a Changelog spec and category definitions.\nSee [references\u002Frelease-notes-format.md](references\u002Frelease-notes-format.md) for user-facing writing guidelines and examples.\n\n## Integration\n\n- **After `ywc-release-pr-list`**: Feed the PR table output via `--pr-list` for richer, PR-linked descriptions.\n- **Before `ywc-create-pr`**: Include the CHANGELOG.md update as part of the release PR.\n- **After `ywc-commit`**: Run this skill to document the batch of changes before tagging.\n- **After `ywc-incident-postmortem`**: If an incident led to a patch release, key action items inform the Security or Fixed entry.\n\n## Banned Output Patterns\n\n| Pattern | Problem | Replace with |\n|---|---|---|\n| \"Various bug fixes and improvements\" | Meaningless to users | List each specific fix |\n| Commit hashes in user-facing notes | Users don't use git | PR numbers or feature names |\n| Internal code names or module paths | Users don't know internal structure | User-visible feature names |\n| Security entries only in user notes | Developers need CVE details | CVE reference in CHANGELOG; plain summary in release notes |\n| Refactor\u002Fchore entries in user notes | Not relevant to users | Omit from release notes (internal; also omitted from CHANGELOG per `references\u002Fchangelog-format.md`), but log each as `Omitted: \u003Cshort-sha> \u003Csubject>` in the run summary |\n",{"name":5,"phase":23,"version":24,"category":23,"requires":25,"description":26,"advisor_budget":27},"release","1.0.0",[],"(ywc) Use when you need to generate CHANGELOG.md entries or user-facing release notes from git history, merged PRs, or ywc-release-pr-list output after completing a release or sprint. Trigger phrases: \"changelog 작성\", \"릴리즈 노트 생성\", \"release notes\", \"変更履歴\", \"リリースノート作成\", \"changelog\", \"what changed in this release\", \"ywc-changelog-release-notes\". Do not use for listing merged PRs as a summary table (use ywc-release-pr-list), committing the changelog file (use ywc-commit), creating the release PR (use ywc-create-pr), writing a postmortem after a patch release (use ywc-incident-postmortem), or general project docs (use ywc-project-docs).\n",0,"main","7e8ac872e53df8c89d75663e031626281a2a2f5c","claude-code\u002Fskills\u002Fywc-changelog-release-notes",1,"https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit","https:\u002F\u002Fgithub.com\u002Fyongwoon","https:\u002F\u002Fwww.webhani.com","2026-11-08 17:14:59",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add yongwoon\u002Fywc-agent-toolkit --skill ywc-changelog-release-notes",{"tool":42,"command":43},"bunx","bunx skills add yongwoon\u002Fywc-agent-toolkit --skill ywc-changelog-release-notes",{"tool":45,"command":46},"pnpm","pnpm dlx skills add yongwoon\u002Fywc-agent-toolkit --skill ywc-changelog-release-notes","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fclaude-code\u002Fskills\u002Fywc-changelog-release-notes\u002FSKILL.md",true,[50,56,60,64,68,72,76,80],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"README.en.md","REFERENCE","参考文档",3241,"https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fclaude-code\u002Fskills\u002Fywc-changelog-release-notes\u002FREADME.en.md",{"path":57,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":58,"sourceHtmlUrl":59},"README.es.md",3773,"https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fclaude-code\u002Fskills\u002Fywc-changelog-release-notes\u002FREADME.es.md",{"path":61,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":62,"sourceHtmlUrl":63},"README.ja.md",3673,"https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fclaude-code\u002Fskills\u002Fywc-changelog-release-notes\u002FREADME.ja.md",{"path":65,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":66,"sourceHtmlUrl":67},"README.ko.md",3486,"https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fclaude-code\u002Fskills\u002Fywc-changelog-release-notes\u002FREADME.ko.md",{"path":69,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":70,"sourceHtmlUrl":71},"README.md",3592,"https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fclaude-code\u002Fskills\u002Fywc-changelog-release-notes\u002FREADME.md",{"path":73,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":74,"sourceHtmlUrl":75},"README.zh.md",3311,"https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fclaude-code\u002Fskills\u002Fywc-changelog-release-notes\u002FREADME.zh.md",{"path":77,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fchangelog-format.md",3131,"https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fclaude-code\u002Fskills\u002Fywc-changelog-release-notes\u002Freferences\u002Fchangelog-format.md",{"path":81,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Frelease-notes-format.md",3737,"https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fclaude-code\u002Fskills\u002Fywc-changelog-release-notes\u002Freferences\u002Frelease-notes-format.md",[85,91,97,104,111,118],{"skillNo":86,"name":87,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":18},"01M72TQ84GTCPCV2VJ778V17TW","missing-frontmatter","https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fscripts\u002Ffixtures\u002Fcodex-description-limit\u002Fmissing-frontmatter\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":18},"01M72TQ6M4BFWE7P9EPW0GZDCM","malformed-frontmatter","https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fscripts\u002Ffixtures\u002Fcodex-description-limit\u002Fmalformed-frontmatter\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":18},"01M72TQ3ESGKXZ4QRWGTX92BKJ","fixture-501-fail","(ywc) Use when aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa Do not use for x.","https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fscripts\u002Ffixtures\u002Fcodex-description-limit\u002F501-fail\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":18},"01M72TQ0HJ8H3R37J9WPWGKJZR","fixture-500-pass","(ywc) Use when aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa Do not use for x.","https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fscripts\u002Ffixtures\u002Fcodex-description-limit\u002F500-pass\u002FSKILL.md",[],[],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":18},"01M72TPWNCC7NEYD0D9N12KSQS","ywc-worktrees","(ywc) Use when creating, auditing, pruning, or resolving git worktrees for isolated task workspaces, whether delegated from an executor or used standalone. Triggers: \"worktree 생성\", \"worktree audit\", \"worktree 정리\", \"worktree prune\", \"ywc-worktrees\", \"create worktree\". Do not use for branch creation\u002Fdeletion alone, PR creation (use ywc-create-pr), CI or merge delivery (use ywc-finish-branch), task orchestration (use ywc-sequential-executor or ywc-parallel-executor), or non-git isolation.","https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fplugins\u002Fywc-agent-toolkit\u002Fskills\u002Fywc-worktrees\u002FSKILL.md",[],[],{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":18},"01M72TPRNR3E6QWB91GM98ABBV","ywc-wayfinder","(ywc) Use when a large or uncertain change needs multi-session discovery with a deterministic local map and exactly one active ticket before planning or implementation. Triggers: \"wayfinder\", \"길찾기\", \"discovery map\", \"multi-session discovery\", \"탐색 ticket\", \"経路整理\", \"探索マップ\", \"ywc-wayfinder\". Do not use for ordinary planning (use ywc-plan), idea clarification (use ywc-brainstorm), direct implementation, or tracker\u002Fdatabase writes outside the local Markdown map.","https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fplugins\u002Fywc-agent-toolkit\u002Fskills\u002Fywc-wayfinder\u002FSKILL.md",[],[]]