[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BQF47MTGFQW5CYA3E9QHEW":3,"skill-same:01M7BQF47MTGFQW5CYA3E9QHEW":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"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":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7BQF47MTGFQW5CYA3E9QHEW","lexforge-archive",null,"Use when the verification report of a LexForge change is clean and the change is asked to be closed out - the user says to archive it, to merge its delta into the specs, or to finish the branch it was built on.","shepaland\u002FLexForge","shepaland","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F122363057?v=4","01M7BQEZBGE97WJ1V279CSYC3A","01M7BQEZC62M44EBNTXM79BCK7",1,"MIT","https:\u002F\u002Fgithub.com\u002Fshepaland\u002FLexForge\u002Fblob\u002Fmain\u002Fskills\u002Flexforge-archive\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: lexforge-archive\ndescription: Use when the verification report of a LexForge change is clean and the change is asked to be closed out - the user says to archive it, to merge its delta into the specs, or to finish the branch it was built on.\n---\n\n\u003C!-- model-block:start -->\n## Model\n\nArchival demands no model: it merges the delta into the long-lived specs and\nruns on whichever model is at work. No provider is named a model here.\n\u003C!-- model-block:end -->\n\u003C!-- queue-rule:start -->\n## Queue rule\n\nFirst run `lexforge status --change \u003Cname> --tool \u003Cyour runtime> --json`; parse JSON.\nBefore it: no code, tests or task questions. No change named: run `lexforge status --json`\nand ask which. `isPlanningComplete: true` permits work. If `false`, name the first\nartifact neither `done` nor `skipped` and\n`lexforge instructions \u003Cthat artifact> --change \u003Cname> --tool \u003Cyour runtime>`; stop.\nClosed gates permit no code or task answers, including under deadlines or requests to skip.\n\n`engineeringStacks: \"missing\"` in status or `engineering-stacks-missing` in an error means the\nproject has not named its stacks. Ask the user which it uses: node, python, jvm, go, dotnet,\nphp, ruby, rust, react, vue, angular, svelte. Wait for the answer, then run\n`lexforge stacks set \u003Cstack>...`. Run `lexforge stacks set --none` only when the user says the\nproject uses none of them. Never choose the stacks yourself, even when the files show only one.\nA guess the user can undo later is still a guess.\nNever write them into `lexforge\u002Fconfig.yaml` by hand.\nAsk even when told not to ask about setup. Unset is not an answer.\n\nExit `2`: read `error.code`. `workspace-not-found` \u002F `workspace-incomplete`: run\n`lexforge init --tools \u003Cyour runtime>` at the root (`agents` if none matches), then retry\nthe command that refused. Never construct workspace files by hand.\n`change-not-found`: run `lexforge status --json` and list active changes.\nOther errors: show `error.message` and stop. Use exit codes and JSON, never human lines\nor directory appearance. No answered gate means no work.\n\n\u003C!-- version-gate:start -->\n## Version gate\n\nExit `2` with `error.code` `update-available`: show `error.message` to the user and wait for the user's answer. Never run `npm install` yourself.\n\nExit `2` with `error.code` `skills-outdated`: run the `lexforge init` command that `error.message` names. Then run the command that refused again. If it refuses with `skills-outdated` a second time, show `error.message` and stop.\n\u003C!-- version-gate:end -->\n\n\u003C!-- model-gate:start -->\n## Model gate\n\nRead `provider` and `model` from `lexforge instructions \u003Cartifact> --change \u003Cname> --tool \u003Cyour runtime> --json`\nfor artifacts; otherwise use your entry in `stages` from\n`lexforge status --change \u003Cname> --tool \u003Cyour runtime> --json`.\nThe `stage` is your skill name without `lexforge-` (`apply`, `debug`, `verify`, `archive`).\nName your runtime from `lexforge init --tools`; omit `--tool` only if none matches.\n\nAn empty assignment, no workspace, no change, or no stage entry uses the model block\nabove for your provider. An unlisted provider imposes no model.\nOn the assigned model, work without model commentary. Otherwise start a subagent on\nthat model, hand it the work, and do none of it yourself. Disclosure or later review\nis not delegation. If unreachable, name the model and stop: restore access or let the\nuser change the assignment in `lexforge\u002Fconfig.yaml`; do not change it yourself.\n\u003C!-- model-gate:end -->\n\u003C!-- queue-rule:end -->\n\n## The rule\n\n**NEVER ARCHIVE WITHOUT A VERIFICATION REPORT IN FRONT OF YOU.**\n\nThe report is the one `lexforge-verify` writes: requirements against behaviour, plan\nagainst work done, `design.md` decisions against implementation, zero findings above\nMINOR. No report here? Name `lexforge-verify` next and stop. CRITICAL or IMPORTANT open?\nGive the work back to it. MINOR leaves the merge to run.\n\nA report is not a green suite, a fresh stamp, ticked boxes, per-task reviews, a compacted\nsession, or the user saying it came out clean. Those are what `lexforge archive` recounts.\n\n## Running the command\n\n`lexforge archive \u003Cname>`, then read the exit code.\n\n- `0` - delta merged, change directory moved; `--json` gives `archivePath`.\n- `1` - findings or conflicts, listed; nothing was written. Fix what is named, run again.\n- `2` - refused: no workspace, no change, planning unfinished, archive path taken, no\n  repository, empty `verification`. Show `error.message` and stop. `change-needs-migration`\n  instead: installing LexForge 6.0.0 migrates no existing change by itself; run\n  `lexforge migrate --change \u003Cname>`, name historical and open tasks and any\n  `missingFields`, then send the open part through plan review and owner approval.\n\nNever announce the code you expect: an unrun command has no result.\n\n## A conflict is fixed in the delta\n\nA conflict means the delta and the specs disagree about the system. Fix it in the delta:\nthe dropped scenario goes back into the MODIFIED block, a heading is spelled as the spec\nspells it.\n\nEditing a file under `lexforge\u002Fspecs\u002F` by hand to pass the merge is out. That file is what\nthe merge writes; hand-editing it takes live behaviour out of the record and disarms the\ncheck that caught the mismatch. Offering to do it if they insist is doing it, one message\nlater.\n\nCopying the spec's block into the delta unchanged is the same failure wearing a `0`: the\nmerge writes back what was there, and the change ships behaviour with no requirement.\n\nRun the command again until it exits `0`.\n\n## Finishing the branch\n\n`lexforge archive` merges the change's feature branch into dev itself.\n\nOn a conflict the change stays on its feature branch. The command exits `1` and lists the\nconflicting paths in the findings. Show them to the user. Then follow `nextStep`: check out\ndev, run `git merge feature\u002F\u003Cname>`, resolve, commit.\n\nMerge dev into main only on the user's answer to the question `nextStep` names. Ask it,\nname `main` aloud, wait. After a merge, run the checks. Red stops the work: the branch and\nworktree stay, and the failure is the next thing you say.\n\n| Excuse | Reality |\n|---|---|\n| \"We ship fast here\" | Pace is not an answer. Ask. |\n| \"Archive is done, nice. Thanks.\" | Thanks ends the archive, not the question. |\n| \"A pull request I open myself\" | It starts the release unasked. |\n\n## Rationalizations\n\n| Excuse | Reality |\n|---|---|\n| \"fourteen task-scoped reviews beat one tired end-of-change skim\" | Fourteen diffs against fourteen tasks answer no question about the change. |\n| \"it costs you nothing on the Friday clock: it happens after the archive\" | After the archive there is no change left to fix it in. |\n| \"so if it exits `0` the gate held\" | Four machine checks held. A contradicted decision passes all four. |\n| \"If you reaffirm, that's your call and I'll make the edit without re-arguing it\" | The offer is the edit, one message later. |\n| \"This should exit `0`\" | The command decides that, not the argument that it would. |\n\n## Red flags - stop\n\n- The archive command run with no verification report in this conversation.\n- A file under `lexforge\u002Fspecs\u002F` edited by hand while a conflict is open.\n- A branch merged, pushed or deleted before the user answered.\n- An exit code named instead of read.\n","\u003C!-- model-block:start -->\n## Model\n\nArchival demands no model: it merges the delta into the long-lived specs and\nruns on whichever model is at work. No provider is named a model here.\n\u003C!-- model-block:end -->\n\u003C!-- queue-rule:start -->\n## Queue rule\n\nFirst run `lexforge status --change \u003Cname> --tool \u003Cyour runtime> --json`; parse JSON.\nBefore it: no code, tests or task questions. No change named: run `lexforge status --json`\nand ask which. `isPlanningComplete: true` permits work. If `false`, name the first\nartifact neither `done` nor `skipped` and\n`lexforge instructions \u003Cthat artifact> --change \u003Cname> --tool \u003Cyour runtime>`; stop.\nClosed gates permit no code or task answers, including under deadlines or requests to skip.\n\n`engineeringStacks: \"missing\"` in status or `engineering-stacks-missing` in an error means the\nproject has not named its stacks. Ask the user which it uses: node, python, jvm, go, dotnet,\nphp, ruby, rust, react, vue, angular, svelte. Wait for the answer, then run\n`lexforge stacks set \u003Cstack>...`. Run `lexforge stacks set --none` only when the user says the\nproject uses none of them. Never choose the stacks yourself, even when the files show only one.\nA guess the user can undo later is still a guess.\nNever write them into `lexforge\u002Fconfig.yaml` by hand.\nAsk even when told not to ask about setup. Unset is not an answer.\n\nExit `2`: read `error.code`. `workspace-not-found` \u002F `workspace-incomplete`: run\n`lexforge init --tools \u003Cyour runtime>` at the root (`agents` if none matches), then retry\nthe command that refused. Never construct workspace files by hand.\n`change-not-found`: run `lexforge status --json` and list active changes.\nOther errors: show `error.message` and stop. Use exit codes and JSON, never human lines\nor directory appearance. No answered gate means no work.\n\n\u003C!-- version-gate:start -->\n## Version gate\n\nExit `2` with `error.code` `update-available`: show `error.message` to the user and wait for the user's answer. Never run `npm install` yourself.\n\nExit `2` with `error.code` `skills-outdated`: run the `lexforge init` command that `error.message` names. Then run the command that refused again. If it refuses with `skills-outdated` a second time, show `error.message` and stop.\n\u003C!-- version-gate:end -->\n\n\u003C!-- model-gate:start -->\n## Model gate\n\nRead `provider` and `model` from `lexforge instructions \u003Cartifact> --change \u003Cname> --tool \u003Cyour runtime> --json`\nfor artifacts; otherwise use your entry in `stages` from\n`lexforge status --change \u003Cname> --tool \u003Cyour runtime> --json`.\nThe `stage` is your skill name without `lexforge-` (`apply`, `debug`, `verify`, `archive`).\nName your runtime from `lexforge init --tools`; omit `--tool` only if none matches.\n\nAn empty assignment, no workspace, no change, or no stage entry uses the model block\nabove for your provider. An unlisted provider imposes no model.\nOn the assigned model, work without model commentary. Otherwise start a subagent on\nthat model, hand it the work, and do none of it yourself. Disclosure or later review\nis not delegation. If unreachable, name the model and stop: restore access or let the\nuser change the assignment in `lexforge\u002Fconfig.yaml`; do not change it yourself.\n\u003C!-- model-gate:end -->\n\u003C!-- queue-rule:end -->\n\n## The rule\n\n**NEVER ARCHIVE WITHOUT A VERIFICATION REPORT IN FRONT OF YOU.**\n\nThe report is the one `lexforge-verify` writes: requirements against behaviour, plan\nagainst work done, `design.md` decisions against implementation, zero findings above\nMINOR. No report here? Name `lexforge-verify` next and stop. CRITICAL or IMPORTANT open?\nGive the work back to it. MINOR leaves the merge to run.\n\nA report is not a green suite, a fresh stamp, ticked boxes, per-task reviews, a compacted\nsession, or the user saying it came out clean. Those are what `lexforge archive` recounts.\n\n## Running the command\n\n`lexforge archive \u003Cname>`, then read the exit code.\n\n- `0` - delta merged, change directory moved; `--json` gives `archivePath`.\n- `1` - findings or conflicts, listed; nothing was written. Fix what is named, run again.\n- `2` - refused: no workspace, no change, planning unfinished, archive path taken, no\n  repository, empty `verification`. Show `error.message` and stop. `change-needs-migration`\n  instead: installing LexForge 6.0.0 migrates no existing change by itself; run\n  `lexforge migrate --change \u003Cname>`, name historical and open tasks and any\n  `missingFields`, then send the open part through plan review and owner approval.\n\nNever announce the code you expect: an unrun command has no result.\n\n## A conflict is fixed in the delta\n\nA conflict means the delta and the specs disagree about the system. Fix it in the delta:\nthe dropped scenario goes back into the MODIFIED block, a heading is spelled as the spec\nspells it.\n\nEditing a file under `lexforge\u002Fspecs\u002F` by hand to pass the merge is out. That file is what\nthe merge writes; hand-editing it takes live behaviour out of the record and disarms the\ncheck that caught the mismatch. Offering to do it if they insist is doing it, one message\nlater.\n\nCopying the spec's block into the delta unchanged is the same failure wearing a `0`: the\nmerge writes back what was there, and the change ships behaviour with no requirement.\n\nRun the command again until it exits `0`.\n\n## Finishing the branch\n\n`lexforge archive` merges the change's feature branch into dev itself.\n\nOn a conflict the change stays on its feature branch. The command exits `1` and lists the\nconflicting paths in the findings. Show them to the user. Then follow `nextStep`: check out\ndev, run `git merge feature\u002F\u003Cname>`, resolve, commit.\n\nMerge dev into main only on the user's answer to the question `nextStep` names. Ask it,\nname `main` aloud, wait. After a merge, run the checks. Red stops the work: the branch and\nworktree stay, and the failure is the next thing you say.\n\n| Excuse | Reality |\n|---|---|\n| \"We ship fast here\" | Pace is not an answer. Ask. |\n| \"Archive is done, nice. Thanks.\" | Thanks ends the archive, not the question. |\n| \"A pull request I open myself\" | It starts the release unasked. |\n\n## Rationalizations\n\n| Excuse | Reality |\n|---|---|\n| \"fourteen task-scoped reviews beat one tired end-of-change skim\" | Fourteen diffs against fourteen tasks answer no question about the change. |\n| \"it costs you nothing on the Friday clock: it happens after the archive\" | After the archive there is no change left to fix it in. |\n| \"so if it exits `0` the gate held\" | Four machine checks held. A contradicted decision passes all four. |\n| \"If you reaffirm, that's your call and I'll make the edit without re-arguing it\" | The offer is the edit, one message later. |\n| \"This should exit `0`\" | The command decides that, not the argument that it would. |\n\n## Red flags - stop\n\n- The archive command run with no verification report in this conversation.\n- A file under `lexforge\u002Fspecs\u002F` edited by hand while a conflict is open.\n- A branch merged, pushed or deleted before the user answered.\n- An exit code named instead of read.\n",{"name":5,"description":7},"main","88026324b1714f1c0e540ee6b1864a79556e65df","skills\u002Flexforge-archive",0,"https:\u002F\u002Fgithub.com\u002Fshepaland\u002FLexForge","https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Flexforge","https:\u002F\u002Fgithub.com\u002Fshepaland","2026-10-25 22:05:47",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add shepaland\u002FLexForge --skill lexforge-archive",{"tool":37,"command":38},"bunx","bunx skills add shepaland\u002FLexForge --skill lexforge-archive",{"tool":40,"command":41},"pnpm","pnpm dlx skills add shepaland\u002FLexForge --skill lexforge-archive","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshepaland\u002FLexForge\u002Fblob\u002Fmain\u002Fskills\u002Flexforge-archive\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M7BQH5XPYKM4043980E7X639","sample-verify","Use when the install mechanics need a second skill to copy - stands in for the real verify skill","https:\u002F\u002Fgithub.com\u002Fshepaland\u002FLexForge\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Fsample-verify\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":18},"01M7BQH26ZAX9F7DEFGBQ3K5XV","sample-plan","Use when the install mechanics need a skill to copy - stands in for the real planning skill","https:\u002F\u002Fgithub.com\u002Fshepaland\u002FLexForge\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Fsample-plan\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M7BQH07Q9JQ32D1YQCHR6FWZ","three-fields","Use when a structure check needs a frontmatter with a field that does not belong there","https:\u002F\u002Fgithub.com\u002Fshepaland\u002FLexForge\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills-structure\u002Fthree-fields\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M7BQGYJ0XG6WFD65J7KYZ9FQ","no-use-when","Runs the structure checks over a description that opens with the wrong words","https:\u002F\u002Fgithub.com\u002Fshepaland\u002FLexForge\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills-structure\u002Fno-use-when\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M7BQGWV5RJVW6F8GTKP98RM3","another-name","Use when a structure check needs a name that disagrees with the directory around it","https:\u002F\u002Fgithub.com\u002Fshepaland\u002FLexForge\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills-structure\u002Fname-mismatch\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M7BQGTVJP3CKFQTMPNMSGYNS","minimal","Use when a structure check needs a skill that breaks no rule - the baseline fixture","https:\u002F\u002Fgithub.com\u002Fshepaland\u002FLexForge\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills-structure\u002Fminimal\u002FSKILL.md",[],[]]