[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6XDB7007K4749CC3DSCNKD5":3,"skill-same:01M6XDB7007K4749CC3DSCNKD5":65},{"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":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":14,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":6,"ownerDescription":49,"updatedAt":50,"install":51,"resources":64},"01M6XDB7007K4749CC3DSCNKD5","git",null,"Project-aware git workflow: conventional commits, PR creation, safe pushes, PR merges, and branch naming suggestions. Triggers on: \"conventional commit\", \"create PR\", \"push changes\".","kaiohenricunha\u002Fdotbabel","kaiohenricunha","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F69804490?v=4","01M6XCZD37W0KPCDGEA40Y610V","Kaio Cunha","01M6XCZD7SX714D114H3ZPNW09",0,"MIT","https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fplugins\u002Fdotbabel\u002Ftemplates\u002Fclaude\u002Fskills\u002Fgit\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36],"conventional commit","changes","naming","triggers","creation","pr creation","project","conventional commits","branch","commits","safe","push","create","git workflow","pr","create pr","commit","workflow","2026-11-10 10:12:30",false,"---\n# dotbabel:generated projection=sha256:7bd1a3fe52419bc14d34dc27e4041cab833338a0f620dd29a0ad5337e137b37b source=skills\u002Fgit\u002FSKILL.md — do not edit directly\nargument-hint: \"[subcommand]\"\ndescription: |\n  Project-aware git workflow: conventional commits, PR creation, safe pushes, PR merges, and branch naming suggestions. Triggers on: \"conventional commit\", \"create PR\", \"push changes\".\nname: git\n---\n\n# \u002Fgit\n\nA project-aware git workflow command: craft conventional commits, create PRs, push with the right safety rails, merge into main, and suggest branch names.\n\n## Your Domain\n\n| Component | Responsibility                                 |\n| --------- | ---------------------------------------------- |\n| Commits   | Craft precise, conventional commit messages    |\n| Staging   | Smart `git add` with awareness of what changed |\n| PRs       | Generate PR descriptions with `\u002Fgit pr`        |\n| Branches  | Branch suggestions with `\u002Fgit suggest`         |\n| Merging   | Merge to main with `\u002Fgit main`                 |\n| Pushing   | Smart push with `\u002Fgit push`                    |\n| History   | Log analysis, blame, bisect                    |\n\n## Primary Command: Auto-Commit\n\nWhen invoked without a subcommand, execute this workflow:\n\n### Step 1: Analyze Changes\n\n```bash\ngit status --porcelain\ngit diff --stat\ngit diff --cached --stat\n```\n\n### Step 2: Understand the Changes\n\nRead the diff to understand:\n\n- **What** files changed (which area: app code, docs, tests, infra)\n- **Why** they changed (feature, fix, refactor, docs, test, chore)\n- **Scope** of change (single file, single feature, multiple concerns)\n\n### Step 3: Stage\n\nPrefer staging specific files by name rather than `git add .` or `git add -A`. Only stage what's part of this logical change. If there are unrelated pending changes, surface them and ask.\n\n### Step 4: Craft Commit Message\n\nUse **Conventional Commits** format:\n\n```text\n\u003Ctype>(\u003Cscope>): \u003Csubject>\n\n[optional body]\n\n[optional footer]\n```\n\n#### Types\n\n| Type       | When to Use                              |\n| ---------- | ---------------------------------------- |\n| `feat`     | New feature or capability                |\n| `fix`      | Bug fix                                  |\n| `refactor` | Code change that neither fixes nor adds  |\n| `docs`     | Documentation only                       |\n| `test`     | Adding or updating tests                 |\n| `chore`    | Maintenance, deps, config                |\n| `style`    | Formatting, whitespace (no logic change) |\n| `perf`     | Performance improvement                  |\n| `ci`       | CI \u002F workflow changes                    |\n\n#### Scopes\n\nInfer the scope from the top-level directory or domain concept touched (e.g., `api`, `frontend`, `config`, `docs`, `deps`). If the repo has a CLAUDE.md or CONTRIBUTING.md section listing allowed scopes, follow that. Otherwise, a short area tag is fine.\n\n#### Subject Rules\n\n- **Imperative mood**: \"add feature\" not \"added feature\"\n- **No period** at the end\n- **≤72 characters** for the subject line (50 preferred)\n- **Lowercase** first letter\n\n### Step 5: Execute Commit\n\n```bash\ngit commit -m \"\u003Ccrafted message>\"\n```\n\n### Step 6: Confirm\n\nOutput:\n\n```text\nCommitted: \u003Chash>\nMessage:   \u003Ctype>(\u003Cscope>): \u003Csubject>\nFiles:     \u003Ccount> changed\n```\n\n---\n\n## Message Crafting Examples\n\n### Single File Change\n\n```bash\ngit commit -m \"feat(config): add staging environment configuration\"\n```\n\n### Multiple Related Files\n\n```bash\ngit commit -m \"feat(api): implement user profile endpoint\"\n```\n\n### Bug Fix\n\n```bash\ngit commit -m \"fix(storage): ensure timestamps use timezone-aware UTC\"\n```\n\n### Documentation\n\n```bash\ngit commit -m \"docs: mark Phase 2 as complete\"\n```\n\n### Refactor\n\n```bash\ngit commit -m \"refactor(config): extract resolver helper function\"\n```\n\n---\n\n## Multi-Concern Detection\n\nIf `git diff` shows unrelated changes, warn:\n\n```text\nDetected multiple unrelated changes:\n   - \u003Cfile-a> (bug fix)\n   - \u003Cfile-b> (docs update)\n\nRecommendation: commit separately for clean history.\n\nProceed with combined commit? [y\u002FN]\n```\n\nIf the user confirms, use a multi-line commit body that lists each concern.\n\n---\n\n## Action: `\u002Fgit main`\n\nCheckout main and merge the previous branch into it.\n\n```bash\nPREVIOUS_BRANCH=$(git branch --show-current)\ngit checkout main\ngit pull origin main\ngit merge \"$PREVIOUS_BRANCH\"\n```\n\n**Error handling:**\n\n- If merge conflicts occur, report them and do NOT auto-resolve.\n- If the working directory is dirty, warn and abort.\n- If the repo has an explicit rule against committing on main directly (e.g., CLAUDE.md requiring worktrees or PRs), stop and escalate.\n\n---\n\n## Action: `\u002Fgit push`\n\nPush the current branch, using `--force-with-lease` when history has diverged (post-rebase or post-amend).\n\n```bash\nBRANCH=$(git branch --show-current)\ngit fetch origin\n\nLOCAL=$(git rev-parse @)\nREMOTE=$(git rev-parse @{u} 2>\u002Fdev\u002Fnull || echo \"none\")\nBASE=$(git merge-base @ @{u} 2>\u002Fdev\u002Fnull || echo \"none\")\n\nif [ \"$REMOTE\" = \"none\" ]; then\n    git push -u origin \"$BRANCH\"\nelif [ \"$LOCAL\" = \"$REMOTE\" ]; then\n    echo \"Already up to date with remote\"\nelif [ \"$BASE\" = \"$REMOTE\" ]; then\n    git push origin \"$BRANCH\"\nelse\n    echo \"Branch has diverged from remote, using --force-with-lease\"\n    git push --force-with-lease origin \"$BRANCH\"\nfi\n```\n\n**Safety rules:**\n\n- **Never** `--force` without `--with-lease`.\n- **Never** force push `main` or `master` without explicit user confirmation.\n- Warn if pushing to a protected branch.\n\n---\n\n## Action: `\u002Fgit main push`\n\nCombined: merge into main, then push main.\n\n```bash\nPREVIOUS_BRANCH=$(git branch --show-current)\ngit checkout main\ngit pull origin main\ngit merge \"$PREVIOUS_BRANCH\"\ngit push origin main\n```\n\n---\n\n## Action: `\u002Fgit pr`\n\nCreate a PR with an auto-generated description.\n\n```bash\ngit push -u origin \"$(git branch --show-current)\"\nBRANCH=$(git branch --show-current)\nBASE=\"main\"\ngit log \"$BASE..$BRANCH\" --oneline\ngit diff \"$BASE...$BRANCH\" --stat\ngh pr create --title \"\u003Cgenerated-title>\" --body \"\u003Cgenerated-body>\"\n```\n\n**Task state.** If this worktree has an open task (`dotbabel task list`), record the pull request on it: `dotbabel task update \u003Cslug> --phase pr --decision \"PR #\u003CN>\"`. Under `\u002Fpr-conductor`, the conductor records the later phases. When there is no task, or `dotbabel` is not installed, skip this step.\n\n**Title rules:**\n\n- Use conventional-commit style: `\u003Ctype>(\u003Cscope>): \u003Csubject>`.\n- Derive from branch name or most significant commit.\n\n**Body template:**\n\n```markdown\n## Summary\n\n\u003C2-3 bullets describing what this PR does>\n\n## Changes\n\n\u003CList of key files or areas modified>\n\n## Testing\n\n- [ ] Unit tests pass (\u003Cdetected test command, e.g. `npm test`, `pytest`, `go test .\u002F...`>)\n- [ ] Manual verification completed\n- [ ] No regressions introduced\n\n## Related\n\n- Closes #\u003Cissue> (if applicable)\n- Part of: \u003Cmilestone> (if applicable)\n```\n\n---\n\n## Action: `\u002Fgit suggest`\n\nSuggest a branch name for the next unit of work.\n\n1. **Scan planning documents** for next incomplete tasks. Common locations: `docs\u002Froadmap.md`, `docs\u002Fplans\u002F*.md`, `TODO.md`, or GitHub issues via `gh issue list --state=open`.\n\n2. **Identify the next task** by looking for:\n   - Items marked `[ ]` following items marked `[x]`\n   - Phase\u002Fmilestone boundaries\n   - Priority indicators\n\n3. **Generate a branch name** using:\n\n```text\n\u003Ctype>\u002F\u003Cscope>-\u003Cshort-description>\n```\n\n| Type        | Usage                 |\n| ----------- | --------------------- |\n| `feat\u002F`     | New features          |\n| `fix\u002F`      | Bug fixes             |\n| `refactor\u002F` | Code restructuring    |\n| `docs\u002F`     | Documentation updates |\n| `test\u002F`     | Test additions        |\n| `chore\u002F`    | Maintenance tasks     |\n| `ci\u002F`       | CI\u002Fworkflow changes   |\n\nScope should match the area conventions used in this repo (detect from recent branch names or CLAUDE.md).\n\n---\n\n## Hard Rules\n\n1. **Never commit secrets.** Check for `.env`, credentials, API keys, tokens in staged files before each commit.\n2. **Never force push main or master** without explicit confirmation.\n3. **Conventional commits** format, always.\n4. **Atomic commits.** One logical change per commit where possible.\n5. **Imperative mood** in subjects (\"add\" not \"added\").\n6. **Respect project rules.** If the repo's CLAUDE.md or equivalent forbids committing on main, or requires worktrees, or demands a PR, follow that over this command's default flow.\n\n---\n\n## Quick Reference\n\n```bash\n\u002Fgit              # stage + commit with crafted message\n\u002Fgit main         # merge current branch into main\n\u002Fgit push         # push current branch (with --force-with-lease when diverged)\n\u002Fgit main push    # merge into main AND push\n\u002Fgit pr           # create a PR with auto-generated description\n\u002Fgit suggest      # suggest next branch name from planning docs\n```\n\n---\n\n## Safety Checks (always run before committing)\n\n```bash\n# Potential secrets\ngit diff --cached | grep -iE \"(api_key|secret|password|token|bearer|ghp_|sk-[A-Za-z0-9]{20,})\" && echo \"SECRETS SUSPECTED\"\n\n# Large additions\ngit diff --cached --stat | grep -E \"\\+[0-9]{4,}\" && echo \"Large addition detected\"\n\n# Binary blobs\ngit diff --cached --numstat | grep \"^-\" && echo \"Binary file detected\"\n```\n","# \u002Fgit\n\nA project-aware git workflow command: craft conventional commits, create PRs, push with the right safety rails, merge into main, and suggest branch names.\n\n## Your Domain\n\n| Component | Responsibility                                 |\n| --------- | ---------------------------------------------- |\n| Commits   | Craft precise, conventional commit messages    |\n| Staging   | Smart `git add` with awareness of what changed |\n| PRs       | Generate PR descriptions with `\u002Fgit pr`        |\n| Branches  | Branch suggestions with `\u002Fgit suggest`         |\n| Merging   | Merge to main with `\u002Fgit main`                 |\n| Pushing   | Smart push with `\u002Fgit push`                    |\n| History   | Log analysis, blame, bisect                    |\n\n## Primary Command: Auto-Commit\n\nWhen invoked without a subcommand, execute this workflow:\n\n### Step 1: Analyze Changes\n\n```bash\ngit status --porcelain\ngit diff --stat\ngit diff --cached --stat\n```\n\n### Step 2: Understand the Changes\n\nRead the diff to understand:\n\n- **What** files changed (which area: app code, docs, tests, infra)\n- **Why** they changed (feature, fix, refactor, docs, test, chore)\n- **Scope** of change (single file, single feature, multiple concerns)\n\n### Step 3: Stage\n\nPrefer staging specific files by name rather than `git add .` or `git add -A`. Only stage what's part of this logical change. If there are unrelated pending changes, surface them and ask.\n\n### Step 4: Craft Commit Message\n\nUse **Conventional Commits** format:\n\n```text\n\u003Ctype>(\u003Cscope>): \u003Csubject>\n\n[optional body]\n\n[optional footer]\n```\n\n#### Types\n\n| Type       | When to Use                              |\n| ---------- | ---------------------------------------- |\n| `feat`     | New feature or capability                |\n| `fix`      | Bug fix                                  |\n| `refactor` | Code change that neither fixes nor adds  |\n| `docs`     | Documentation only                       |\n| `test`     | Adding or updating tests                 |\n| `chore`    | Maintenance, deps, config                |\n| `style`    | Formatting, whitespace (no logic change) |\n| `perf`     | Performance improvement                  |\n| `ci`       | CI \u002F workflow changes                    |\n\n#### Scopes\n\nInfer the scope from the top-level directory or domain concept touched (e.g., `api`, `frontend`, `config`, `docs`, `deps`). If the repo has a CLAUDE.md or CONTRIBUTING.md section listing allowed scopes, follow that. Otherwise, a short area tag is fine.\n\n#### Subject Rules\n\n- **Imperative mood**: \"add feature\" not \"added feature\"\n- **No period** at the end\n- **≤72 characters** for the subject line (50 preferred)\n- **Lowercase** first letter\n\n### Step 5: Execute Commit\n\n```bash\ngit commit -m \"\u003Ccrafted message>\"\n```\n\n### Step 6: Confirm\n\nOutput:\n\n```text\nCommitted: \u003Chash>\nMessage:   \u003Ctype>(\u003Cscope>): \u003Csubject>\nFiles:     \u003Ccount> changed\n```\n\n---\n\n## Message Crafting Examples\n\n### Single File Change\n\n```bash\ngit commit -m \"feat(config): add staging environment configuration\"\n```\n\n### Multiple Related Files\n\n```bash\ngit commit -m \"feat(api): implement user profile endpoint\"\n```\n\n### Bug Fix\n\n```bash\ngit commit -m \"fix(storage): ensure timestamps use timezone-aware UTC\"\n```\n\n### Documentation\n\n```bash\ngit commit -m \"docs: mark Phase 2 as complete\"\n```\n\n### Refactor\n\n```bash\ngit commit -m \"refactor(config): extract resolver helper function\"\n```\n\n---\n\n## Multi-Concern Detection\n\nIf `git diff` shows unrelated changes, warn:\n\n```text\nDetected multiple unrelated changes:\n   - \u003Cfile-a> (bug fix)\n   - \u003Cfile-b> (docs update)\n\nRecommendation: commit separately for clean history.\n\nProceed with combined commit? [y\u002FN]\n```\n\nIf the user confirms, use a multi-line commit body that lists each concern.\n\n---\n\n## Action: `\u002Fgit main`\n\nCheckout main and merge the previous branch into it.\n\n```bash\nPREVIOUS_BRANCH=$(git branch --show-current)\ngit checkout main\ngit pull origin main\ngit merge \"$PREVIOUS_BRANCH\"\n```\n\n**Error handling:**\n\n- If merge conflicts occur, report them and do NOT auto-resolve.\n- If the working directory is dirty, warn and abort.\n- If the repo has an explicit rule against committing on main directly (e.g., CLAUDE.md requiring worktrees or PRs), stop and escalate.\n\n---\n\n## Action: `\u002Fgit push`\n\nPush the current branch, using `--force-with-lease` when history has diverged (post-rebase or post-amend).\n\n```bash\nBRANCH=$(git branch --show-current)\ngit fetch origin\n\nLOCAL=$(git rev-parse @)\nREMOTE=$(git rev-parse @{u} 2>\u002Fdev\u002Fnull || echo \"none\")\nBASE=$(git merge-base @ @{u} 2>\u002Fdev\u002Fnull || echo \"none\")\n\nif [ \"$REMOTE\" = \"none\" ]; then\n    git push -u origin \"$BRANCH\"\nelif [ \"$LOCAL\" = \"$REMOTE\" ]; then\n    echo \"Already up to date with remote\"\nelif [ \"$BASE\" = \"$REMOTE\" ]; then\n    git push origin \"$BRANCH\"\nelse\n    echo \"Branch has diverged from remote, using --force-with-lease\"\n    git push --force-with-lease origin \"$BRANCH\"\nfi\n```\n\n**Safety rules:**\n\n- **Never** `--force` without `--with-lease`.\n- **Never** force push `main` or `master` without explicit user confirmation.\n- Warn if pushing to a protected branch.\n\n---\n\n## Action: `\u002Fgit main push`\n\nCombined: merge into main, then push main.\n\n```bash\nPREVIOUS_BRANCH=$(git branch --show-current)\ngit checkout main\ngit pull origin main\ngit merge \"$PREVIOUS_BRANCH\"\ngit push origin main\n```\n\n---\n\n## Action: `\u002Fgit pr`\n\nCreate a PR with an auto-generated description.\n\n```bash\ngit push -u origin \"$(git branch --show-current)\"\nBRANCH=$(git branch --show-current)\nBASE=\"main\"\ngit log \"$BASE..$BRANCH\" --oneline\ngit diff \"$BASE...$BRANCH\" --stat\ngh pr create --title \"\u003Cgenerated-title>\" --body \"\u003Cgenerated-body>\"\n```\n\n**Task state.** If this worktree has an open task (`dotbabel task list`), record the pull request on it: `dotbabel task update \u003Cslug> --phase pr --decision \"PR #\u003CN>\"`. Under `\u002Fpr-conductor`, the conductor records the later phases. When there is no task, or `dotbabel` is not installed, skip this step.\n\n**Title rules:**\n\n- Use conventional-commit style: `\u003Ctype>(\u003Cscope>): \u003Csubject>`.\n- Derive from branch name or most significant commit.\n\n**Body template:**\n\n```markdown\n## Summary\n\n\u003C2-3 bullets describing what this PR does>\n\n## Changes\n\n\u003CList of key files or areas modified>\n\n## Testing\n\n- [ ] Unit tests pass (\u003Cdetected test command, e.g. `npm test`, `pytest`, `go test .\u002F...`>)\n- [ ] Manual verification completed\n- [ ] No regressions introduced\n\n## Related\n\n- Closes #\u003Cissue> (if applicable)\n- Part of: \u003Cmilestone> (if applicable)\n```\n\n---\n\n## Action: `\u002Fgit suggest`\n\nSuggest a branch name for the next unit of work.\n\n1. **Scan planning documents** for next incomplete tasks. Common locations: `docs\u002Froadmap.md`, `docs\u002Fplans\u002F*.md`, `TODO.md`, or GitHub issues via `gh issue list --state=open`.\n\n2. **Identify the next task** by looking for:\n   - Items marked `[ ]` following items marked `[x]`\n   - Phase\u002Fmilestone boundaries\n   - Priority indicators\n\n3. **Generate a branch name** using:\n\n```text\n\u003Ctype>\u002F\u003Cscope>-\u003Cshort-description>\n```\n\n| Type        | Usage                 |\n| ----------- | --------------------- |\n| `feat\u002F`     | New features          |\n| `fix\u002F`      | Bug fixes             |\n| `refactor\u002F` | Code restructuring    |\n| `docs\u002F`     | Documentation updates |\n| `test\u002F`     | Test additions        |\n| `chore\u002F`    | Maintenance tasks     |\n| `ci\u002F`       | CI\u002Fworkflow changes   |\n\nScope should match the area conventions used in this repo (detect from recent branch names or CLAUDE.md).\n\n---\n\n## Hard Rules\n\n1. **Never commit secrets.** Check for `.env`, credentials, API keys, tokens in staged files before each commit.\n2. **Never force push main or master** without explicit confirmation.\n3. **Conventional commits** format, always.\n4. **Atomic commits.** One logical change per commit where possible.\n5. **Imperative mood** in subjects (\"add\" not \"added\").\n6. **Respect project rules.** If the repo's CLAUDE.md or equivalent forbids committing on main, or requires worktrees, or demands a PR, follow that over this command's default flow.\n\n---\n\n## Quick Reference\n\n```bash\n\u002Fgit              # stage + commit with crafted message\n\u002Fgit main         # merge current branch into main\n\u002Fgit push         # push current branch (with --force-with-lease when diverged)\n\u002Fgit main push    # merge into main AND push\n\u002Fgit pr           # create a PR with auto-generated description\n\u002Fgit suggest      # suggest next branch name from planning docs\n```\n\n---\n\n## Safety Checks (always run before committing)\n\n```bash\n# Potential secrets\ngit diff --cached | grep -iE \"(api_key|secret|password|token|bearer|ghp_|sk-[A-Za-z0-9]{20,})\" && echo \"SECRETS SUSPECTED\"\n\n# Large additions\ngit diff --cached --stat | grep -E \"\\+[0-9]{4,}\" && echo \"Large addition detected\"\n\n# Binary blobs\ngit diff --cached --numstat | grep \"^-\" && echo \"Binary file detected\"\n```\n",{"name":5,"description":42,"argument-hint":43},"Project-aware git workflow: conventional commits, PR creation, safe pushes, PR merges, and branch naming suggestions. Triggers on: \"conventional commit\", \"create PR\", \"push changes\".\n","[subcommand]","main","91c337164997b99943fbcc64e8e362577b67bc81","plugins\u002Fdotbabel\u002Ftemplates\u002Fclaude\u002Fskills\u002Fgit","https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel","https:\u002F\u002Fgithub.com\u002Fkaiohenricunha","I'm a Platform\u002FInfra engineer who happens to work in cybersec and write Go code.","2026-10-26 14:12:51",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add kaiohenricunha\u002Fdotbabel --skill git",{"tool":57,"command":58},"bunx","bunx skills add kaiohenricunha\u002Fdotbabel --skill git",{"tool":60,"command":61},"pnpm","pnpm dlx skills add kaiohenricunha\u002Fdotbabel --skill git","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fplugins\u002Fdotbabel\u002Ftemplates\u002Fclaude\u002Fskills\u002Fgit\u002FSKILL.md",true,[],[66,97,130,152,174,197],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":77,"publishedAt":37},"01M6XDQ7QMASPFZ355MYKCD06T","yolo","Start temporary autonomy for the current task or an explicit scope with a required --for expiry. Codex permits scoped pushes, merges, deploys, and releases after strict testing and validation; Full access is a separate runtime setting. Claude Code uses a session permission hook with a protected-action denylist.","https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fskills\u002Fyolo\u002FSKILL.md",[72],{"categoryNo":73,"categoryName":74,"taxonomyType":75,"taxonomyTypeDesc":76},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[68,78,79,80,81,82,83,84,85,86,87,88,89,90,91,92,93,94,95,96],"testing","merge","code","start","access","session","ops","autonomy","releases","permission","full","runtime","scope","devex","hook","true","action","for","scoped",{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":111,"publishedAt":37},"01M6XDQ1N21VE4KH98JWGZ7GN9","veracity-audit","Audit a data pipeline for Veracity and Value. Dispatches data-scientist, compliance-auditor, and data-engineer agents with project context injected at dispatch time. All source paths are supplied via flags — no defaults, no project assumptions. Subcommands: audit (full pipeline walk), score-check (scoring math only), gate-check (gate coverage only), source-trace \u003Clabel> (single source end-to-end). Invoke when: \"audit pipeline\", \"veracity check\", \"scoring math correct?\", \"check gates\", \"trace source\", \"verify quality gates\", \"formula correct?\".","https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fskills\u002Fveracity-audit\u002FSKILL.md",[103,108],{"categoryNo":104,"categoryName":105,"taxonomyType":106,"taxonomyTypeDesc":107},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":109,"categoryName":110,"taxonomyType":75,"taxonomyTypeDesc":76},"01JBSEEDCAT000000000000037","律师与法务",[112,113,78,114,115,116,117,118,119,120,121,122,123,124,25,125,126,127,128,129],"audit","veracity audit","review","data pipeline","pipeline","Bash","math","coverage","only","engineer","formula","scoring","time","worker","end","at","invoke","when",{"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":136,"publishedAt":37},"01M6XDPVDKBR376C06CEK9BC5S","validate-spec","Audit an already-implemented spec against the codebase. Walks each constraint (ARCH-N, PERF-N, KD-N, etc.) and acceptance criterion, grounds findings in file:line evidence, runs the spec.json acceptance_commands, and writes a single audit doc to docs\u002Faudits\u002F. Use whenever the user asks to \"validate a spec\", \"audit a spec\", \"check if spec is implemented\", \"verify the spec is done\", \"is this spec really done\", or otherwise wants closure on spec-driven work. Read-only against the spec — produces an audit, never modifies the spec itself.","https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fskills\u002Fvalidate-spec\u002FSKILL.md",[],[137,138,139,78,114,140,141,112,117,142,143,144,120,145,146,147,148,149,150,151],"spec","validate","validate spec","run","acceptance","work","read","never","max","done","arch","line","2025","spec-driven","closure",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":161,"publishedAt":37},"01M6XDPMMECH82RAW553Y94HDS","terragrunt-specialist","Deep-dive Terragrunt hierarchy review, DRY pattern audits, and run-all orchestration analysis. Use for structured investigations of multi-environment Terragrunt layouts, dependency graphs, remote state config, and hook correctness. Triggers on: \"Terragrunt audit\", \"run-all review\", \"dependency block\", \"DRY pattern review\", \"env hierarchy audit\", \"mock_outputs\", \"terragrunt hooks\".","https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fskills\u002Fterragrunt-specialist\u002FSKILL.md",[158],{"categoryNo":159,"categoryName":160,"taxonomyType":106,"taxonomyTypeDesc":107},"01JBSEEDCAT000000000000011","运维与部署",[162,163,164,114,165,166,140,112,167,117,143,168,169,145,170,171,149,172,127,173],"terragrunt","specialist","terragrunt specialist","orchestration","debugging","analysis","dependency","hooks","deep","dry","remote","hierarchy",{"skillNo":175,"name":176,"nameZh":6,"description":177,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":178,"categories":179,"keywords":187,"publishedAt":37},"01M6XDPFJS2HGSE13RXF1HV8S7","terraform-specialist","Deep-dive Terraform architecture review, module design, state management, and migration. Use for structured investigations of Terraform workspaces, provider configuration, module coupling, import workflows, and test coverage. Triggers on: \"Terraform audit\", \"module review\", \"state management\", \"Terraform import\", \"workspace design\", \"provider config review\", \"Terraform testing\".","https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fskills\u002Fterraform-specialist\u002FSKILL.md",[180,183,184],{"categoryNo":181,"categoryName":182,"taxonomyType":106,"taxonomyTypeDesc":107},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":159,"categoryName":160,"taxonomyType":106,"taxonomyTypeDesc":107},{"categoryNo":185,"categoryName":186,"taxonomyType":106,"taxonomyTypeDesc":107},"01JBSEEDCAT000000000000015","视觉设计",[188,189,163,78,190,114,191,192,193,166,112,117,143,119,194,195,170,196,149,127],"terraform","terraform specialist","design","workflows","architecture","architecture review","test coverage","workspaces","problem",{"skillNo":198,"name":137,"nameZh":6,"description":199,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":200,"categories":201,"keywords":206,"publishedAt":37},"01M6XDP7V6H8WYPSXVEKYE6HJ6","Create structured engineering specs through interactive pairing. Use when the user wants to create a spec, design doc, technical specification, architecture document, RFC, or engineering plan. Triggers on \"let's spec this out\", \"create a spec\", \"design doc\", \"write a technical plan\", \"plan the architecture\". Works for greenfield and brownfield projects. Outputs to docs\u002Fspecs\u002F.","https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fskills\u002Fspec\u002FSKILL.md",[202,203],{"categoryNo":185,"categoryName":186,"taxonomyType":106,"taxonomyTypeDesc":107},{"categoryNo":204,"categoryName":205,"taxonomyType":75,"taxonomyTypeDesc":76},"01JBSEEDCAT000000000000032","设计师",[137,190,207,192,31,208,209,210,211,212,213,214,22,215,216,95,217,218,219,220],"component","plan","projects","write","interactive","use","document","specification","opus","technical specification","trade-offs","technical plan","outputs","frontier"]