[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DK62N6CDZ2TH890AX2Z7P9":3,"skill-same:01M7DK62N6CDZ2TH890AX2Z7P9":51},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":36,"install":37,"resources":50},"01M7DK62N6CDZ2TH890AX2Z7P9","dh-semver",null,"Apply strict Semantic Versioning — analyze commits since the last tag to determine the bump type (major\u002Fminor\u002Fpatch from conventional commit prefixes), generate an automated changelog grouped by breaking changes, features, fixes, and chores, and create a git tag locally without pushing until confirmed, handling both conventional commits and manual version decisions. Use when preparing a release, invoked by dh-execute-plan after plan completion and dh-final-review for release readiness, or when the user asks \"what version is next?\", \"bump version\", \"generate changelog\", \"tag release\", or \"what changed since last release?\".","andrescevp\u002Fdevelopment-harness","andrescevp","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F10025841?v=4","01M7DK1Q07H5GT5R4JSGMWV1DE","Andres Cevallos","01M7DK1Q18W9DHVMV4HZ4BQAY3",8,"MIT","https:\u002F\u002Fgithub.com\u002Fandrescevp\u002Fdevelopment-harness\u002Fblob\u002Fmain\u002Fskills\u002Fdh-semver\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: dh-semver\ndescription: >\n  Apply strict Semantic Versioning — analyze commits since the last tag to\n  determine the bump type (major\u002Fminor\u002Fpatch from conventional commit\n  prefixes), generate an automated changelog grouped by breaking changes,\n  features, fixes, and chores, and create a git tag locally without pushing\n  until confirmed, handling both conventional commits and manual version\n  decisions. Use when preparing a release, invoked by dh-execute-plan after\n  plan completion and dh-final-review for release readiness, or when the\n  user asks \"what version is next?\", \"bump version\", \"generate changelog\",\n  \"tag release\", or \"what changed since last release?\".\nlicense: MIT\ncompatibility: opencode\nallowed-tools: bash, read\nmetadata:\n  audience: developers\n  workflow: development\n---\n\nHarness-localized adaptation of the global `semver` skill. The versioning\nalgorithm is identical; the harness adaptations are that every git command\nruns through the `dh-execute-cli` skill, and this skill is invoked from the\nbundled loop skills or a direct user request — the harness bundles no\ncommands.\n\n## Core Rules\n\n- Find the last tag: `git describe --tags --abbrev=0`. If that fails because\n  the repo has no tags yet, default to `v0.0.0`.\n- Collect the commits since that tag: `git log \u003Ctag>..HEAD --oneline`.\n- Map commit messages to the bump type using conventional commit prefixes:\n  - `BREAKING CHANGE:` in the message body, or `!` after the type\n    (`feat!:`), → **MAJOR** bump\n  - `feat:` or `feat(scope):` → **MINOR** bump\n  - `fix:`, `chore:`, `docs:`, `style:`, `refactor:`, `perf:`, `test:`,\n    `ci:`, `build:` → **PATCH** bump\n- If no conventional commit format is detected, prompt the user for the\n  bump type — never guess.\n- Generate the changelog grouped by Breaking Changes (if any), Features,\n  Fixes, and Chores & Maintenance; every entry keeps its short commit hash.\n- Create the tag locally:\n  `git tag -a v\u003Cmajor>.\u003Cminor>.\u003Cpatch> -m \"Release v\u003Cmajor>.\u003Cminor>.\u003Cpatch>\"`.\n- Do NOT push the tag — the user confirms before pushing.\n- Run ALL git commands through the `dh-execute-cli` skill — never run bash\n  directly from the agent applying this skill.\n\n## Edge Cases\n\n- No commits since the last tag → report\n  \"No changes — no version bump needed\" and stop.\n- No tags in the repo → treat `v0.0.0` as the current version, but note it\n  is not a real ref to diff against — enumerate ALL commits with\n  `git log --oneline` to determine the first release.\n- Tags exist but are unreachable from the current branch (e.g. releases are\n  tagged on `main` while you work on `develop`) → `git describe` under-reports\n  the current version. Cross-check `git tag --sort=-v:refname` for the highest\n  released tag and state the assumption; the durable fix is the repo's\n  back-merge of `main` after tagging, which keeps tags reachable.\n- History without conventional commit prefixes → ask the user which bump\n  applies; do not infer a bump from vague messages.\n\n## Harness Invocation Sources\n\nThe harness bundles no commands, so there is no release command step to\nimport. This skill runs when:\n\n- `dh-execute-plan` finishes a plan on a software project and needs the next\n  version bump.\n- `dh-final-review` checks release readiness and reports the recommended\n  bump.\n- The user asks directly: \"what version is next?\", \"bump version\",\n  \"generate changelog\", \"tag release\", or \"what changed since last release?\".\n\n## Output Template\n\n```markdown\n# Version Decision\n\n**Current:** vX.Y.Z (tag: \u003Ctagname>)\n**Bump:** MAJOR \u002F MINOR \u002F PATCH → **vX.Y.Z**\n**Reason:** [N breaking changes, N features, N fixes]\n\n# Changelog vX.Y.Z\n\n## Breaking Changes\n- [Description] (\u003Ccommit-short-hash>)\n\n## Features\n- [Description] (\u003Ccommit-short-hash>)\n\n## Fixes\n- [Description] (\u003Ccommit-short-hash>)\n\n## Chores & Maintenance\n- [Description] (\u003Ccommit-short-hash>)\n\n**Tag:** `vX.Y.Z` (created locally — awaiting confirmation to push)\n```\n\n## Safety\n\n- Do not push tags or commits without explicit user confirmation.\n- Do not delete or modify existing tags.\n- Create the tag only after the version decision and changelog are reported;\n  the tag stays local until the user confirms pushing.\n- Report the decision with its git evidence (last tag, commit counts, short\n  hashes) exactly as the `dh-execute-cli` skill reports it — no guessing.\n\n## References\n\n- `dh-execute-plan` and `dh-final-review` skills: the bundled loop steps\n  that invoke this skill.\n- `AGENTS.md` versioning note: tags are semver on `main` only.\n\n## Doc search\n\n**Documentation management:** delegate create \u002F update \u002F delete \u002F retrieve of generated documents (excluding docs\u002Fplans) to the best available documentation agent (bundled documentation capability as fallback) — the main and only documentation owner (see dh-create-documentation).\n\nSearch generated documentation quickly: `notesmd-cli search-content \"\u003Cterm>\" --vault \"\u003Cproject-name>\"` or `obsidian search query=\"\u003Cterm>\"` (fallback: `rg --glob '*.md' \"\u003Cterm>\" docs\u002F`).\n","Harness-localized adaptation of the global `semver` skill. The versioning\nalgorithm is identical; the harness adaptations are that every git command\nruns through the `dh-execute-cli` skill, and this skill is invoked from the\nbundled loop skills or a direct user request — the harness bundles no\ncommands.\n\n## Core Rules\n\n- Find the last tag: `git describe --tags --abbrev=0`. If that fails because\n  the repo has no tags yet, default to `v0.0.0`.\n- Collect the commits since that tag: `git log \u003Ctag>..HEAD --oneline`.\n- Map commit messages to the bump type using conventional commit prefixes:\n  - `BREAKING CHANGE:` in the message body, or `!` after the type\n    (`feat!:`), → **MAJOR** bump\n  - `feat:` or `feat(scope):` → **MINOR** bump\n  - `fix:`, `chore:`, `docs:`, `style:`, `refactor:`, `perf:`, `test:`,\n    `ci:`, `build:` → **PATCH** bump\n- If no conventional commit format is detected, prompt the user for the\n  bump type — never guess.\n- Generate the changelog grouped by Breaking Changes (if any), Features,\n  Fixes, and Chores & Maintenance; every entry keeps its short commit hash.\n- Create the tag locally:\n  `git tag -a v\u003Cmajor>.\u003Cminor>.\u003Cpatch> -m \"Release v\u003Cmajor>.\u003Cminor>.\u003Cpatch>\"`.\n- Do NOT push the tag — the user confirms before pushing.\n- Run ALL git commands through the `dh-execute-cli` skill — never run bash\n  directly from the agent applying this skill.\n\n## Edge Cases\n\n- No commits since the last tag → report\n  \"No changes — no version bump needed\" and stop.\n- No tags in the repo → treat `v0.0.0` as the current version, but note it\n  is not a real ref to diff against — enumerate ALL commits with\n  `git log --oneline` to determine the first release.\n- Tags exist but are unreachable from the current branch (e.g. releases are\n  tagged on `main` while you work on `develop`) → `git describe` under-reports\n  the current version. Cross-check `git tag --sort=-v:refname` for the highest\n  released tag and state the assumption; the durable fix is the repo's\n  back-merge of `main` after tagging, which keeps tags reachable.\n- History without conventional commit prefixes → ask the user which bump\n  applies; do not infer a bump from vague messages.\n\n## Harness Invocation Sources\n\nThe harness bundles no commands, so there is no release command step to\nimport. This skill runs when:\n\n- `dh-execute-plan` finishes a plan on a software project and needs the next\n  version bump.\n- `dh-final-review` checks release readiness and reports the recommended\n  bump.\n- The user asks directly: \"what version is next?\", \"bump version\",\n  \"generate changelog\", \"tag release\", or \"what changed since last release?\".\n\n## Output Template\n\n```markdown\n# Version Decision\n\n**Current:** vX.Y.Z (tag: \u003Ctagname>)\n**Bump:** MAJOR \u002F MINOR \u002F PATCH → **vX.Y.Z**\n**Reason:** [N breaking changes, N features, N fixes]\n\n# Changelog vX.Y.Z\n\n## Breaking Changes\n- [Description] (\u003Ccommit-short-hash>)\n\n## Features\n- [Description] (\u003Ccommit-short-hash>)\n\n## Fixes\n- [Description] (\u003Ccommit-short-hash>)\n\n## Chores & Maintenance\n- [Description] (\u003Ccommit-short-hash>)\n\n**Tag:** `vX.Y.Z` (created locally — awaiting confirmation to push)\n```\n\n## Safety\n\n- Do not push tags or commits without explicit user confirmation.\n- Do not delete or modify existing tags.\n- Create the tag only after the version decision and changelog are reported;\n  the tag stays local until the user confirms pushing.\n- Report the decision with its git evidence (last tag, commit counts, short\n  hashes) exactly as the `dh-execute-cli` skill reports it — no guessing.\n\n## References\n\n- `dh-execute-plan` and `dh-final-review` skills: the bundled loop steps\n  that invoke this skill.\n- `AGENTS.md` versioning note: tags are semver on `main` only.\n\n## Doc search\n\n**Documentation management:** delegate create \u002F update \u002F delete \u002F retrieve of generated documents (excluding docs\u002Fplans) to the best available documentation agent (bundled documentation capability as fallback) — the main and only documentation owner (see dh-create-documentation).\n\nSearch generated documentation quickly: `notesmd-cli search-content \"\u003Cterm>\" --vault \"\u003Cproject-name>\"` or `obsidian search query=\"\u003Cterm>\"` (fallback: `rg --glob '*.md' \"\u003Cterm>\" docs\u002F`).\n",{"name":5,"license":15,"metadata":24,"description":27,"allowed-tools":28,"compatibility":29},{"audience":25,"workflow":26},"developers","development","Apply strict Semantic Versioning — analyze commits since the last tag to determine the bump type (major\u002Fminor\u002Fpatch from conventional commit prefixes), generate an automated changelog grouped by breaking changes, features, fixes, and chores, and create a git tag locally without pushing until confirmed, handling both conventional commits and manual version decisions. Use when preparing a release, invoked by dh-execute-plan after plan completion and dh-final-review for release readiness, or when the user asks \"what version is next?\", \"bump version\", \"generate changelog\", \"tag release\", or \"what changed since last release?\".\n","bash, read","opencode","main","f7ddc0c3b3190e379bda1059d53f861bd4e1f30d","skills\u002Fdh-semver",1,"https:\u002F\u002Fgithub.com\u002Fandrescevp\u002Fdevelopment-harness","https:\u002F\u002Fgithub.com\u002Fandrescevp","2026-11-10 07:43:44",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add andrescevp\u002Fdevelopment-harness --skill dh-semver",{"tool":43,"command":44},"bunx","bunx skills add andrescevp\u002Fdevelopment-harness --skill dh-semver",{"tool":46,"command":47},"pnpm","pnpm dlx skills add andrescevp\u002Fdevelopment-harness --skill dh-semver","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fandrescevp\u002Fdevelopment-harness\u002Fblob\u002Fmain\u002Fskills\u002Fdh-semver\u002FSKILL.md",true,[],[52,59,66,73,80,87],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7DK6HMNFES75RNB4G6TE55T","dh-simplify","Review changed code for reuse, quality, and efficiency (three parallel reviews), then fix findings directly. Use after making changes or when asked to clean up, refactor, simplify, or improve this code.","https:\u002F\u002Fgithub.com\u002Fandrescevp\u002Fdevelopment-harness\u002Fblob\u002Fmain\u002Fskills\u002Fdh-simplify\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7DK6BFEQ9PVZTHKV0DR66BR","dh-setup","Audit system software, configure user MCPs\u002Fplugins, scaffold project QA (hooks + per-stack tools), bootstrap docs\u002Farchitecture with the selected architecture agent, and write harness directives into AGENTS.md. Use to check requirements or setup the environment.","https:\u002F\u002Fgithub.com\u002Fandrescevp\u002Fdevelopment-harness\u002Fblob\u002Fmain\u002Fskills\u002Fdh-setup\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7DK5SM44RAH10HM59JC6ZPZ","dh-review","Verify a plan sub-task against acceptance criteria, scope, done-when; review diff, validation, regression risk; structured verdict to tasks\u002Freview.md. Plan Alignment Mode (fast execution) is a separate mode: no sub-task selection, no diff review, no code review — it compares plan.md with plan_fast.md and writes tasks\u002Freview-fast.md (pre-execution) or tasks\u002Freview-fast-final.md (plan-end). Use after implementation, to review\u002Fverify the sub-task, or to check fast-plan alignment.","https:\u002F\u002Fgithub.com\u002Fandrescevp\u002Fdevelopment-harness\u002Fblob\u002Fmain\u002Fskills\u002Fdh-review\u002FSKILL.md",[],[],{"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":79,"publishedAt":19},"01M7DK5KKZ05K0FR0ARFHA58KG","dh-resume-plan","Resume a paused phased plan from docs\u002Fplans\u002F\u003Cslug>\u002Fhandoff.md: validate the contract, detect drift, rehydrate context, mark the handoff resumed, and continue via dh-execute-plan resume mode. Use when the user says \"resume the plan\", \"continue where we stopped\", \"pick up the plan\", or \"resume after a pause\".","https:\u002F\u002Fgithub.com\u002Fandrescevp\u002Fdevelopment-harness\u002Fblob\u002Fmain\u002Fskills\u002Fdh-resume-plan\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7DK5E10T47JWQAJSAXJHHGD","dh-preflight","Run tests, linters, static analysis as a release gate: auto-detect tooling, check dirty state, pass\u002Ffail verdict with actionable failures (no auto-fixes). Use to run preflight, pre-release check, or validate before release.","https:\u002F\u002Fgithub.com\u002Fandrescevp\u002Fdevelopment-harness\u002Fblob\u002Fmain\u002Fskills\u002Fdh-preflight\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7DK58BHEGQZNQXAA42RGS79","dh-planning","Write phased plans to .\u002Fdocs\u002Fplans\u002F\u003Cslug>\u002Fplan.md: phases with sub-tasks, requirements mapping (stable IDs), scope, acceptance criteria. SDD gate: invoke dh-grill-sdd when .\u002Fdocs\u002Fplans\u002F\u003Cslug>\u002Fsdd.md is absent. Use to plan this or create a plan.","https:\u002F\u002Fgithub.com\u002Fandrescevp\u002Fdevelopment-harness\u002Fblob\u002Fmain\u002Fskills\u002Fdh-planning\u002FSKILL.md",[],[]]