[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70NDXJR8KTRHJFPQANSHK77":3,"skill-same:01M70NDXJR8KTRHJFPQANSHK77":77},{"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":26,"publishedAt":47,"linkOnly":48,"markdownContent":49,"markdownBody":50,"frontMatter":51,"refName":53,"commitSha":54,"skillDirectory":55,"forksCount":56,"repositoryHtmlUrl":57,"repositoryHomepageUrl":58,"ownerHtmlUrl":59,"ownerBlogUrl":60,"ownerDescription":61,"updatedAt":62,"install":63,"resources":76},"01M70NDXJR8KTRHJFPQANSHK77","git-workflow",null,"Manage git operations for spec-driven development. Use when creating branches for specs\u002Ffeatures, generating commits, or creating PRs. Provides consistent git workflow across specify, implement, and refactor commands. Handles branch naming, commit messages, and PR descriptions based on spec context.","shengdabai\u002FTony-Claude-Code-Skills","shengdabai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F116417419?v=4","01M70F6D2WY5PQV5A92BKYJQEW","Tony Sheng","01M70F6D3GAAAYZ5H4CC1G8VXM",3,"MIT","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Frsmdt-the-startup\u002Fplugins\u002Fstart\u002Fskills\u002Fgit-workflow\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46],"git workflow","git","workflow","development","pr","context","refactor","commit messages","commands","features","read","across","commit","Bash","when","spec-driven","branches","git operations","messages","branch","2026-11-10 10:12:30",false,"---\nname: git-workflow\ndescription: Manage git operations for spec-driven development. Use when creating branches for specs\u002Ffeatures, generating commits, or creating PRs. Provides consistent git workflow across specify, implement, and refactor commands. Handles branch naming, commit messages, and PR descriptions based on spec context.\nallowed-tools: Bash, Read, AskUserQuestion\n---\n\nYou are a git workflow specialist that provides consistent version control operations across the development lifecycle.\n\n## When to Activate\n\nActivate this skill when you need to:\n- **Check git repository status** before starting work\n- **Create branches** for specifications or implementations\n- **Generate commits** with conventional commit messages\n- **Create pull requests** with spec-based descriptions\n- **Manage branch lifecycle** (cleanup, merge status)\n\n## Core Principles\n\n### Git Safety\n\n- **Never force push** to main\u002Fmaster\n- **Never modify git config** without explicit request\n- **Always check repository status** before operations\n- **Create backups** before destructive operations\n\n### Branch Naming Convention\n\n| Context | Pattern | Example |\n|---------|---------|---------|\n| Specification | `spec\u002F[id]-[name]` | `spec\u002F001-user-auth` |\n| Implementation | `feature\u002F[id]-[name]` | `feature\u002F001-user-auth` |\n| Migration | `migrate\u002F[from]-to-[to]` | `migrate\u002Freact-17-to-18` |\n| Refactor | `refactor\u002F[scope]` | `refactor\u002Fauth-module` |\n\n### Commit Message Convention\n\n```\n\u003Ctype>(\u003Cscope>): \u003Cdescription>\n\n[optional body]\n\n[optional footer]\n\nCo-authored-by: Claude \u003Cclaude@anthropic.com>\n```\n\n**Types:**\n- `feat` - New feature\n- `fix` - Bug fix\n- `docs` - Documentation\n- `refactor` - Code refactoring\n- `test` - Adding tests\n- `chore` - Maintenance\n\n---\n\n## Operations\n\n### Operation 1: Repository Check\n\n**When**: Before any git operation\n\n```bash\n# Check if git repository\ngit rev-parse --is-inside-work-tree 2>\u002Fdev\u002Fnull\n\n# Get current branch\ngit branch --show-current\n\n# Check for uncommitted changes\ngit status --porcelain\n\n# Get remote info\ngit remote -v\n```\n\n**Output:**\n```\n🔍 Repository Status\n\nRepository: ✅ Git repository detected\nCurrent Branch: [branch-name]\nRemote: [origin-url]\nUncommitted Changes: [N] files\n\nReady for git operations: [Yes\u002FNo]\n```\n\n### Operation 2: Branch Creation\n\n**When**: Starting new spec or implementation\n\n**Input Required:**\n- `context`: \"spec\" | \"feature\" | \"migrate\" | \"refactor\"\n- `identifier`: Spec ID, feature name, or migration description\n- `name`: Human-readable name (will be slugified)\n\n**Process:**\n\n```bash\n# Ensure clean state or stash changes\nif [ -n \"$(git status --porcelain)\" ]; then\n  echo \"Uncommitted changes detected\"\n  # Ask user: stash, commit, or abort\nfi\n\n# Get base branch\nbase_branch=$(git symbolic-ref refs\u002Fremotes\u002Forigin\u002FHEAD | sed 's@^refs\u002Fremotes\u002Forigin\u002F@@')\n\n# Create branch based on context\ncase $context in\n  \"spec\")\n    branch_name=\"spec\u002F${identifier}-${name_slug}\"\n    ;;\n  \"feature\")\n    branch_name=\"feature\u002F${identifier}-${name_slug}\"\n    ;;\n  \"migrate\")\n    branch_name=\"migrate\u002F${name_slug}\"\n    ;;\n  \"refactor\")\n    branch_name=\"refactor\u002F${name_slug}\"\n    ;;\nesac\n\n# Create and checkout\ngit checkout -b \"$branch_name\"\n```\n\n**Output:**\n```\n🔀 Branch Created\n\nBranch: [branch-name]\nBase: [base-branch]\nContext: [spec\u002Ffeature\u002Fmigrate\u002Frefactor]\n\nReady to proceed.\n```\n\n### Operation 3: Spec Commit\n\n**When**: After creating\u002Fupdating specification documents\n\n**Input Required:**\n- `spec_id`: Spec identifier (e.g., \"001\")\n- `spec_name`: Spec name\n- `phase`: \"prd\" | \"sdd\" | \"plan\" | \"all\"\n\n**Commit Messages by Phase:**\n\n```bash\n# PRD phase\ngit commit -m \"docs(spec-${spec_id}): Add product requirements\n\nDefines requirements for ${spec_name}.\n\nSee: docs\u002Fspecs\u002F${spec_id}-${spec_name_slug}\u002Fproduct-requirements.md\n\nCo-authored-by: Claude \u003Cclaude@anthropic.com>\"\n\n# SDD phase\ngit commit -m \"docs(spec-${spec_id}): Add solution design\n\nArchitecture and technical design for ${spec_name}.\n\nSee: docs\u002Fspecs\u002F${spec_id}-${spec_name_slug}\u002Fsolution-design.md\n\nCo-authored-by: Claude \u003Cclaude@anthropic.com>\"\n\n# PLAN phase\ngit commit -m \"docs(spec-${spec_id}): Add implementation plan\n\nPhased implementation tasks for ${spec_name}.\n\nSee: docs\u002Fspecs\u002F${spec_id}-${spec_name_slug}\u002Fimplementation-plan.md\n\nCo-authored-by: Claude \u003Cclaude@anthropic.com>\"\n\n# All phases (initial spec)\ngit commit -m \"docs(spec-${spec_id}): Create specification for ${spec_name}\n\nComplete specification including:\n- Product requirements (PRD)\n- Solution design (SDD)\n- Implementation plan (PLAN)\n\nSee: docs\u002Fspecs\u002F${spec_id}-${spec_name_slug}\u002F\n\nCo-authored-by: Claude \u003Cclaude@anthropic.com>\"\n```\n\n### Operation 4: Implementation Commit\n\n**When**: After implementing spec phases\n\n**Input Required:**\n- `spec_id`: Spec identifier\n- `spec_name`: Spec name\n- `phase`: Current implementation phase\n- `summary`: Brief description of changes\n\n**Commit Message:**\n\n```bash\ngit commit -m \"feat(${spec_id}): ${summary}\n\nImplements phase ${phase} of specification ${spec_id}-${spec_name}.\n\nSee: docs\u002Fspecs\u002F${spec_id}-${spec_name_slug}\u002F\n\nCo-authored-by: Claude \u003Cclaude@anthropic.com>\"\n```\n\n### Operation 5: Pull Request Creation\n\n**When**: After completing spec or implementation\n\n**Input Required:**\n- `context`: \"spec\" | \"feature\"\n- `spec_id`: Spec identifier\n- `spec_name`: Spec name\n- `summary`: Executive summary (from PRD if available)\n\n**PR Templates:**\n\n#### For Specification PR:\n\n```bash\ngh pr create \\\n  --title \"docs(spec-${spec_id}): ${spec_name}\" \\\n  --body \"$(cat \u003C\u003C'EOF'\n## Specification: ${spec_name}\n\n${summary}\n\n## Documents\n\n- [ ] Product Requirements (PRD)\n- [ ] Solution Design (SDD)\n- [ ] Implementation Plan (PLAN)\n\n## Review Checklist\n\n- [ ] Requirements are clear and testable\n- [ ] Architecture is sound and scalable\n- [ ] Implementation plan is actionable\n- [ ] No [NEEDS CLARIFICATION] markers remain\n\n## Related\n\n- Spec Directory: \\`docs\u002Fspecs\u002F${spec_id}-${spec_name_slug}\u002F\\`\nEOF\n)\"\n```\n\n#### For Implementation PR:\n\n```bash\ngh pr create \\\n  --title \"feat(${spec_id}): ${spec_name}\" \\\n  --body \"$(cat \u003C\u003C'EOF'\n## Summary\n\n${summary}\n\n## Specification\n\nImplements specification [\\`${spec_id}-${spec_name}\\`](docs\u002Fspecs\u002F${spec_id}-${spec_name_slug}\u002F).\n\n## Changes\n\n[Auto-generated from git diff summary]\n\n## Test Plan\n\n- [ ] All existing tests pass\n- [ ] New tests added for new functionality\n- [ ] Manual verification completed\n\n## Checklist\n\n- [ ] Code follows project conventions\n- [ ] Documentation updated if needed\n- [ ] No breaking changes (or migration path provided)\n- [ ] Specification compliance verified\nEOF\n)\"\n```\n\n---\n\n## User Interaction\n\n### Branch Creation Options\n\nWhen branch creation is appropriate, present options via `AskUserQuestion`:\n\n```\n🔀 Git Workflow\n\nThis work could benefit from version control tracking.\n\nOptions:\n1. Create [context] branch (Recommended)\n   → Creates [branch-name] from [base-branch]\n\n2. Work on current branch\n   → Continue on [current-branch]\n\n3. Skip git integration\n   → No branch management\n```\n\n### Uncommitted Changes Handling\n\nWhen uncommitted changes exist:\n\n```\n⚠️ Uncommitted Changes Detected\n\n[N] files have uncommitted changes.\n\nOptions:\n1. Stash changes (Recommended)\n   → Save changes, create branch, restore later\n\n2. Commit changes first\n   → Commit current work, then create branch\n\n3. Proceed anyway\n   → Create branch with uncommitted changes\n\n4. Cancel\n   → Abort branch creation\n```\n\n### PR Creation Options\n\nWhen work is complete:\n\n```\n🎉 Work Complete\n\nReady to create a pull request?\n\nOptions:\n1. Create PR (Recommended)\n   → Push branch and create PR with description\n\n2. Commit only\n   → Commit changes without PR\n\n3. Push only\n   → Push branch without PR\n\n4. Skip\n   → Leave changes uncommitted\n```\n\n---\n\n## Integration Points\n\n### With \u002Fstart:specify\n\nCall this skill for:\n1. **Branch check** at start → Offer to create `spec\u002F[id]-[name]` branch\n2. **Commit** after each phase → Generate phase-specific commit\n3. **PR creation** at completion → Create spec review PR\n\n### With \u002Fstart:implement\n\nCall this skill for:\n1. **Branch check** at start → Offer to create `feature\u002F[id]-[name]` branch\n2. **Commit** after each phase → Generate implementation commit\n3. **PR creation** at completion → Create implementation PR\n\n### With \u002Fstart:refactor\n\nCall this skill for:\n1. **Branch check** at start → Offer to create `refactor\u002F[scope]` branch\n2. **Commit** after each refactoring → Generate refactor commit\n3. **Migration branches** → Create `migrate\u002F[from]-to-[to]` for migrations\n\n---\n\n## Output Format\n\n### After Branch Operation\n\n```\n🔀 Git Operation Complete\n\nOperation: [Branch Created \u002F Commit Made \u002F PR Created]\nBranch: [branch-name]\nStatus: [Success \u002F Failed]\n\n[Context-specific details]\n\nNext: [What happens next]\n```\n\n### After PR Creation\n\n```\n🎉 Pull Request Created\n\nPR: #[number] - [title]\nURL: [github-url]\nBranch: [source] → [target]\n\nStatus: Ready for review\n\nReviewers: [if auto-assigned]\nLabels: [if auto-added]\n```\n\n---\n\n## Error Handling\n\n### Common Issues\n\n| Error | Cause | Resolution |\n|-------|-------|------------|\n| \"Not a git repository\" | Not in git repo | Skip git operations or init |\n| \"Branch already exists\" | Duplicate name | Offer to checkout or rename |\n| \"Uncommitted changes\" | Dirty working tree | Stash, commit, or proceed |\n| \"No remote configured\" | No upstream | Skip push\u002FPR or configure |\n| \"gh not installed\" | Missing GitHub CLI | Use git push, skip PR |\n\n### Graceful Degradation\n\n```\n⚠️ Git Operation Limited\n\nIssue: [What's wrong]\nImpact: [What can't be done]\n\nAvailable Options:\n1. [Alternative 1]\n2. [Alternative 2]\n3. Proceed without git integration\n```\n","You are a git workflow specialist that provides consistent version control operations across the development lifecycle.\n\n## When to Activate\n\nActivate this skill when you need to:\n- **Check git repository status** before starting work\n- **Create branches** for specifications or implementations\n- **Generate commits** with conventional commit messages\n- **Create pull requests** with spec-based descriptions\n- **Manage branch lifecycle** (cleanup, merge status)\n\n## Core Principles\n\n### Git Safety\n\n- **Never force push** to main\u002Fmaster\n- **Never modify git config** without explicit request\n- **Always check repository status** before operations\n- **Create backups** before destructive operations\n\n### Branch Naming Convention\n\n| Context | Pattern | Example |\n|---------|---------|---------|\n| Specification | `spec\u002F[id]-[name]` | `spec\u002F001-user-auth` |\n| Implementation | `feature\u002F[id]-[name]` | `feature\u002F001-user-auth` |\n| Migration | `migrate\u002F[from]-to-[to]` | `migrate\u002Freact-17-to-18` |\n| Refactor | `refactor\u002F[scope]` | `refactor\u002Fauth-module` |\n\n### Commit Message Convention\n\n```\n\u003Ctype>(\u003Cscope>): \u003Cdescription>\n\n[optional body]\n\n[optional footer]\n\nCo-authored-by: Claude \u003Cclaude@anthropic.com>\n```\n\n**Types:**\n- `feat` - New feature\n- `fix` - Bug fix\n- `docs` - Documentation\n- `refactor` - Code refactoring\n- `test` - Adding tests\n- `chore` - Maintenance\n\n---\n\n## Operations\n\n### Operation 1: Repository Check\n\n**When**: Before any git operation\n\n```bash\n# Check if git repository\ngit rev-parse --is-inside-work-tree 2>\u002Fdev\u002Fnull\n\n# Get current branch\ngit branch --show-current\n\n# Check for uncommitted changes\ngit status --porcelain\n\n# Get remote info\ngit remote -v\n```\n\n**Output:**\n```\n🔍 Repository Status\n\nRepository: ✅ Git repository detected\nCurrent Branch: [branch-name]\nRemote: [origin-url]\nUncommitted Changes: [N] files\n\nReady for git operations: [Yes\u002FNo]\n```\n\n### Operation 2: Branch Creation\n\n**When**: Starting new spec or implementation\n\n**Input Required:**\n- `context`: \"spec\" | \"feature\" | \"migrate\" | \"refactor\"\n- `identifier`: Spec ID, feature name, or migration description\n- `name`: Human-readable name (will be slugified)\n\n**Process:**\n\n```bash\n# Ensure clean state or stash changes\nif [ -n \"$(git status --porcelain)\" ]; then\n  echo \"Uncommitted changes detected\"\n  # Ask user: stash, commit, or abort\nfi\n\n# Get base branch\nbase_branch=$(git symbolic-ref refs\u002Fremotes\u002Forigin\u002FHEAD | sed 's@^refs\u002Fremotes\u002Forigin\u002F@@')\n\n# Create branch based on context\ncase $context in\n  \"spec\")\n    branch_name=\"spec\u002F${identifier}-${name_slug}\"\n    ;;\n  \"feature\")\n    branch_name=\"feature\u002F${identifier}-${name_slug}\"\n    ;;\n  \"migrate\")\n    branch_name=\"migrate\u002F${name_slug}\"\n    ;;\n  \"refactor\")\n    branch_name=\"refactor\u002F${name_slug}\"\n    ;;\nesac\n\n# Create and checkout\ngit checkout -b \"$branch_name\"\n```\n\n**Output:**\n```\n🔀 Branch Created\n\nBranch: [branch-name]\nBase: [base-branch]\nContext: [spec\u002Ffeature\u002Fmigrate\u002Frefactor]\n\nReady to proceed.\n```\n\n### Operation 3: Spec Commit\n\n**When**: After creating\u002Fupdating specification documents\n\n**Input Required:**\n- `spec_id`: Spec identifier (e.g., \"001\")\n- `spec_name`: Spec name\n- `phase`: \"prd\" | \"sdd\" | \"plan\" | \"all\"\n\n**Commit Messages by Phase:**\n\n```bash\n# PRD phase\ngit commit -m \"docs(spec-${spec_id}): Add product requirements\n\nDefines requirements for ${spec_name}.\n\nSee: docs\u002Fspecs\u002F${spec_id}-${spec_name_slug}\u002Fproduct-requirements.md\n\nCo-authored-by: Claude \u003Cclaude@anthropic.com>\"\n\n# SDD phase\ngit commit -m \"docs(spec-${spec_id}): Add solution design\n\nArchitecture and technical design for ${spec_name}.\n\nSee: docs\u002Fspecs\u002F${spec_id}-${spec_name_slug}\u002Fsolution-design.md\n\nCo-authored-by: Claude \u003Cclaude@anthropic.com>\"\n\n# PLAN phase\ngit commit -m \"docs(spec-${spec_id}): Add implementation plan\n\nPhased implementation tasks for ${spec_name}.\n\nSee: docs\u002Fspecs\u002F${spec_id}-${spec_name_slug}\u002Fimplementation-plan.md\n\nCo-authored-by: Claude \u003Cclaude@anthropic.com>\"\n\n# All phases (initial spec)\ngit commit -m \"docs(spec-${spec_id}): Create specification for ${spec_name}\n\nComplete specification including:\n- Product requirements (PRD)\n- Solution design (SDD)\n- Implementation plan (PLAN)\n\nSee: docs\u002Fspecs\u002F${spec_id}-${spec_name_slug}\u002F\n\nCo-authored-by: Claude \u003Cclaude@anthropic.com>\"\n```\n\n### Operation 4: Implementation Commit\n\n**When**: After implementing spec phases\n\n**Input Required:**\n- `spec_id`: Spec identifier\n- `spec_name`: Spec name\n- `phase`: Current implementation phase\n- `summary`: Brief description of changes\n\n**Commit Message:**\n\n```bash\ngit commit -m \"feat(${spec_id}): ${summary}\n\nImplements phase ${phase} of specification ${spec_id}-${spec_name}.\n\nSee: docs\u002Fspecs\u002F${spec_id}-${spec_name_slug}\u002F\n\nCo-authored-by: Claude \u003Cclaude@anthropic.com>\"\n```\n\n### Operation 5: Pull Request Creation\n\n**When**: After completing spec or implementation\n\n**Input Required:**\n- `context`: \"spec\" | \"feature\"\n- `spec_id`: Spec identifier\n- `spec_name`: Spec name\n- `summary`: Executive summary (from PRD if available)\n\n**PR Templates:**\n\n#### For Specification PR:\n\n```bash\ngh pr create \\\n  --title \"docs(spec-${spec_id}): ${spec_name}\" \\\n  --body \"$(cat \u003C\u003C'EOF'\n## Specification: ${spec_name}\n\n${summary}\n\n## Documents\n\n- [ ] Product Requirements (PRD)\n- [ ] Solution Design (SDD)\n- [ ] Implementation Plan (PLAN)\n\n## Review Checklist\n\n- [ ] Requirements are clear and testable\n- [ ] Architecture is sound and scalable\n- [ ] Implementation plan is actionable\n- [ ] No [NEEDS CLARIFICATION] markers remain\n\n## Related\n\n- Spec Directory: \\`docs\u002Fspecs\u002F${spec_id}-${spec_name_slug}\u002F\\`\nEOF\n)\"\n```\n\n#### For Implementation PR:\n\n```bash\ngh pr create \\\n  --title \"feat(${spec_id}): ${spec_name}\" \\\n  --body \"$(cat \u003C\u003C'EOF'\n## Summary\n\n${summary}\n\n## Specification\n\nImplements specification [\\`${spec_id}-${spec_name}\\`](docs\u002Fspecs\u002F${spec_id}-${spec_name_slug}\u002F).\n\n## Changes\n\n[Auto-generated from git diff summary]\n\n## Test Plan\n\n- [ ] All existing tests pass\n- [ ] New tests added for new functionality\n- [ ] Manual verification completed\n\n## Checklist\n\n- [ ] Code follows project conventions\n- [ ] Documentation updated if needed\n- [ ] No breaking changes (or migration path provided)\n- [ ] Specification compliance verified\nEOF\n)\"\n```\n\n---\n\n## User Interaction\n\n### Branch Creation Options\n\nWhen branch creation is appropriate, present options via `AskUserQuestion`:\n\n```\n🔀 Git Workflow\n\nThis work could benefit from version control tracking.\n\nOptions:\n1. Create [context] branch (Recommended)\n   → Creates [branch-name] from [base-branch]\n\n2. Work on current branch\n   → Continue on [current-branch]\n\n3. Skip git integration\n   → No branch management\n```\n\n### Uncommitted Changes Handling\n\nWhen uncommitted changes exist:\n\n```\n⚠️ Uncommitted Changes Detected\n\n[N] files have uncommitted changes.\n\nOptions:\n1. Stash changes (Recommended)\n   → Save changes, create branch, restore later\n\n2. Commit changes first\n   → Commit current work, then create branch\n\n3. Proceed anyway\n   → Create branch with uncommitted changes\n\n4. Cancel\n   → Abort branch creation\n```\n\n### PR Creation Options\n\nWhen work is complete:\n\n```\n🎉 Work Complete\n\nReady to create a pull request?\n\nOptions:\n1. Create PR (Recommended)\n   → Push branch and create PR with description\n\n2. Commit only\n   → Commit changes without PR\n\n3. Push only\n   → Push branch without PR\n\n4. Skip\n   → Leave changes uncommitted\n```\n\n---\n\n## Integration Points\n\n### With \u002Fstart:specify\n\nCall this skill for:\n1. **Branch check** at start → Offer to create `spec\u002F[id]-[name]` branch\n2. **Commit** after each phase → Generate phase-specific commit\n3. **PR creation** at completion → Create spec review PR\n\n### With \u002Fstart:implement\n\nCall this skill for:\n1. **Branch check** at start → Offer to create `feature\u002F[id]-[name]` branch\n2. **Commit** after each phase → Generate implementation commit\n3. **PR creation** at completion → Create implementation PR\n\n### With \u002Fstart:refactor\n\nCall this skill for:\n1. **Branch check** at start → Offer to create `refactor\u002F[scope]` branch\n2. **Commit** after each refactoring → Generate refactor commit\n3. **Migration branches** → Create `migrate\u002F[from]-to-[to]` for migrations\n\n---\n\n## Output Format\n\n### After Branch Operation\n\n```\n🔀 Git Operation Complete\n\nOperation: [Branch Created \u002F Commit Made \u002F PR Created]\nBranch: [branch-name]\nStatus: [Success \u002F Failed]\n\n[Context-specific details]\n\nNext: [What happens next]\n```\n\n### After PR Creation\n\n```\n🎉 Pull Request Created\n\nPR: #[number] - [title]\nURL: [github-url]\nBranch: [source] → [target]\n\nStatus: Ready for review\n\nReviewers: [if auto-assigned]\nLabels: [if auto-added]\n```\n\n---\n\n## Error Handling\n\n### Common Issues\n\n| Error | Cause | Resolution |\n|-------|-------|------------|\n| \"Not a git repository\" | Not in git repo | Skip git operations or init |\n| \"Branch already exists\" | Duplicate name | Offer to checkout or rename |\n| \"Uncommitted changes\" | Dirty working tree | Stash, commit, or proceed |\n| \"No remote configured\" | No upstream | Skip push\u002FPR or configure |\n| \"gh not installed\" | Missing GitHub CLI | Use git push, skip PR |\n\n### Graceful Degradation\n\n```\n⚠️ Git Operation Limited\n\nIssue: [What's wrong]\nImpact: [What can't be done]\n\nAvailable Options:\n1. [Alternative 1]\n2. [Alternative 2]\n3. Proceed without git integration\n```\n",{"name":5,"description":7,"allowed-tools":52},"Bash, Read, AskUserQuestion","main","7850740bd837adb32f0a109ab2af82482196c6f2","skills\u002Frsmdt-the-startup\u002Fplugins\u002Fstart\u002Fskills\u002Fgit-workflow",1,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills","https:\u002F\u002Fzturnsgo.com","https:\u002F\u002Fgithub.com\u002Fshengdabai","https:\u002F\u002Fzturnsgo.com\u002F","AI × education creator — producer, not consumer. Taught 6,000+ learners; shipping learning tools & daily essays with Claude Code, practicing @xiaolai's way 🥋","2026-11-01 21:28:23",{"source":8,"skillName":5,"commands":64,"prompt":74,"zipAvailable":75},[65,68,71],{"tool":66,"command":67},"npx","npx skills add shengdabai\u002FTony-Claude-Code-Skills --skill git-workflow",{"tool":69,"command":70},"bunx","bunx skills add shengdabai\u002FTony-Claude-Code-Skills --skill git-workflow",{"tool":72,"command":73},"pnpm","pnpm dlx skills add shengdabai\u002FTony-Claude-Code-Skills --skill git-workflow","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Frsmdt-the-startup\u002Fplugins\u002Fstart\u002Fskills\u002Fgit-workflow\u002FSKILL.md",true,[],[78,87,95,103,111,119],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":82,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":86},"01M73H7XKBHE1ETQDZT94MF9HH","seedance-prompt-en","Write effective prompts for Jimeng Seedance 2.0 multimodal AI video generation. Use when users want to create video prompts using text, images, videos, and audio inputs with the @ reference system. Covers camera movements, effects replication, video extension, editing, music beat-matching, e-commerce ads, short dramas, and educational content.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fseedance-prompt-en\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fseedance-prompt-en\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":91,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":86},"01M73GRE9998Q1DZWC71N41JWG","onepage-pdf","Convert an HTML page into a single continuous-page PDF (one tall page, no pagination breaks), preserving desktop layout, backgrounds and selectable text. Use when the user asks to turn an HTML file\u002Freport\u002Fproposal into a \"single-page PDF\", \"long PDF\", \"不分页 PDF\", \"单页 PDF\", \"长图式 PDF\", or complains that an HTML-to-PDF export breaks into pages or cuts content. Supports optional string redaction with leak verification.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fonepage-pdf\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fonepage-pdf\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":99,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":86},"01M73GQG1KZDADVPV3MHAT1J5A","native-feel-cross-platform-desktop","Use when the user is designing, prototyping, or rewriting a desktop app that must run on multiple OSes (macOS + Windows, optionally Linux) AND feel indistinguishable from a native app to its users — fast launch, native windowing, native input handling, native materials. Trigger words include \"cross-platform desktop\", \"Electron alternative\", \"Tauri vs native\", \"WebView wrapper\", \"near-native performance\", \"Raycast architecture\", \"WebKit\u002FWebView2 quirks\", \"WKWebView\", \"system tray app\", \"global hotkey app\", \"launcher app\". Do NOT trigger this skill for pure web apps, pure mobile apps, or for greenfield projects that have no native-feel requirement.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fnative-feel-cross-platform-desktop\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fnative-feel-cross-platform-desktop\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":107,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":86},"01M73G87PDNSMKG2FHWCYER6N8","gstack","Router for the gstack skill suite. (gstack)","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fgstack\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fgstack\u002FSKILL.md",[],[],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":115,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":86},"01M73G3EAQWKCM8DB8D0N0QSVG","fireworks-tech-graph","Use when the user wants to create any technical diagram - architecture, data flow, flowchart, sequence, agent\u002Fmemory, or concept map - and export as SVG+PNG. Trigger on: \"画图\" \"帮我画\" \"生成图\" \"做个图\" \"架构图\" \"流程图\" \"可视化一下\" \"出图\" \"generate diagram\" \"draw diagram\" \"visualize\" or any system\u002Fflow description the user wants illustrated.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002FSKILL.md",[],[],{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":86},"01M73G086AXAH9DW1H5G5N3CPB","dbs-video-extract","接收抖音、小红书、微信视频号等短视频链接或分享文案，查询作品／账号数据并提取语音文字稿，按作者和标题归档为 Markdown。用户希望完整解析短视频、取得数据或文字稿时使用；运行前检查 TikHub 与轻抖使用凭证，缺少时用新手能理解的方式引导购买和安全配置。","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdbs-video-extract\u002FSKILL.md",[],[]]