[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77JFEWG3BVT19H2DGTKX52P":3,"skill-same:01M77JFEWG3BVT19H2DGTKX52P":49},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"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":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":32,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M77JFEWG3BVT19H2DGTKX52P","speckit-git-commit",null,"Auto-commit changes after a Spec Kit command completes","Kemetra\u002FSeshat-BI","Kemetra","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F206601658?v=4","01M77J5APND9QAJK8XMBH5B1A8","01M77J5AR4TM1GN2G4GS5KH02J",2,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FKemetra\u002FSeshat-BI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fspeckit-git-commit\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: speckit-git-commit\ndescription: Auto-commit changes after a Spec Kit command completes\ncompatibility: Requires spec-kit project structure with .specify\u002F directory\nmetadata:\n  author: github-spec-kit\n  source: git:commands\u002Fspeckit.git.commit.md\n---\n\n# Auto-Commit Changes\n\nAutomatically stage and commit all changes after a Spec Kit command completes.\n\n## Behavior\n\nThis command is invoked as a hook after (or before) core commands. It:\n\n1. Determines the event name from the hook context (e.g., if invoked as an `after_specify` hook, the event is `after_specify`; if `before_plan`, the event is `before_plan`)\n2. Checks `.specify\u002Fextensions\u002Fgit\u002Fgit-config.yml` for the `auto_commit` section\n3. Looks up the specific event key to see if auto-commit is enabled\n4. Falls back to `auto_commit.default` if no event-specific key exists\n5. Uses the per-command `message` if configured, otherwise a default message\n6. If enabled and there are uncommitted changes, runs `git add .` + `git commit`\n\n## Execution\n\nDetermine the event name from the hook that triggered this command, then run the script:\n\n- **Bash**: `.specify\u002Fextensions\u002Fgit\u002Fscripts\u002Fbash\u002Fauto-commit.sh \u003Cevent_name>`\n- **PowerShell**: `.specify\u002Fextensions\u002Fgit\u002Fscripts\u002Fpowershell\u002Fauto-commit.ps1 \u003Cevent_name>`\n\nReplace `\u003Cevent_name>` with the actual hook event (e.g., `after_specify`, `before_plan`, `after_implement`).\n\n## Configuration\n\nIn `.specify\u002Fextensions\u002Fgit\u002Fgit-config.yml`:\n\n```yaml\nauto_commit:\n  default: false          # Global toggle — set true to enable for all commands\n  after_specify:\n    enabled: true          # Override per-command\n    message: \"[Spec Kit] Add specification\"\n  after_plan:\n    enabled: false\n    message: \"[Spec Kit] Add implementation plan\"\n```\n\n## Graceful Degradation\n\n- If Git is not available or the current directory is not a repository: skips with a warning\n- If no config file exists: skips (disabled by default)\n- If no changes to commit: skips with a message","# Auto-Commit Changes\n\nAutomatically stage and commit all changes after a Spec Kit command completes.\n\n## Behavior\n\nThis command is invoked as a hook after (or before) core commands. It:\n\n1. Determines the event name from the hook context (e.g., if invoked as an `after_specify` hook, the event is `after_specify`; if `before_plan`, the event is `before_plan`)\n2. Checks `.specify\u002Fextensions\u002Fgit\u002Fgit-config.yml` for the `auto_commit` section\n3. Looks up the specific event key to see if auto-commit is enabled\n4. Falls back to `auto_commit.default` if no event-specific key exists\n5. Uses the per-command `message` if configured, otherwise a default message\n6. If enabled and there are uncommitted changes, runs `git add .` + `git commit`\n\n## Execution\n\nDetermine the event name from the hook that triggered this command, then run the script:\n\n- **Bash**: `.specify\u002Fextensions\u002Fgit\u002Fscripts\u002Fbash\u002Fauto-commit.sh \u003Cevent_name>`\n- **PowerShell**: `.specify\u002Fextensions\u002Fgit\u002Fscripts\u002Fpowershell\u002Fauto-commit.ps1 \u003Cevent_name>`\n\nReplace `\u003Cevent_name>` with the actual hook event (e.g., `after_specify`, `before_plan`, `after_implement`).\n\n## Configuration\n\nIn `.specify\u002Fextensions\u002Fgit\u002Fgit-config.yml`:\n\n```yaml\nauto_commit:\n  default: false          # Global toggle — set true to enable for all commands\n  after_specify:\n    enabled: true          # Override per-command\n    message: \"[Spec Kit] Add specification\"\n  after_plan:\n    enabled: false\n    message: \"[Spec Kit] Add implementation plan\"\n```\n\n## Graceful Degradation\n\n- If Git is not available or the current directory is not a repository: skips with a warning\n- If no config file exists: skips (disabled by default)\n- If no changes to commit: skips with a message",{"name":5,"metadata":23,"description":7,"compatibility":26},{"author":24,"source":25},"github-spec-kit","git:commands\u002Fspeckit.git.commit.md","Requires spec-kit project structure with .specify\u002F directory","main","6266e304556a72b75d951b9433fd833481c61233",".claude\u002Fskills\u002Fspeckit-git-commit",0,"https:\u002F\u002Fgithub.com\u002FKemetra\u002FSeshat-BI","https:\u002F\u002Fpypi.org\u002Fproject\u002Fseshat-bi\u002F","https:\u002F\u002Fgithub.com\u002FKemetra","2026-11-11 21:44:25",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add Kemetra\u002FSeshat-BI --skill speckit-git-commit",{"tool":41,"command":42},"bunx","bunx skills add Kemetra\u002FSeshat-BI --skill speckit-git-commit",{"tool":44,"command":45},"pnpm","pnpm dlx skills add Kemetra\u002FSeshat-BI --skill speckit-git-commit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FKemetra\u002FSeshat-BI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fspeckit-git-commit\u002FSKILL.md",true,[],[50,57,62,68,73,80],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":18},"01M77JWCTJ88JWPDD25WZ2NEY8","fake-skill","A fixture skill with declaring frontmatter, used as positive shipped evidence.","https:\u002F\u002Fgithub.com\u002FKemetra\u002FSeshat-BI\u002Fblob\u002Fmain\u002Ftests\u002Funit\u002Ffixtures\u002Fcapability_inventory\u002Funlisted\u002F.claude\u002Fskills\u002Ffake-skill\u002FSKILL.md",[],[],{"skillNo":58,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":18},"01M77JWA0BTG4JB2HR52Q99216","https:\u002F\u002Fgithub.com\u002FKemetra\u002FSeshat-BI\u002Fblob\u002Fmain\u002Ftests\u002Funit\u002Ffixtures\u002Fcapability_inventory\u002Forphan\u002F.claude\u002Fskills\u002Ffake-skill\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M77JW6VE59XEFHWBTNDYAS2Q","bare-skill-no-frontmatter","https:\u002F\u002Fgithub.com\u002FKemetra\u002FSeshat-BI\u002Fblob\u002Fmain\u002Ftests\u002Funit\u002Ffixtures\u002Fcapability_inventory\u002Forphan\u002F.claude\u002Fskills\u002Fbare-skill-no-frontmatter\u002FSKILL.md",[],[],{"skillNo":69,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M77JW4TD1FNFSBNP5C0WXAA5","https:\u002F\u002Fgithub.com\u002FKemetra\u002FSeshat-BI\u002Fblob\u002Fmain\u002Ftests\u002Funit\u002Ffixtures\u002Fcapability_inventory\u002Fgood\u002F.claude\u002Fskills\u002Ffake-skill\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M77JVWCVE3WZ82ZNFCSFVDCP","retail-kpi-knowledge","Retail KPI \u002F metric-contract reasoning layer for BI agents in the Seshat BI project. Use when an agent must reason about the BUSINESS MEANING of a retail KPI before any implementation — defining a KPI in business terms, classifying additivity (fully\u002Fsemi\u002Fnon-additive), identifying grain, listing required source fields, resolving ambiguity (gross vs net, VAT, returns, cost method, same-store), choosing an MVP KPI pack, reviewing a metric contract for completeness, or preparing a clean handoff to an implementation layer. Also use it to classify KPI sufficiency or prepare an owner policy decision packet. This is a meaning\u002Fdefinition + review layer, not an executor: it does not write DAX\u002FSQL\u002FPython, grant readiness, approve policy, or design dashboards. See INDEX.md for live\u002Fplanned routes; registry.yaml is the authoritative machine-readable inventory.","https:\u002F\u002Fgithub.com\u002FKemetra\u002FSeshat-BI\u002Fblob\u002Fmain\u002Fskills\u002Fretail-kpi-knowledge\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M77JVNDM1NGYGSCPTBW9ZCF5","bi-sql-knowledge","SQL reasoning, validation, reconciliation, transformation, diagnostics, and anti-pattern knowledge layer for Seshat BI agents. Use when a task involves reasoning about source SQL: source profiling, table grain, keys & uniqueness, joins & fan-out amplification, aggregation correctness, COUNT\u002FNULL semantics, deduplication, validation queries, reconciliation queries, silver\u002Fgold transformation logic, window\u002Fdate-time analytics, SQL anti-patterns, or basic SQL performance reasoning, or interpretation of a supplied sanitized PostgreSQL JSON execution plan. The SQL counterpart to bi-dax-knowledge. It is a thinking & validation layer, not a database executor, runtime validator, dbt\u002FDagster project, or automatic tuning service.","https:\u002F\u002Fgithub.com\u002FKemetra\u002FSeshat-BI\u002Fblob\u002Fmain\u002Fskills\u002Fbi-sql-knowledge\u002FSKILL.md",[],[]]