[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79W7GV5H252ARY77MBHEGP7":3,"skill-same:01M79W7GV5H252ARY77MBHEGP7":51},{"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":31,"commitSha":32,"skillDirectory":33,"forksCount":13,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":36,"install":37,"resources":50},"01M79W7GV5H252ARY77MBHEGP7","Git Commit Helper",null,"Generate descriptive commit messages by analyzing git diffs. Use when the user asks for help writing commit messages or reviewing staged changes.","KrismithReddy12\u002Fclaude-code-templates","KrismithReddy12","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F182916557?v=4","01M79T8DNGJRHG48G3H3Q02MK8","01M79TA8ZWV2PP7R4ARWVYWZFE",0,"MIT","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fgit-commit-helper\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: Git Commit Helper\ndescription: Generate descriptive commit messages by analyzing git diffs. Use when the user asks for help writing commit messages or reviewing staged changes.\nhooks:\n  PostToolUse:\n    - matcher: \"Bash\"\n      hooks:\n        - type: command\n          command: \"echo \\\"[$(date)] Git Commit Helper: Analyzed git diff for commit message\\\" >> ~\u002F.claude\u002Fgit-commit-helper.log\"\n---\n\n# Git Commit Helper\n\n## Quick start\n\nAnalyze staged changes and generate commit message:\n\n```bash\n# View staged changes\ngit diff --staged\n\n# Generate commit message based on changes\n# (Claude will analyze the diff and suggest a message)\n```\n\n## Commit message format\n\nFollow conventional commits format:\n\n```\n\u003Ctype>(\u003Cscope>): \u003Cdescription>\n\n[optional body]\n\n[optional footer]\n```\n\n### Types\n\n- **feat**: New feature\n- **fix**: Bug fix\n- **docs**: Documentation changes\n- **style**: Code style changes (formatting, missing semicolons)\n- **refactor**: Code refactoring\n- **test**: Adding or updating tests\n- **chore**: Maintenance tasks\n\n### Examples\n\n**Feature commit:**\n```\nfeat(auth): add JWT authentication\n\nImplement JWT-based authentication system with:\n- Login endpoint with token generation\n- Token validation middleware\n- Refresh token support\n```\n\n**Bug fix:**\n```\nfix(api): handle null values in user profile\n\nPrevent crashes when user profile fields are null.\nAdd null checks before accessing nested properties.\n```\n\n**Refactor:**\n```\nrefactor(database): simplify query builder\n\nExtract common query patterns into reusable functions.\nReduce code duplication in database layer.\n```\n\n## Analyzing changes\n\nReview what's being committed:\n\n```bash\n# Show files changed\ngit status\n\n# Show detailed changes\ngit diff --staged\n\n# Show statistics\ngit diff --staged --stat\n\n# Show changes for specific file\ngit diff --staged path\u002Fto\u002Ffile\n```\n\n## Commit message guidelines\n\n**DO:**\n- Use imperative mood (\"add feature\" not \"added feature\")\n- Keep first line under 50 characters\n- Capitalize first letter\n- No period at end of summary\n- Explain WHY not just WHAT in body\n\n**DON'T:**\n- Use vague messages like \"update\" or \"fix stuff\"\n- Include technical implementation details in summary\n- Write paragraphs in summary line\n- Use past tense\n\n## Multi-file commits\n\nWhen committing multiple related changes:\n\n```\nrefactor(core): restructure authentication module\n\n- Move auth logic from controllers to service layer\n- Extract validation into separate validators\n- Update tests to use new structure\n- Add integration tests for auth flow\n\nBreaking change: Auth service now requires config object\n```\n\n## Scope examples\n\n**Frontend:**\n- `feat(ui): add loading spinner to dashboard`\n- `fix(form): validate email format`\n\n**Backend:**\n- `feat(api): add user profile endpoint`\n- `fix(db): resolve connection pool leak`\n\n**Infrastructure:**\n- `chore(ci): update Node version to 20`\n- `feat(docker): add multi-stage build`\n\n## Breaking changes\n\nIndicate breaking changes clearly:\n\n```\nfeat(api)!: restructure API response format\n\nBREAKING CHANGE: All API responses now follow JSON:API spec\n\nPrevious format:\n{ \"data\": {...}, \"status\": \"ok\" }\n\nNew format:\n{ \"data\": {...}, \"meta\": {...} }\n\nMigration guide: Update client code to handle new response structure\n```\n\n## Template workflow\n\n1. **Review changes**: `git diff --staged`\n2. **Identify type**: Is it feat, fix, refactor, etc.?\n3. **Determine scope**: What part of the codebase?\n4. **Write summary**: Brief, imperative description\n5. **Add body**: Explain why and what impact\n6. **Note breaking changes**: If applicable\n\n## Interactive commit helper\n\nUse `git add -p` for selective staging:\n\n```bash\n# Stage changes interactively\ngit add -p\n\n# Review what's staged\ngit diff --staged\n\n# Commit with message\ngit commit -m \"type(scope): description\"\n```\n\n## Amending commits\n\nFix the last commit message:\n\n```bash\n# Amend commit message only\ngit commit --amend\n\n# Amend and add more changes\ngit add forgotten-file.js\ngit commit --amend --no-edit\n```\n\n## Best practices\n\n1. **Atomic commits** - One logical change per commit\n2. **Test before commit** - Ensure code works\n3. **Reference issues** - Include issue numbers if applicable\n4. **Keep it focused** - Don't mix unrelated changes\n5. **Write for humans** - Future you will read this\n\n## Commit message checklist\n\n- [ ] Type is appropriate (feat\u002Ffix\u002Fdocs\u002Fetc.)\n- [ ] Scope is specific and clear\n- [ ] Summary is under 50 characters\n- [ ] Summary uses imperative mood\n- [ ] Body explains WHY not just WHAT\n- [ ] Breaking changes are clearly marked\n- [ ] Related issue numbers are included\n","# Git Commit Helper\n\n## Quick start\n\nAnalyze staged changes and generate commit message:\n\n```bash\n# View staged changes\ngit diff --staged\n\n# Generate commit message based on changes\n# (Claude will analyze the diff and suggest a message)\n```\n\n## Commit message format\n\nFollow conventional commits format:\n\n```\n\u003Ctype>(\u003Cscope>): \u003Cdescription>\n\n[optional body]\n\n[optional footer]\n```\n\n### Types\n\n- **feat**: New feature\n- **fix**: Bug fix\n- **docs**: Documentation changes\n- **style**: Code style changes (formatting, missing semicolons)\n- **refactor**: Code refactoring\n- **test**: Adding or updating tests\n- **chore**: Maintenance tasks\n\n### Examples\n\n**Feature commit:**\n```\nfeat(auth): add JWT authentication\n\nImplement JWT-based authentication system with:\n- Login endpoint with token generation\n- Token validation middleware\n- Refresh token support\n```\n\n**Bug fix:**\n```\nfix(api): handle null values in user profile\n\nPrevent crashes when user profile fields are null.\nAdd null checks before accessing nested properties.\n```\n\n**Refactor:**\n```\nrefactor(database): simplify query builder\n\nExtract common query patterns into reusable functions.\nReduce code duplication in database layer.\n```\n\n## Analyzing changes\n\nReview what's being committed:\n\n```bash\n# Show files changed\ngit status\n\n# Show detailed changes\ngit diff --staged\n\n# Show statistics\ngit diff --staged --stat\n\n# Show changes for specific file\ngit diff --staged path\u002Fto\u002Ffile\n```\n\n## Commit message guidelines\n\n**DO:**\n- Use imperative mood (\"add feature\" not \"added feature\")\n- Keep first line under 50 characters\n- Capitalize first letter\n- No period at end of summary\n- Explain WHY not just WHAT in body\n\n**DON'T:**\n- Use vague messages like \"update\" or \"fix stuff\"\n- Include technical implementation details in summary\n- Write paragraphs in summary line\n- Use past tense\n\n## Multi-file commits\n\nWhen committing multiple related changes:\n\n```\nrefactor(core): restructure authentication module\n\n- Move auth logic from controllers to service layer\n- Extract validation into separate validators\n- Update tests to use new structure\n- Add integration tests for auth flow\n\nBreaking change: Auth service now requires config object\n```\n\n## Scope examples\n\n**Frontend:**\n- `feat(ui): add loading spinner to dashboard`\n- `fix(form): validate email format`\n\n**Backend:**\n- `feat(api): add user profile endpoint`\n- `fix(db): resolve connection pool leak`\n\n**Infrastructure:**\n- `chore(ci): update Node version to 20`\n- `feat(docker): add multi-stage build`\n\n## Breaking changes\n\nIndicate breaking changes clearly:\n\n```\nfeat(api)!: restructure API response format\n\nBREAKING CHANGE: All API responses now follow JSON:API spec\n\nPrevious format:\n{ \"data\": {...}, \"status\": \"ok\" }\n\nNew format:\n{ \"data\": {...}, \"meta\": {...} }\n\nMigration guide: Update client code to handle new response structure\n```\n\n## Template workflow\n\n1. **Review changes**: `git diff --staged`\n2. **Identify type**: Is it feat, fix, refactor, etc.?\n3. **Determine scope**: What part of the codebase?\n4. **Write summary**: Brief, imperative description\n5. **Add body**: Explain why and what impact\n6. **Note breaking changes**: If applicable\n\n## Interactive commit helper\n\nUse `git add -p` for selective staging:\n\n```bash\n# Stage changes interactively\ngit add -p\n\n# Review what's staged\ngit diff --staged\n\n# Commit with message\ngit commit -m \"type(scope): description\"\n```\n\n## Amending commits\n\nFix the last commit message:\n\n```bash\n# Amend commit message only\ngit commit --amend\n\n# Amend and add more changes\ngit add forgotten-file.js\ngit commit --amend --no-edit\n```\n\n## Best practices\n\n1. **Atomic commits** - One logical change per commit\n2. **Test before commit** - Ensure code works\n3. **Reference issues** - Include issue numbers if applicable\n4. **Keep it focused** - Don't mix unrelated changes\n5. **Write for humans** - Future you will read this\n\n## Commit message checklist\n\n- [ ] Type is appropriate (feat\u002Ffix\u002Fdocs\u002Fetc.)\n- [ ] Scope is specific and clear\n- [ ] Summary is under 50 characters\n- [ ] Summary uses imperative mood\n- [ ] Body explains WHY not just WHAT\n- [ ] Breaking changes are clearly marked\n- [ ] Related issue numbers are included\n",{"name":5,"hooks":23,"description":7},{"PostToolUse":24},[25],{"hooks":26,"matcher":30},[27],{"type":28,"command":29},"command","echo \"[$(date)] Git Commit Helper: Analyzed git diff for commit message\" >> ~\u002F.claude\u002Fgit-commit-helper.log","Bash","main","e3744adb7654df443f12927f3e001252b3a26b6d","cli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fgit-commit-helper","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates","https:\u002F\u002Fgithub.com\u002FKrismithReddy12","2026-07-29 08:15:10",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add KrismithReddy12\u002Fclaude-code-templates --skill \"Git Commit Helper\"",{"tool":43,"command":44},"bunx","bunx skills add KrismithReddy12\u002Fclaude-code-templates --skill \"Git Commit Helper\"",{"tool":46,"command":47},"pnpm","pnpm dlx skills add KrismithReddy12\u002Fclaude-code-templates --skill \"Git Commit Helper\"","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fgit-commit-helper\u002FSKILL.md",true,[],[52,59,68,75,82,89],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":18},"01M79YMXJ07S2BQVB7JAM3657Q","zapier-make-patterns","No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points.  This skill covers when to use which platform, how to build reliable automations, and when to graduate to code-based solutions. Key insight: Zapier optimizes for simplicity and integrations (7000+ apps), Make optimizes for power","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fzapier-make-patterns\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":63,"licenseFileUrl":64,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M79YMVPMK3Y4JDP2KDJKQ2ZD","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M79YMMQ4XXMPJHDQHY8FR7ME","workflow-automation","Workflow automation is the infrastructure that makes AI agents reliable. Without durable execution, a network hiccup during a 10-step payment flow means lost money and angry customers. With it, workflows resume exactly where they left off.  This skill covers the platforms (n8n, Temporal, Inngest) and patterns (sequential, parallel, orchestrator-worker) that turn brittle scripts into production-grade automation.  Key insight: The platforms make different tradeoffs. n8n optimizes for accessibility","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fworkflow-automation\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M79YMHQY3CP1XXMQ00TGQFAW","trigger-dev","Trigger.dev expert for background jobs, AI workflows, and reliable async execution with excellent developer experience and TypeScript-first design. Use when: trigger.dev, trigger dev, background task, ai background job, long running task.","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Ftrigger-dev\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M79YME4Z3DRW0MT6BNYW1D7P","slack-automation","Automate Slack workspace operations including messaging, search, channel management, and reaction workflows through Composio's Slack toolkit.","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fslack-automation\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":18},"01M79YMAX7NFYDFXFZH2TJS7SS","planning-with-files","Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Use when starting complex tasks, multi-step projects, research tasks, or when the user mentions planning, organizing work, tracking progress, or wants structured output.","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fplanning-with-files\u002FSKILL.md",[],[]]