[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DEDJXZSN2F4X3A3HCS5RM2":3,"skill-same:01M7DEDJXZSN2F4X3A3HCS5RM2":46},{"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":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7DEDJXZSN2F4X3A3HCS5RM2","pigpen-commit",null,"Read this skill before making git commits","MichaelKinsy\u002Fpigpen","MichaelKinsy","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F54590707?v=4","01M7CYQK2FGYV1482DN7VHACJ6","Michael Kinsy","01M7DEAGVENVX1P76H737CT5FX",18,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FMichaelKinsy\u002Fpigpen\u002Fblob\u002Fmain\u002Fcomponents\u002Fdev-skills\u002Fskills\u002Fpigpen-commit\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: pigpen-commit\ndescription: \"Read this skill before making git commits\"\nlicense: Apache-2.0\n---\n\nAdapted from `skills\u002Fcommit\u002FSKILL.md` of mitsuhiko\u002Fagent-stuff at 0865c84 (Apache-2.0); see\nthe Package's CREDITS.md. **This file was changed from the original:** the body is strongly\nencouraged rather than optional, and the format rules were tightened.\n\nCreate a git commit for the current changes using Conventional Commits format with a **polished, highly descriptive** message.\n\n## Format\n\n`\u003Ctype>(\u003Cscope>): \u003Csummary>`\n\n- `type` REQUIRED. Use `feat` for new features, `fix` for bug fixes. Other common types: `docs`, `refactor`, `chore`, `test`, `perf`.\n- `scope` OPTIONAL. Short noun in parentheses for the affected area (e.g., `api`, `parser`, `ui`).\n- `summary` REQUIRED. Short, imperative, \u003C= 72 chars, no trailing period.\n\n## Notes\n\n- Body is **strongly encouraged** — always include one unless the change is trivially obvious (e.g., fixing a typo). The body should explain **what** changed, **why** it changed, the approach taken, and any notable decisions. A reader of `git log` should understand the change without looking at the diff.\n- Do NOT include breaking-change markers or footers.\n- Do NOT add sign-offs (no `Signed-off-by`), unless the project requires them.\n- Only commit; do NOT push.\n- If it is unclear whether a file should be included, ask the user which files to commit.\n- Treat any caller-provided arguments as additional commit guidance. Common patterns:\n  - Freeform instructions should influence scope, summary, and body.\n  - File paths or globs should limit which files to commit. If files are specified, only stage\u002Fcommit those unless the user explicitly asks otherwise.\n  - If arguments combine files and instructions, honor both.\n\n## Steps\n\n1. Infer from the prompt if the user provided specific file paths\u002Fglobs and\u002For additional instructions.\n2. Review `git status` and `git diff` to understand the current changes (limit to argument-specified files if provided).\n3. (Optional) Run `git log -n 50 --pretty=format:%s` to see commonly used scopes.\n4. If there are ambiguous extra files, ask the user for clarification before committing.\n5. Stage only the intended files (all changes if no files specified).\n6. Run `git commit -m \"\u003Csubject>\"` (and `-m \"\u003Cbody>\"` if needed).\n","Adapted from `skills\u002Fcommit\u002FSKILL.md` of mitsuhiko\u002Fagent-stuff at 0865c84 (Apache-2.0); see\nthe Package's CREDITS.md. **This file was changed from the original:** the body is strongly\nencouraged rather than optional, and the format rules were tightened.\n\nCreate a git commit for the current changes using Conventional Commits format with a **polished, highly descriptive** message.\n\n## Format\n\n`\u003Ctype>(\u003Cscope>): \u003Csummary>`\n\n- `type` REQUIRED. Use `feat` for new features, `fix` for bug fixes. Other common types: `docs`, `refactor`, `chore`, `test`, `perf`.\n- `scope` OPTIONAL. Short noun in parentheses for the affected area (e.g., `api`, `parser`, `ui`).\n- `summary` REQUIRED. Short, imperative, \u003C= 72 chars, no trailing period.\n\n## Notes\n\n- Body is **strongly encouraged** — always include one unless the change is trivially obvious (e.g., fixing a typo). The body should explain **what** changed, **why** it changed, the approach taken, and any notable decisions. A reader of `git log` should understand the change without looking at the diff.\n- Do NOT include breaking-change markers or footers.\n- Do NOT add sign-offs (no `Signed-off-by`), unless the project requires them.\n- Only commit; do NOT push.\n- If it is unclear whether a file should be included, ask the user which files to commit.\n- Treat any caller-provided arguments as additional commit guidance. Common patterns:\n  - Freeform instructions should influence scope, summary, and body.\n  - File paths or globs should limit which files to commit. If files are specified, only stage\u002Fcommit those unless the user explicitly asks otherwise.\n  - If arguments combine files and instructions, honor both.\n\n## Steps\n\n1. Infer from the prompt if the user provided specific file paths\u002Fglobs and\u002For additional instructions.\n2. Review `git status` and `git diff` to understand the current changes (limit to argument-specified files if provided).\n3. (Optional) Run `git log -n 50 --pretty=format:%s` to see commonly used scopes.\n4. If there are ambiguous extra files, ask the user for clarification before committing.\n5. Stage only the intended files (all changes if no files specified).\n6. Run `git commit -m \"\u003Csubject>\"` (and `-m \"\u003Cbody>\"` if needed).\n",{"name":5,"license":15,"description":7},"main","262f2fbc0c721ee470028905399e2cbe1d652847","components\u002Fdev-skills\u002Fskills\u002Fpigpen-commit",5,"https:\u002F\u002Fgithub.com\u002FMichaelKinsy\u002Fpigpen","https:\u002F\u002Fgithub.com\u002FMichaelKinsy","Systems & platform engineer @ HPE | \r\nBSU Alumni 21.              |\r\nBuilding AI\u002Fsoftware infrastructure, tools, and open-source software.","2026-11-15 06:15:23",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add MichaelKinsy\u002Fpigpen --skill pigpen-commit",{"tool":38,"command":39},"bunx","bunx skills add MichaelKinsy\u002Fpigpen --skill pigpen-commit",{"tool":41,"command":42},"pnpm","pnpm dlx skills add MichaelKinsy\u002Fpigpen --skill pigpen-commit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMichaelKinsy\u002Fpigpen\u002Fblob\u002Fmain\u002Fcomponents\u002Fdev-skills\u002Fskills\u002Fpigpen-commit\u002FSKILL.md",true,[],[47,55,62,69,76,83],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":51,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7DEP7TB04M3XJ8Z0NGKW97X","pigpen-superpowers-writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","MIT","https:\u002F\u002Fgithub.com\u002FMichaelKinsy\u002Fpigpen\u002Fblob\u002Fmain\u002Fcomponents\u002Fsuperpowers\u002Fskills\u002Fpigpen-superpowers-writing-skills\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":51,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7DEP3W24SKFVMRYWJQB1073","pigpen-superpowers-writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002FMichaelKinsy\u002Fpigpen\u002Fblob\u002Fmain\u002Fcomponents\u002Fsuperpowers\u002Fskills\u002Fpigpen-superpowers-writing-plans\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":51,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7DENZ1ZPD21VGVXBQKE8Z4F","pigpen-superpowers-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\u002FMichaelKinsy\u002Fpigpen\u002Fblob\u002Fmain\u002Fcomponents\u002Fsuperpowers\u002Fskills\u002Fpigpen-superpowers-verification-before-completion\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":51,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7DENV9CTFN7KAGPA9BEMGQ1","pigpen-superpowers-using-superpowers","Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions","https:\u002F\u002Fgithub.com\u002FMichaelKinsy\u002Fpigpen\u002Fblob\u002Fmain\u002Fcomponents\u002Fsuperpowers\u002Fskills\u002Fpigpen-superpowers-using-superpowers\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":51,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7DENQR56MYZJAAWDEX1YEMZ","pigpen-superpowers-using-git-worktrees","Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback","https:\u002F\u002Fgithub.com\u002FMichaelKinsy\u002Fpigpen\u002Fblob\u002Fmain\u002Fcomponents\u002Fsuperpowers\u002Fskills\u002Fpigpen-superpowers-using-git-worktrees\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":51,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7DENFGH1S9583WWJ4EY9RCN","pigpen-superpowers-test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FMichaelKinsy\u002Fpigpen\u002Fblob\u002Fmain\u002Fcomponents\u002Fsuperpowers\u002Fskills\u002Fpigpen-superpowers-test-driven-development\u002FSKILL.md",[],[]]