[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79BMSKPEX2DM62JE1TG0SKM":3,"skill-same:01M79BMSKPEX2DM62JE1TG0SKM":53},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M79BMSKPEX2DM62JE1TG0SKM","git-advanced",null,"Advanced git operations including rebase, bisect, cherry-pick, and conflict resolution. Use when rebasing branches, debugging with bisect, cherry-picking commits, or resolving complex merge conflicts.","sahil-kaushik1\u002FAuditing-Workflow","sahil-kaushik1","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F143880923?v=4","01M79BEEK3947RQYD3WC00K9W3","Sahil Kaushik","01M79BEEKVHPFPTNBDB0GFXBHE",0,"MIT","https:\u002F\u002Fgithub.com\u002Fsahil-kaushik1\u002FAuditing-Workflow\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fgit-advanced\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: git-advanced\ndescription: Advanced git operations including rebase, bisect, cherry-pick, and conflict resolution. Use when rebasing branches, debugging with bisect, cherry-picking commits, or resolving complex merge conflicts.\nallowed-tools: Read, Bash, Grep\n---\n\n# Git Advanced Skill\n\n## Purpose\n\nProvide guidance for advanced git operations with safety considerations. This project uses a **rebase-first workflow** with linear history—understand these patterns to avoid breaking the codebase.\n\n## When This Skill Applies\n\nInvoke this skill when:\n\n- Rebasing feature branches onto dev\n- Using git bisect to find bugs\n- Cherry-picking commits between branches\n- Resolving complex merge conflicts\n- Recovering from git mistakes\n\n## Stop-the-Line Conditions\n\n### FORBIDDEN Operations\n\n```bash\n# FORBIDDEN: Force push to protected branches\ngit push --force origin dev    # ❌ NEVER\ngit push --force origin master # ❌ NEVER\n\n# FORBIDDEN: Merge commits on dev branch\ngit merge feature-branch       # ❌ Use rebase-and-merge PR strategy\n\n# FORBIDDEN: Skip pre-commit hooks\ngit commit --no-verify         # ❌ Hooks exist for a reason\n\n# FORBIDDEN: Rewriting shared history\ngit rebase -i HEAD~5 && git push --force  # ❌ If already pushed\n```\n\n### SAFE Operations\n\n```bash\n# SAFE: Force-with-lease on your feature branch\ngit push --force-with-lease origin {{TICKET_PREFIX}}-XXX-feature  # ✅ Safe\n\n# SAFE: Interactive rebase before first push\ngit rebase -i origin\u002Fdev   # ✅ Squash\u002Fclean local commits\n\n# SAFE: Force push after conflict resolution\ngit rebase origin\u002Fdev && git push --force-with-lease origin {{TICKET_PREFIX}}-XXX-feature\n```\n\n## Rebase Workflow (Standard)\n\n### Before Creating PR\n\n```bash\n# 1. Fetch latest changes\ngit fetch origin dev\n\n# 2. Rebase onto latest dev\ngit rebase origin\u002Fdev\n\n# 3. If conflicts, resolve them\ngit status                   # See conflicted files\n# ... edit files to resolve ...\ngit add \u003Cresolved-files>\ngit rebase --continue\n\n# 4. Push with force-with-lease\ngit push --force-with-lease origin {{TICKET_PREFIX}}-XXX-feature\n```\n\n### During PR Review (After Feedback)\n\n```bash\n# 1. Make requested changes\ngit add . && git commit -m \"fix: address PR feedback [{{TICKET_PREFIX}}-XXX]\"\n\n# 2. Fetch and rebase again\ngit fetch origin dev\ngit rebase origin\u002Fdev\n\n# 3. Push update\ngit push --force-with-lease origin {{TICKET_PREFIX}}-XXX-feature\n```\n\n## Git Bisect (Finding Bugs)\n\n### When to Use\n\nUse bisect when you know a bug was introduced at some point but don't know which commit.\n\n### Bisect Workflow\n\n```bash\n# 1. Start bisect\ngit bisect start\n\n# 2. Mark current state (has bug)\ngit bisect bad\n\n# 3. Mark a known good commit\ngit bisect good \u003Ccommit-sha>\n# e.g., git bisect good abc1234\n\n# 4. Git checks out middle commit - test it\nyarn test:unit  # or manual test\n\n# 5. Tell git if this commit is good or bad\ngit bisect good  # or\ngit bisect bad\n\n# 6. Repeat until found\n# Git will tell you the first bad commit\n\n# 7. End bisect\ngit bisect reset\n```\n\n### Automated Bisect\n\n```bash\n# Run a test script automatically\ngit bisect start HEAD abc1234\ngit bisect run yarn test:specific-test\n```\n\n## Cherry-Pick (Selective Commits)\n\n### When to Use\n\n- Backporting a fix to an older branch\n- Pulling a specific commit from one branch to another\n- Selective feature extraction\n\n### Cherry-Pick Workflow\n\n```bash\n# 1. Find the commit SHA\ngit log --oneline branch-name | head -20\n\n# 2. Cherry-pick to current branch\ngit cherry-pick \u003Ccommit-sha>\n\n# 3. If conflicts, resolve them\ngit status\n# ... resolve conflicts ...\ngit add \u003Cresolved-files>\ngit cherry-pick --continue\n\n# 4. Push the result\ngit push origin current-branch\n```\n\n### Cherry-Pick Multiple Commits\n\n```bash\n# Range of commits (oldest..newest, exclusive of oldest)\ngit cherry-pick abc123^..def456\n\n# Specific commits\ngit cherry-pick abc123 def456 ghi789\n```\n\n## Conflict Resolution\n\n### Common Conflict Scenarios\n\n| Scenario                 | Resolution Strategy             |\n| ------------------------ | ------------------------------- |\n| Same line edited         | Choose one version or combine   |\n| File deleted vs modified | Decide: keep modified or delete |\n| Rename conflicts         | Decide which name to use        |\n| Binary file conflicts    | Choose one version explicitly   |\n\n### Conflict Resolution Steps\n\n```bash\n# 1. See what's conflicted\ngit status\n\n# 2. Open conflicted file, look for markers\n\u003C\u003C\u003C\u003C\u003C\u003C\u003C HEAD\nyour changes\n=======\ntheir changes\n>>>>>>> branch-name\n\n# 3. Edit file to resolve (remove markers, keep correct code)\n\n# 4. Mark as resolved\ngit add \u003Cresolved-file>\n\n# 5. Continue rebase\u002Fmerge\ngit rebase --continue\n# or\ngit merge --continue\n```\n\n### Conflict Prevention\n\n```bash\n# Rebase frequently to avoid large conflicts\ngit fetch origin dev\ngit rebase origin\u002Fdev  # Do this daily during long features\n\n# Check for potential conflicts before rebase\ngit diff origin\u002Fdev...HEAD --stat\n```\n\n## Recovery Commands\n\n### Abort Operations\n\n```bash\n# Abort rebase\ngit rebase --abort\n\n# Abort merge\ngit merge --abort\n\n# Abort cherry-pick\ngit cherry-pick --abort\n```\n\n### Undo Last Commit\n\n```bash\n# Keep changes staged\ngit reset --soft HEAD~1\n\n# Keep changes unstaged\ngit reset HEAD~1\n\n# Discard changes (DANGEROUS)\ngit reset --hard HEAD~1\n```\n\n### Recover Lost Commits\n\n```bash\n# Find lost commits in reflog\ngit reflog\n\n# Restore to a specific state\ngit reset --hard HEAD@{n}\n\n# Cherry-pick a lost commit\ngit cherry-pick \u003Csha-from-reflog>\n```\n\n## Safety Guidelines\n\n### When to Ask Before Force Push\n\n**ALWAYS ask first if:**\n\n- You've pushed commits that others might have pulled\n- You're working on a shared branch\n- You're not 100% sure what will happen\n- The branch has been open for > 1 week\n\n### Safe Force Push Pattern\n\n```bash\n# 1. Verify you're on correct branch\ngit branch\n\n# 2. Verify what will be pushed\ngit log origin\u002F{{TICKET_PREFIX}}-XXX-feature..HEAD --oneline\n\n# 3. Use force-with-lease (protects against overwriting others' work)\ngit push --force-with-lease origin {{TICKET_PREFIX}}-XXX-feature\n```\n\n### Pre-Push Checklist\n\n- [ ] Running `yarn ci:validate` passes\n- [ ] On correct branch (not dev or master)\n- [ ] Commits have proper message format\n- [ ] No sensitive data in commits\n\n## Related Resources\n\n- **CONTRIBUTING.md**: Branch naming and commit format\n- **safe-workflow skill**: Complete workflow patterns\n- **release-patterns skill**: PR and merge patterns\n","# Git Advanced Skill\n\n## Purpose\n\nProvide guidance for advanced git operations with safety considerations. This project uses a **rebase-first workflow** with linear history—understand these patterns to avoid breaking the codebase.\n\n## When This Skill Applies\n\nInvoke this skill when:\n\n- Rebasing feature branches onto dev\n- Using git bisect to find bugs\n- Cherry-picking commits between branches\n- Resolving complex merge conflicts\n- Recovering from git mistakes\n\n## Stop-the-Line Conditions\n\n### FORBIDDEN Operations\n\n```bash\n# FORBIDDEN: Force push to protected branches\ngit push --force origin dev    # ❌ NEVER\ngit push --force origin master # ❌ NEVER\n\n# FORBIDDEN: Merge commits on dev branch\ngit merge feature-branch       # ❌ Use rebase-and-merge PR strategy\n\n# FORBIDDEN: Skip pre-commit hooks\ngit commit --no-verify         # ❌ Hooks exist for a reason\n\n# FORBIDDEN: Rewriting shared history\ngit rebase -i HEAD~5 && git push --force  # ❌ If already pushed\n```\n\n### SAFE Operations\n\n```bash\n# SAFE: Force-with-lease on your feature branch\ngit push --force-with-lease origin {{TICKET_PREFIX}}-XXX-feature  # ✅ Safe\n\n# SAFE: Interactive rebase before first push\ngit rebase -i origin\u002Fdev   # ✅ Squash\u002Fclean local commits\n\n# SAFE: Force push after conflict resolution\ngit rebase origin\u002Fdev && git push --force-with-lease origin {{TICKET_PREFIX}}-XXX-feature\n```\n\n## Rebase Workflow (Standard)\n\n### Before Creating PR\n\n```bash\n# 1. Fetch latest changes\ngit fetch origin dev\n\n# 2. Rebase onto latest dev\ngit rebase origin\u002Fdev\n\n# 3. If conflicts, resolve them\ngit status                   # See conflicted files\n# ... edit files to resolve ...\ngit add \u003Cresolved-files>\ngit rebase --continue\n\n# 4. Push with force-with-lease\ngit push --force-with-lease origin {{TICKET_PREFIX}}-XXX-feature\n```\n\n### During PR Review (After Feedback)\n\n```bash\n# 1. Make requested changes\ngit add . && git commit -m \"fix: address PR feedback [{{TICKET_PREFIX}}-XXX]\"\n\n# 2. Fetch and rebase again\ngit fetch origin dev\ngit rebase origin\u002Fdev\n\n# 3. Push update\ngit push --force-with-lease origin {{TICKET_PREFIX}}-XXX-feature\n```\n\n## Git Bisect (Finding Bugs)\n\n### When to Use\n\nUse bisect when you know a bug was introduced at some point but don't know which commit.\n\n### Bisect Workflow\n\n```bash\n# 1. Start bisect\ngit bisect start\n\n# 2. Mark current state (has bug)\ngit bisect bad\n\n# 3. Mark a known good commit\ngit bisect good \u003Ccommit-sha>\n# e.g., git bisect good abc1234\n\n# 4. Git checks out middle commit - test it\nyarn test:unit  # or manual test\n\n# 5. Tell git if this commit is good or bad\ngit bisect good  # or\ngit bisect bad\n\n# 6. Repeat until found\n# Git will tell you the first bad commit\n\n# 7. End bisect\ngit bisect reset\n```\n\n### Automated Bisect\n\n```bash\n# Run a test script automatically\ngit bisect start HEAD abc1234\ngit bisect run yarn test:specific-test\n```\n\n## Cherry-Pick (Selective Commits)\n\n### When to Use\n\n- Backporting a fix to an older branch\n- Pulling a specific commit from one branch to another\n- Selective feature extraction\n\n### Cherry-Pick Workflow\n\n```bash\n# 1. Find the commit SHA\ngit log --oneline branch-name | head -20\n\n# 2. Cherry-pick to current branch\ngit cherry-pick \u003Ccommit-sha>\n\n# 3. If conflicts, resolve them\ngit status\n# ... resolve conflicts ...\ngit add \u003Cresolved-files>\ngit cherry-pick --continue\n\n# 4. Push the result\ngit push origin current-branch\n```\n\n### Cherry-Pick Multiple Commits\n\n```bash\n# Range of commits (oldest..newest, exclusive of oldest)\ngit cherry-pick abc123^..def456\n\n# Specific commits\ngit cherry-pick abc123 def456 ghi789\n```\n\n## Conflict Resolution\n\n### Common Conflict Scenarios\n\n| Scenario                 | Resolution Strategy             |\n| ------------------------ | ------------------------------- |\n| Same line edited         | Choose one version or combine   |\n| File deleted vs modified | Decide: keep modified or delete |\n| Rename conflicts         | Decide which name to use        |\n| Binary file conflicts    | Choose one version explicitly   |\n\n### Conflict Resolution Steps\n\n```bash\n# 1. See what's conflicted\ngit status\n\n# 2. Open conflicted file, look for markers\n\u003C\u003C\u003C\u003C\u003C\u003C\u003C HEAD\nyour changes\n=======\ntheir changes\n>>>>>>> branch-name\n\n# 3. Edit file to resolve (remove markers, keep correct code)\n\n# 4. Mark as resolved\ngit add \u003Cresolved-file>\n\n# 5. Continue rebase\u002Fmerge\ngit rebase --continue\n# or\ngit merge --continue\n```\n\n### Conflict Prevention\n\n```bash\n# Rebase frequently to avoid large conflicts\ngit fetch origin dev\ngit rebase origin\u002Fdev  # Do this daily during long features\n\n# Check for potential conflicts before rebase\ngit diff origin\u002Fdev...HEAD --stat\n```\n\n## Recovery Commands\n\n### Abort Operations\n\n```bash\n# Abort rebase\ngit rebase --abort\n\n# Abort merge\ngit merge --abort\n\n# Abort cherry-pick\ngit cherry-pick --abort\n```\n\n### Undo Last Commit\n\n```bash\n# Keep changes staged\ngit reset --soft HEAD~1\n\n# Keep changes unstaged\ngit reset HEAD~1\n\n# Discard changes (DANGEROUS)\ngit reset --hard HEAD~1\n```\n\n### Recover Lost Commits\n\n```bash\n# Find lost commits in reflog\ngit reflog\n\n# Restore to a specific state\ngit reset --hard HEAD@{n}\n\n# Cherry-pick a lost commit\ngit cherry-pick \u003Csha-from-reflog>\n```\n\n## Safety Guidelines\n\n### When to Ask Before Force Push\n\n**ALWAYS ask first if:**\n\n- You've pushed commits that others might have pulled\n- You're working on a shared branch\n- You're not 100% sure what will happen\n- The branch has been open for > 1 week\n\n### Safe Force Push Pattern\n\n```bash\n# 1. Verify you're on correct branch\ngit branch\n\n# 2. Verify what will be pushed\ngit log origin\u002F{{TICKET_PREFIX}}-XXX-feature..HEAD --oneline\n\n# 3. Use force-with-lease (protects against overwriting others' work)\ngit push --force-with-lease origin {{TICKET_PREFIX}}-XXX-feature\n```\n\n### Pre-Push Checklist\n\n- [ ] Running `yarn ci:validate` passes\n- [ ] On correct branch (not dev or master)\n- [ ] Commits have proper message format\n- [ ] No sensitive data in commits\n\n## Related Resources\n\n- **CONTRIBUTING.md**: Branch naming and commit format\n- **safe-workflow skill**: Complete workflow patterns\n- **release-patterns skill**: PR and merge patterns\n",{"name":5,"description":7,"allowed-tools":24},"Read, Bash, Grep","main","39a25d63191d67efe43cdce5b7507069e2307f0f",".claude\u002Fskills\u002Fgit-advanced","https:\u002F\u002Fgithub.com\u002Fsahil-kaushik1\u002FAuditing-Workflow","https:\u002F\u002Fgithub.com\u002Fsahil-kaushik1","https:\u002F\u002Fdrive.google.com\u002Ffile\u002Fd\u002F1Te4TcrpgcN4j8DsYqVdjPl4QXVbs5XXo\u002Fview?usp=drive_link","Web3 security researcher \u002F developer","2026-10-18 15:17:21",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add sahil-kaushik1\u002FAuditing-Workflow --skill git-advanced",{"tool":39,"command":40},"bunx","bunx skills add sahil-kaushik1\u002FAuditing-Workflow --skill git-advanced",{"tool":42,"command":43},"pnpm","pnpm dlx skills add sahil-kaushik1\u002FAuditing-Workflow --skill git-advanced","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsahil-kaushik1\u002FAuditing-Workflow\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fgit-advanced\u002FSKILL.md",true,[47],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"README.md","REFERENCE","参考文档",1592,"https:\u002F\u002Fgithub.com\u002Fsahil-kaushik1\u002FAuditing-Workflow\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fgit-advanced\u002FREADME.md",[54,60,66,73,80,87],{"skillNo":55,"name":56,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M79BSEAG0SS9CC2EN1S51K2X","stripe-patterns","https:\u002F\u002Fgithub.com\u002Fsahil-kaushik1\u002FAuditing-Workflow\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fsync\u002Frendertrust\u002F.claude\u002Fskills\u002Fstripe-patterns\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M79BSBAZXQBWCPKYJP38A35B","payment-patterns","https:\u002F\u002Fgithub.com\u002Fsahil-kaushik1\u002FAuditing-Workflow\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fsync\u002Fkeryk-ai\u002F.claude\u002Fskills\u002Fpayment-patterns\u002FSKILL.md",[],[],{"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":72,"publishedAt":19},"01M79BS8PKZXFGBNQBS2GHNXZW","testing-patterns","Testing patterns for Jest and Playwright. Use when writing tests, setting up test fixtures, or validating RLS enforcement. Routes to existing test conventions.","https:\u002F\u002Fgithub.com\u002Fsahil-kaushik1\u002FAuditing-Workflow\u002Fblob\u002Fmain\u002F.gemini\u002Fskills\u002Ftesting-patterns\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M79BS3PR92A4QNEJAFNDKB2G","team-coordination","Agent Teams orchestration patterns for multi-agent SAFe workflows. Use when spawning agent teams, coordinating teammates, enforcing quality gates via task dependencies, or orchestrating the 11-agent SAFe pipeline. Covers team creation, messaging, shared task lists, and SAFe gate enforcement. Do NOT use for single-agent or simple subagent workflows.","https:\u002F\u002Fgithub.com\u002Fsahil-kaushik1\u002FAuditing-Workflow\u002Fblob\u002Fmain\u002F.gemini\u002Fskills\u002Fteam-coordination\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M79BRZ422QD8D5QHQMXAVPWZ","task-compilation","Compile broad audit goals into structured proof obligations with 9 mandatory fields. Used after decomposition by the Threat Modeler agent.","https:\u002F\u002Fgithub.com\u002Fsahil-kaushik1\u002FAuditing-Workflow\u002Fblob\u002Fmain\u002F.gemini\u002Fskills\u002Ftask-compilation\u002FSKILL.md",[],[],{"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":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M79BRV2MK2AJZBNSE2BETP28","storage-layout-analysis","Proxy patterns, slot collisions, upgrade safety. Used during decomposition to identify storage-related vulnerabilities in upgradeable contracts.","https:\u002F\u002Fgithub.com\u002Fsahil-kaushik1\u002FAuditing-Workflow\u002Fblob\u002Fmain\u002F.gemini\u002Fskills\u002Fstorage-layout-analysis\u002FSKILL.md",[],[]]