[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ERS0589GX2VBVC5HF239BW":3,"skill-same:01M6ERS0589GX2VBVC5HF239BW":89},{"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":31,"linkOnly":32,"markdownContent":33,"markdownBody":34,"frontMatter":35,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":39,"repositoryHtmlUrl":40,"repositoryHomepageUrl":6,"ownerHtmlUrl":41,"ownerBlogUrl":42,"ownerDescription":43,"updatedAt":44,"install":45,"resources":58},"01M6ERS0589GX2VBVC5HF239BW","making-commits",null,"Use when ready to commit code changes. Covers conventional commit format, commit sizing, GPG failures, and push safety. Other skills invoke this for commit mechanics.","nocksock\u002Fsuperpowers","nocksock","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F22164?v=4","01M6ERQWRTZARGFM7AX8HB89GZ","Nils Riedemann","01M6ERQWXFH5876Z6HEDH9TWYS",1,"MIT","https:\u002F\u002Fgithub.com\u002Fnocksock\u002Fsuperpowers\u002Fblob\u002Fmain\u002Fskills\u002Fmaking-commits\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30],"commits","making commits","commit","code","push","conventional commit","Safety","format","use","ready","mechanics","gpg","2026-11-10 10:12:30",false,"---\nname: making-commits\ndescription: Use when ready to commit code changes. Covers conventional commit format, commit sizing, GPG failures, and push safety. Other skills invoke this for commit mechanics.\n---\n\n# Making Commits\n\nCommit mechanics when committing is allowed. For WHEN to commit, see `COMMIT_PREFERENCE` in deep-work-session.\n\n**Core principle:** Small, focused commits. Verify first. Never push without asking.\n\n## Explicit Invocation\n\nIf user explicitly asks to commit (not via deep work session) with substantial changes (5+ files):\n\n> \"I see substantial changes. Before committing, what's your preference?\"\n> Options: Single commit \u002F Multiple commits (by logical unit) \u002F Let me review what to include\n\n## Conventional Commit Format\n\n```\ntype(scope): description   # lowercase, imperative, \u003C72 chars, no period\n```\n\n| Type | Use |\n|------|-----|\n| `feat` | New feature |\n| `fix` | Bug fix |\n| `docs` | Documentation only |\n| `refactor` | Neither fix nor feature |\n| `test` | Tests |\n| `chore` | Maintenance |\n\n## Commit Sizing\n\n- One logical change per commit\n- Break up: unrelated changes, bug+feature mixed, refactor+behavior mixed\n- Keep together: test+implementation for same feature\n\n## Pre-Commit\n\n1. **Verify** - Run tests, build if applicable\n2. **Review diff** - `git diff --staged`\n3. **No secrets** - No API keys, passwords, credentials\n4. **No debug code** - No console.log, debugger\n\n**REQUIRED:** superpowers:verification-before-completion for significant changes.\n\n## GPG Signing Failure\n\nIf `gpg failed to sign the data`:\n\n**Use question tool:**\n> \"GPG signing failed. How to proceed?\"\n> Options: Retry \u002F Skip signing (--no-gpg-sign) \u002F Abort\n\n**Never** silently skip or retry.\n\n## Push Safety\n\n**Never push without explicit permission.**\n\n**Use question tool before any push:**\n> \"Ready to push to [remote\u002Fbranch]. Confirm?\"\n> Options: Yes, push \u002F No, don't push\n\n**Force push:** Warn about overwriting remote history, require explicit confirmation.\n\n**Never:**\n- Push automatically after commit\n- Push to main\u002Fmaster without confirmation\n- Force push without warning\n- Push commits you didn't create\n\n## Quick Reference\n\n| Situation | Action |\n|-----------|--------|\n| GPG fails | Ask user (question tool) |\n| Want to push | Ask user (question tool) |\n| Large changeset | Break into smaller commits |\n| Secrets in diff | Remove, never commit |\n\n## Integration\n\n**Delegating skills:** writing-plans, subagent-driven-development, implementer-prompt\n\n**Required:** verification-before-completion (before significant commits)\n\n**Preference system:** `COMMIT_PREFERENCE` = WHETHER to commit; this skill = HOW\n","# Making Commits\n\nCommit mechanics when committing is allowed. For WHEN to commit, see `COMMIT_PREFERENCE` in deep-work-session.\n\n**Core principle:** Small, focused commits. Verify first. Never push without asking.\n\n## Explicit Invocation\n\nIf user explicitly asks to commit (not via deep work session) with substantial changes (5+ files):\n\n> \"I see substantial changes. Before committing, what's your preference?\"\n> Options: Single commit \u002F Multiple commits (by logical unit) \u002F Let me review what to include\n\n## Conventional Commit Format\n\n```\ntype(scope): description   # lowercase, imperative, \u003C72 chars, no period\n```\n\n| Type | Use |\n|------|-----|\n| `feat` | New feature |\n| `fix` | Bug fix |\n| `docs` | Documentation only |\n| `refactor` | Neither fix nor feature |\n| `test` | Tests |\n| `chore` | Maintenance |\n\n## Commit Sizing\n\n- One logical change per commit\n- Break up: unrelated changes, bug+feature mixed, refactor+behavior mixed\n- Keep together: test+implementation for same feature\n\n## Pre-Commit\n\n1. **Verify** - Run tests, build if applicable\n2. **Review diff** - `git diff --staged`\n3. **No secrets** - No API keys, passwords, credentials\n4. **No debug code** - No console.log, debugger\n\n**REQUIRED:** superpowers:verification-before-completion for significant changes.\n\n## GPG Signing Failure\n\nIf `gpg failed to sign the data`:\n\n**Use question tool:**\n> \"GPG signing failed. How to proceed?\"\n> Options: Retry \u002F Skip signing (--no-gpg-sign) \u002F Abort\n\n**Never** silently skip or retry.\n\n## Push Safety\n\n**Never push without explicit permission.**\n\n**Use question tool before any push:**\n> \"Ready to push to [remote\u002Fbranch]. Confirm?\"\n> Options: Yes, push \u002F No, don't push\n\n**Force push:** Warn about overwriting remote history, require explicit confirmation.\n\n**Never:**\n- Push automatically after commit\n- Push to main\u002Fmaster without confirmation\n- Force push without warning\n- Push commits you didn't create\n\n## Quick Reference\n\n| Situation | Action |\n|-----------|--------|\n| GPG fails | Ask user (question tool) |\n| Want to push | Ask user (question tool) |\n| Large changeset | Break into smaller commits |\n| Secrets in diff | Remove, never commit |\n\n## Integration\n\n**Delegating skills:** writing-plans, subagent-driven-development, implementer-prompt\n\n**Required:** verification-before-completion (before significant commits)\n\n**Preference system:** `COMMIT_PREFERENCE` = WHETHER to commit; this skill = HOW\n",{"name":5,"description":7},"main","52d2d5a29297631b5e3ff61fbc8ca3c6505a26e2","skills\u002Fmaking-commits",0,"https:\u002F\u002Fgithub.com\u002Fnocksock\u002Fsuperpowers","https:\u002F\u002Fgithub.com\u002Fnocksock","http:\u002F\u002Fbleepbloop.studio\u002F","Hi, I'm Nils. I build interfaces for the web.","2026-03-19 04:55:50",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add nocksock\u002Fsuperpowers --skill making-commits",{"tool":51,"command":52},"bunx","bunx skills add nocksock\u002Fsuperpowers --skill making-commits",{"tool":54,"command":55},"pnpm","pnpm dlx skills add nocksock\u002Fsuperpowers --skill making-commits","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fnocksock\u002Fsuperpowers\u002Fblob\u002Fmain\u002Fskills\u002Fmaking-commits\u002FSKILL.md",true,[59,65,69,73,77,81,85],{"path":60,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":63,"sourceHtmlUrl":64},"agents\u002Fopenai.yaml","REFERENCE","参考文档",327,"https:\u002F\u002Fgithub.com\u002Fmatt-riley\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsystematic-debugging\u002Fagents\u002Fopenai.yaml",{"path":66,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":67,"sourceHtmlUrl":68},"evals\u002Fevals.json",4675,"https:\u002F\u002Fgithub.com\u002Fmatt-riley\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsystematic-debugging\u002Fevals\u002Fevals.json",{"path":70,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":71,"sourceHtmlUrl":72},"evals\u002Ftrigger-queries.json",1314,"https:\u002F\u002Fgithub.com\u002Fmatt-riley\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsystematic-debugging\u002Fevals\u002Ftrigger-queries.json",{"path":74,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Fdefense-in-depth.md",9042,"https:\u002F\u002Fgithub.com\u002Fmatt-riley\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsystematic-debugging\u002Freferences\u002Fdefense-in-depth.md",{"path":78,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fexamples.md",2024,"https:\u002F\u002Fgithub.com\u002Fmatt-riley\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsystematic-debugging\u002Freferences\u002Fexamples.md",{"path":82,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fphases-and-rationalisations.md",2818,"https:\u002F\u002Fgithub.com\u002Fmatt-riley\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsystematic-debugging\u002Freferences\u002Fphases-and-rationalisations.md",{"path":86,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Froot-cause-tracing.md",8685,"https:\u002F\u002Fgithub.com\u002Fmatt-riley\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsystematic-debugging\u002Freferences\u002Froot-cause-tracing.md",[90,115,130,147,160,171],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":109,"publishedAt":31},"01M6ERV5R58PKM81EH15XEYPMF","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002Fnocksock\u002Fsuperpowers\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[96,101,104],{"categoryNo":97,"categoryName":98,"taxonomyType":99,"taxonomyTypeDesc":100},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":102,"categoryName":103,"taxonomyType":99,"taxonomyTypeDesc":100},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":105,"categoryName":106,"taxonomyType":107,"taxonomyTypeDesc":108},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[110,111,27,112,113,114],"writing skills","writing","deployment","work","editing",{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":123,"publishedAt":31},"01M6ERV2JX5DJV2EHSC6FXHEHN","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002Fnocksock\u002Fsuperpowers\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[121,122],{"categoryNo":102,"categoryName":103,"taxonomyType":99,"taxonomyTypeDesc":100},{"categoryNo":105,"categoryName":106,"taxonomyType":107,"taxonomyTypeDesc":108},[124,125,111,126,22,27,127,128,129],"plans","writing plans","spec","task","requirements","multi",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":141,"publishedAt":31},"01M6ERTZS70NCVS375DTD8HGKE","writing good code","use this skill whenever you write code. it provides a process for creating good, composable apis.","https:\u002F\u002Fgithub.com\u002Fnocksock\u002Fsuperpowers\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-good-code\u002FSKILL.md",[136,137,140],{"categoryNo":102,"categoryName":103,"taxonomyType":99,"taxonomyTypeDesc":100},{"categoryNo":138,"categoryName":139,"taxonomyType":107,"taxonomyTypeDesc":108},"01JBSEEDCAT000000000000030","开发工程师",{"categoryNo":105,"categoryName":106,"taxonomyType":107,"taxonomyTypeDesc":108},[132,142,22,111,143,27,144,145,146],"good","it","process","write","composable",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":153,"publishedAt":31},"01M6ERTVVRPKZVWK6M8EXPB5QE","write-review-elixir","Review Elixir code. ALWAYS use this skill before or after you added code written in elixir to ensure high code quality. Also use use this when asked to review existing elixir code.","https:\u002F\u002Fgithub.com\u002Fnocksock\u002Fsuperpowers\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-or-review-elixir\u002FSKILL.md",[],[154,145,155,156,157,27,158,22,159],"write review elixir","elixir","review","elixir code","quality","code quality",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":166,"publishedAt":31},"01M6ERTRAM8PSJ9JTAW5J4ABFD","whats-next","Answers what to do next, what to work on next, where we're at","https:\u002F\u002Fgithub.com\u002Fnocksock\u002Fsuperpowers\u002Fblob\u002Fmain\u002Fskills\u002Fwhats-next\u002FSKILL.md",[],[167,168,169,113,170],"next","whats next","work on","do",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":175,"categories":176,"keywords":177,"publishedAt":31},"01M6ERTNG9NT8SQH5FHN91JRTS","verification-before-completion","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002Fnocksock\u002Fsuperpowers\u002Fblob\u002Fmain\u002Fskills\u002Fverification-before-completion\u002FSKILL.md",[],[178,179,180,181,182,27,113,183,184,185],"verification before completion","verification","commands","claim","evidence","complete","output","about"]