[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CDWK2KW9TYY0D66Q1CQQB2":3,"skill-same:01M7CDWK2KW9TYY0D66Q1CQQB2":45},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7CDWK2KW9TYY0D66Q1CQQB2","commit",null,"Use when committing or pushing changes to the repository.","dveyarangi\u002Fgoodwolf-harness","dveyarangi","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F693404?v=4","01M77KAGWZ8X0CNA092ZDNEF6T","Fima Rotter","01M7CDVSGB58A879MVTYC1SVD0",0,"MIT","https:\u002F\u002Fgithub.com\u002Fdveyarangi\u002Fgoodwolf-harness\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcommit\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: commit\ndescription: >-\n  Use when committing or pushing changes to the repository.\n---\n\n\u003Cstraw-dog question=\"q-yiygh6\">Mechanism: not yet\u003C\u002Fstraw-dog>\n\n- Look at pending changes; group them by content aligning with origin topic, ticket, rfc or change type (documentation, code, CI, skills).\n\n- Separate implementation and documentation commits.\n\n- Write the subject in the project's convention: the one it states, else the one its tooling enforces, else the one its recent history keeps; a project with none of these, Conventional Commits.\n\n- In case the file changes belong to several groups, commit the file with the group forming its dominant topic and mention the bleed in that commit's message.\n\n- Do not reference sessions in commit comments, sessions are ephemeral.\n\n- Unless already working in branch or instructed to branch - commit to default branch.\n\n- Work the person holds back stays on its own branch, never merged into the shared main until they\n  release it: whatever stands on main may be published.\n\n- When committing a code change, first run the checks the repository defines for itself — its\n  linter, its formatter in check mode, its type checker, its tests. Pure doc changes need none\n  of them. **Read them from where the project states them; never carry them here.** A commit\n  skill holding a project's commands is a second home for them, and it is wrong for every\n  project but the one it was written in.\n\n- Commit when the work closes — `\u002Fverify` has passed on it. Push as the project's local file states\n  its way of working with git; a push is never implied by a commit.\n\n\u003Cinstalled by=\"session\">\n**S5** Commit the work of the current session only: another session's changes may be its work in\nprogress, and in doubt ask the person. Work on a unit this session took over is its own, the\nholder's uncommitted changes to it included. Commit with the paths named, `git commit -- \u003Cfile>…`,\neach one this session wrote or moved, and stage nothing ahead of the commit; never a directory, a\nglob, `-A` or a bare `git commit` — in a tree where other sessions run, the index is shared.\n\u003C\u002Finstalled>\n\n\u003Cinstalled by=\"local\">\n**L8** Prefix the subject with the loop step that produced the work, uppercase, then a colon — one of\nthese and no other: `ALIGN`, `TICKET`, `PLAN`, `IMPLEMENT`, `VERIFY`, `MAINTAIN`,\n`DISCOVER`, `RECALL`, `CONCLUDE`; outside the ring, `FIX` for a repair taken on its own, `EQUIP`\nfor a change to the harness's own installation, `DREAM` for a record the second lobe wrote. A\nname for what the commit touched — the entry file, the local rules, the question store, an RFC —\nis not a step: a rule landed at an align is `ALIGN`, a question opened while planning is `PLAN`.\nOne prefix per commit; where the work spans two steps, take the dominant one and name the bleed in\nthe message.\n\u003C\u002Finstalled>\n","\u003Cstraw-dog question=\"q-yiygh6\">Mechanism: not yet\u003C\u002Fstraw-dog>\n\n- Look at pending changes; group them by content aligning with origin topic, ticket, rfc or change type (documentation, code, CI, skills).\n\n- Separate implementation and documentation commits.\n\n- Write the subject in the project's convention: the one it states, else the one its tooling enforces, else the one its recent history keeps; a project with none of these, Conventional Commits.\n\n- In case the file changes belong to several groups, commit the file with the group forming its dominant topic and mention the bleed in that commit's message.\n\n- Do not reference sessions in commit comments, sessions are ephemeral.\n\n- Unless already working in branch or instructed to branch - commit to default branch.\n\n- Work the person holds back stays on its own branch, never merged into the shared main until they\n  release it: whatever stands on main may be published.\n\n- When committing a code change, first run the checks the repository defines for itself — its\n  linter, its formatter in check mode, its type checker, its tests. Pure doc changes need none\n  of them. **Read them from where the project states them; never carry them here.** A commit\n  skill holding a project's commands is a second home for them, and it is wrong for every\n  project but the one it was written in.\n\n- Commit when the work closes — `\u002Fverify` has passed on it. Push as the project's local file states\n  its way of working with git; a push is never implied by a commit.\n\n\u003Cinstalled by=\"session\">\n**S5** Commit the work of the current session only: another session's changes may be its work in\nprogress, and in doubt ask the person. Work on a unit this session took over is its own, the\nholder's uncommitted changes to it included. Commit with the paths named, `git commit -- \u003Cfile>…`,\neach one this session wrote or moved, and stage nothing ahead of the commit; never a directory, a\nglob, `-A` or a bare `git commit` — in a tree where other sessions run, the index is shared.\n\u003C\u002Finstalled>\n\n\u003Cinstalled by=\"local\">\n**L8** Prefix the subject with the loop step that produced the work, uppercase, then a colon — one of\nthese and no other: `ALIGN`, `TICKET`, `PLAN`, `IMPLEMENT`, `VERIFY`, `MAINTAIN`,\n`DISCOVER`, `RECALL`, `CONCLUDE`; outside the ring, `FIX` for a repair taken on its own, `EQUIP`\nfor a change to the harness's own installation, `DREAM` for a record the second lobe wrote. A\nname for what the commit touched — the entry file, the local rules, the question store, an RFC —\nis not a step: a rule landed at an align is `ALIGN`, a question opened while planning is `PLAN`.\nOne prefix per commit; where the work spans two steps, take the dominant one and name the bleed in\nthe message.\n\u003C\u002Finstalled>\n",{"name":5,"description":7},"main","a43633f7ef0eeeb220f42872be487150daec8575",".agents\u002Fskills\u002Fcommit","https:\u002F\u002Fgithub.com\u002Fdveyarangi\u002Fgoodwolf-harness","https:\u002F\u002Fgithub.com\u002Fdveyarangi","http:\u002F\u002Fdveyarangi.blogspot.com\u002F","2026-11-14 12:09:52",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add dveyarangi\u002Fgoodwolf-harness --skill commit",{"tool":37,"command":38},"bunx","bunx skills add dveyarangi\u002Fgoodwolf-harness --skill commit",{"tool":40,"command":41},"pnpm","pnpm dlx skills add dveyarangi\u002Fgoodwolf-harness --skill commit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdveyarangi\u002Fgoodwolf-harness\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcommit\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":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M7CDYHDFRAZP8T121PGMZ46R","verify","Use after an implementation pass, or to verify a landed slice before close. Whole verification of landed work: ticket, RFC, governing docs, and the project's verification set.","https:\u002F\u002Fgithub.com\u002Fdveyarangi\u002Fgoodwolf-harness\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fverify\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7CDYES9QW4N2JZ8GX1Q9DMV","ticket","Use to decompose a parent work into independently-workable child tickets. Use to mint ticket(s), possibly a single one, when planning implementation without one.","https:\u002F\u002Fgithub.com\u002Fdveyarangi\u002Fgoodwolf-harness\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fticket\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7CDYB6CFM7PD0APTBBS17HH","tdd","Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions \"red-green-refactor\", wants integration tests, or asks for test-first development.","https:\u002F\u002Fgithub.com\u002Fdveyarangi\u002Fgoodwolf-harness\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftdd\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7CDY7V9VR5DDC0TPXQRB6K1","skill-up","Aid agent skill creation or modification. Use when creating a new skill or changing an existing one. Use whenever writing any agent instructions, whether to a file or directly in a reply.","https:\u002F\u002Fgithub.com\u002Fdveyarangi\u002Fgoodwolf-harness\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fskill-up\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7CDY4B01RZP7Y90JGTCHNY5","setup-devops","Set up the project's engineering scaffolding, from toolchain to CICD and observability. Use when initializing a repo or filling a setup gap.","https:\u002F\u002Fgithub.com\u002Fdveyarangi\u002Fgoodwolf-harness\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsetup-devops\u002FSKILL.md",[],[],{"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":87,"publishedAt":19},"01M7CDY1P8T9VT2W2ZXEH1H4PR","review-architecture","Explore the codebase for module-deepening opportunities — architectural improvements that raise testability and navigability. Use when asked to improve or refactor the architecture.","https:\u002F\u002Fgithub.com\u002Fdveyarangi\u002Fgoodwolf-harness\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Freview-architecture\u002FSKILL.md",[],[]]