[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6NJHWS9G9MSE7BFAD9YTNWF":3,"skill-same:01M6NJHWS9G9MSE7BFAD9YTNWF":53},{"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":27,"linkOnly":28,"markdownContent":29,"markdownBody":30,"frontMatter":31,"refName":32,"commitSha":33,"skillDirectory":34,"forksCount":14,"repositoryHtmlUrl":35,"repositoryHomepageUrl":6,"ownerHtmlUrl":36,"ownerBlogUrl":37,"ownerDescription":6,"updatedAt":38,"install":39,"resources":52},"01M6NJHWS9G9MSE7BFAD9YTNWF","release",null,"Create a new auto-stack release by tagging a commit and pushing the tag. The GitHub Actions release workflow builds binaries and publishes the release.","mistakenot\u002Fauto-stack","mistakenot","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F7852099?v=4","01M6CY3K3NE7B30VD9C8HP815J","Charlie","01M6NHYR6FB2SEZ7DFHD3PS3D6",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmistakenot\u002Fauto-stack\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frelease\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26],"github","workflow","commit","create","actions","github actions","stack","auto","2026-11-10 10:12:30",false,"---\nname: release\ndescription: >-\n    Create a new auto-stack release by tagging a commit and pushing the tag. The GitHub Actions release workflow builds binaries and publishes the release.\nlicense: MIT\n---\n\n# Release\n\nCreate a new auto-stack release. The agent's only job is to tag and push — GitHub Actions handles building and publishing.\n\n## How It Works\n\n1. You push a semver tag (e.g. `v0.8.0`) to the repo.\n2. The `.github\u002Fworkflows\u002Frelease.yml` workflow triggers on `v*` tags.\n3. It cross-compiles the single `auto` binary for `linux-amd64` and `darwin-arm64`.\n4. It creates (or updates) a GitHub Release with the binaries attached.\n5. Users install via `curl -fsSL https:\u002F\u002Fraw.githubusercontent.com\u002Fmistakenot\u002Fauto-stack\u002Fmain\u002Finstall.sh | bash`.\n\n## Steps\n\n### Step 1: Determine the next version\n\n```bash\n# Get the latest release tag\nLATEST=$(git tag --sort=-v:refname | head -1)\necho \"Latest tag: $LATEST\"\n```\n\nCheck what has changed since the last release:\n\n```bash\ngit log ${LATEST}..HEAD --oneline\n```\n\nApply semver:\n- **Patch** (v0.7.0 -> v0.7.1): bug fixes only\n- **Minor** (v0.7.0 -> v0.8.0): new features, non-breaking changes\n- **Major** (v0.7.0 -> v1.0.0): breaking changes\n\nAsk the user to confirm the version before proceeding.\n\n### Step 2: Verify the build\n\nRun the full build and tests to make sure everything compiles:\n\n```bash\nmake build\nmake test\n```\n\nDo not proceed if either fails.\n\n### Step 3: Tag and push\n\n```bash\nVERSION=\"v0.8.0\"  # use the confirmed version\ngit tag \"$VERSION\"\ngit push origin \"$VERSION\"\n```\n\n### Step 4: Monitor the release\n\nCheck that the workflow succeeded:\n\n```bash\n# Wait a moment for the workflow to start, then check\ngh run list --workflow=release.yml --limit=1\n```\n\nIf the run fails, check logs with:\n\n```bash\ngh run view \u003Crun-id> --log-failed\n```\n\n### Step 5: Verify the release assets\n\n```bash\ngh release view \"$VERSION\" --json assets --jq '.assets[].name'\n```\n\nExpected assets (the single `auto` binary, one per platform):\n- `auto-linux-amd64`\n- `auto-darwin-arm64`\n\n## Important\n\n- **Do not create releases through the GitHub UI.** Always push tags from the CLI. The workflow creates the release.\n- **Do not force-push or move tags.** If a release fails, diagnose and fix the issue, then create a new patch version.\n- **All binaries must compile** before tagging. The CI build will fail if any sub-project has errors.\n","# Release\n\nCreate a new auto-stack release. The agent's only job is to tag and push — GitHub Actions handles building and publishing.\n\n## How It Works\n\n1. You push a semver tag (e.g. `v0.8.0`) to the repo.\n2. The `.github\u002Fworkflows\u002Frelease.yml` workflow triggers on `v*` tags.\n3. It cross-compiles the single `auto` binary for `linux-amd64` and `darwin-arm64`.\n4. It creates (or updates) a GitHub Release with the binaries attached.\n5. Users install via `curl -fsSL https:\u002F\u002Fraw.githubusercontent.com\u002Fmistakenot\u002Fauto-stack\u002Fmain\u002Finstall.sh | bash`.\n\n## Steps\n\n### Step 1: Determine the next version\n\n```bash\n# Get the latest release tag\nLATEST=$(git tag --sort=-v:refname | head -1)\necho \"Latest tag: $LATEST\"\n```\n\nCheck what has changed since the last release:\n\n```bash\ngit log ${LATEST}..HEAD --oneline\n```\n\nApply semver:\n- **Patch** (v0.7.0 -> v0.7.1): bug fixes only\n- **Minor** (v0.7.0 -> v0.8.0): new features, non-breaking changes\n- **Major** (v0.7.0 -> v1.0.0): breaking changes\n\nAsk the user to confirm the version before proceeding.\n\n### Step 2: Verify the build\n\nRun the full build and tests to make sure everything compiles:\n\n```bash\nmake build\nmake test\n```\n\nDo not proceed if either fails.\n\n### Step 3: Tag and push\n\n```bash\nVERSION=\"v0.8.0\"  # use the confirmed version\ngit tag \"$VERSION\"\ngit push origin \"$VERSION\"\n```\n\n### Step 4: Monitor the release\n\nCheck that the workflow succeeded:\n\n```bash\n# Wait a moment for the workflow to start, then check\ngh run list --workflow=release.yml --limit=1\n```\n\nIf the run fails, check logs with:\n\n```bash\ngh run view \u003Crun-id> --log-failed\n```\n\n### Step 5: Verify the release assets\n\n```bash\ngh release view \"$VERSION\" --json assets --jq '.assets[].name'\n```\n\nExpected assets (the single `auto` binary, one per platform):\n- `auto-linux-amd64`\n- `auto-darwin-arm64`\n\n## Important\n\n- **Do not create releases through the GitHub UI.** Always push tags from the CLI. The workflow creates the release.\n- **Do not force-push or move tags.** If a release fails, diagnose and fix the issue, then create a new patch version.\n- **All binaries must compile** before tagging. The CI build will fail if any sub-project has errors.\n",{"name":5,"license":15,"description":7},"main","8075db80b0f662909c8c49bbf04da1acb03c24e1",".agents\u002Fskills\u002Frelease","https:\u002F\u002Fgithub.com\u002Fmistakenot\u002Fauto-stack","https:\u002F\u002Fgithub.com\u002Fmistakenot","charliedaly.co.uk","2026-10-29 07:32:11",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add mistakenot\u002Fauto-stack --skill release",{"tool":45,"command":46},"bunx","bunx skills add mistakenot\u002Fauto-stack --skill release",{"tool":48,"command":49},"pnpm","pnpm dlx skills add mistakenot\u002Fauto-stack --skill release","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmistakenot\u002Fauto-stack\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frelease\u002FSKILL.md",true,[],[54,59,81,112,137,154],{"skillNo":55,"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":56,"categories":57,"keywords":58,"publishedAt":27},"01M6NK49FNTVKG4KNN4ZZ1XH84","https:\u002F\u002Fgithub.com\u002Fmistakenot\u002Fauto-stack\u002Fblob\u002Fmain\u002Fskills\u002Frelease\u002FSKILL.md",[],[5,26,25,24,23,22,21,20,19],{"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":27},"01M6NK3M6TNEBZBBTMY0JM6884","recall","Reconstruct and narrate the current development context from contextual commits. Run at session start, when resuming work, or when switching branches. Produces a brief, conversational summary of where things stand.","https:\u002F\u002Fgithub.com\u002Fmistakenot\u002Fauto-stack\u002Fblob\u002Fmain\u002Fskills\u002Frecall\u002FSKILL.md",[],[61,66,67,68,69,70,71,72,73,74,75,76,77,78,79,80],"development","run","brief","start","commits","things","resuming","work","at","session start","switching","branches","summary","session","context",{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":92,"publishedAt":27},"01M6NK3C68MGDACSHXF0MAF07Y","readme-updater","Bring a project's README up to date with the current state of the codebase. Audits the existing README for stale commands, dead links, renamed tools, and drifted status claims; surveys what's changed since the README was last touched; rewrites it with verified facts; then commits and pushes. Use this skill whenever the user says \"update the README\", \"the readme is stale\", \"refresh the README\", \"rewrite README.md\", \"add new features to the readme\", or otherwise asks for documentation that reflects the current state of the project. Also trigger when a README clearly hasn't kept pace with the codebase (e.g. recent feature commits not reflected, broken examples).","https:\u002F\u002Fgithub.com\u002Fmistakenot\u002Fauto-stack\u002Fblob\u002Fmain\u002Fskills\u002Freadme-updater\u002FSKILL.md",[87],{"categoryNo":88,"categoryName":89,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[93,94,95,96,97,98,99,100,101,102,103,104,105,106,70,107,108,109,110,111],"readme updater","updater","README","bring","feature","verified","claims","for","add","features","links","project","up","broken","Tools","update","documentation","status","commands",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":27},"01M6NK2W0073Z14AYD6FBQH3V8","contextual-commit","Write contextual commits that capture intent, decisions, and constraints alongside code changes. Use when committing code, finishing a task, or when the user asks to commit. Extends Conventional Commits with structured action lines in the commit body that preserve WHY code was written, not just WHAT changed.","https:\u002F\u002Fgithub.com\u002Fmistakenot\u002Fauto-stack\u002Fblob\u002Fmain\u002Fskills\u002Fcontextual-commit\u002FSKILL.md",[],[119,21,120,121,122,123,70,124,125,126,127,128,129,130,131,132,133,134,135,136],"contextual commit","decisions","capture","just","capture intent","why","constraints","code","write","preserve","changes","action","with","task","intent","conventional commits","use","user",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":146,"publishedAt":27},"01M6NK2JEGH6QC2EPQSZNCTDWC","deploy-checklist","A pre-deployment checklist for safe releases.","https:\u002F\u002Fgithub.com\u002Fmistakenot\u002Fauto-stack\u002Fblob\u002Fmain\u002Fharness\u002Fscenarios\u002Fskill-remote\u002Ffixtures\u002Fskills\u002Fdeploy-checklist\u002FSKILL.md",[143],{"categoryNo":144,"categoryName":145,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000011","运维与部署",[147,148,149,100,150,151,152,153],"deploy checklist","checklist","deploy","deployment checklist","releases","deployment","safe",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":168,"publishedAt":27},"01M6NK2EDH7XHR830B51AA750P","code-review","Structured code review with severity labels.","https:\u002F\u002Fgithub.com\u002Fmistakenot\u002Fauto-stack\u002Fblob\u002Fmain\u002Fharness\u002Fscenarios\u002Fskill-remote\u002Ffixtures\u002Fskills\u002Fcode-review\u002FSKILL.md",[160,163],{"categoryNo":161,"categoryName":162,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":164,"categoryName":165,"taxonomyType":166,"taxonomyTypeDesc":167},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[169,126,170,171,131,172,173],"review","code review","labels","structured","severity"]