[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79WP3QHZ33RY0RXTM3VXHSB":3,"skill-same:01M79WP3QHZ33RY0RXTM3VXHSB":43},{"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":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":28,"install":29,"resources":42},"01M79WP3QHZ33RY0RXTM3VXHSB","test-detect",null,"Auto-detect testing framework and run relevant tests. Identifies Jest, Vitest, Playwright, Cypress, pytest, Go test, and others. Can run all tests, specific file tests, or generate basic tests for new code. Usage - \u002Ftest-detect, \u002Ftest-detect src\u002Fauth\u002Flogin.ts, \u002Ftest-detect generate src\u002Futils.ts","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\u002Ftest-detect\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: test-detect\ndescription: Auto-detect testing framework and run relevant tests. Identifies Jest, Vitest, Playwright, Cypress, pytest, Go test, and others. Can run all tests, specific file tests, or generate basic tests for new code. Usage - \u002Ftest-detect, \u002Ftest-detect src\u002Fauth\u002Flogin.ts, \u002Ftest-detect generate src\u002Futils.ts\n---\n\n# Test Detect\n\nAutomatically detect the testing framework in the current project and run the right tests.\n\n## Workflow\n\n### Step 1: Detect the testing framework\n\nCheck for these files in order (first match wins):\n\n| Check | Framework | Run Command |\n|-------|-----------|-------------|\n| `vitest.config.*` exists OR `vitest` in devDeps | **Vitest** | `npx vitest run` |\n| `jest.config.*` exists OR `jest` in devDeps | **Jest** | `npx jest` |\n| `playwright.config.*` exists | **Playwright** | `npx playwright test` |\n| `cypress.config.*` exists | **Cypress** | `npx cypress run` |\n| `pytest.ini` or `conftest.py` or `pyproject.toml` with `[tool.pytest]` | **pytest** | `python -m pytest` |\n| `go.mod` exists | **Go test** | `go test .\u002F...` |\n| `Cargo.toml` exists | **Rust\u002Fcargo** | `cargo test` |\n| `mix.exs` exists | **ExUnit** | `mix test` |\n| `Gemfile` with `rspec` | **RSpec** | `bundle exec rspec` |\n| `package.json` has `scripts.test` | **npm test** | `npm test` |\n\nReport the detected framework before proceeding.\n\n### Step 2: Parse arguments\n\nCheck `$ARGUMENTS` for the mode:\n\n- **No arguments** or **\"all\"**: Run the full test suite (Step 3)\n- **File path** (e.g., `src\u002Fauth\u002Flogin.ts`): Run tests for that file (Step 4)\n- **\"generate\" + file path** (e.g., `generate src\u002Futils.ts`): Generate tests (Step 5)\n\n### Step 3: Run full test suite\n\nRun the detected test command. After completion:\n\n- Report total tests, passed, failed, skipped\n- If tests fail, show the first 3 failure messages with file:line references\n- Suggest: \"Run `\u002Ftest-detect \u003Cfailing-file>` to investigate a specific failure\"\n\n### Step 4: Run tests for a specific file\n\nGiven a source file path, find its test file:\n\n**Search strategy** (try in order):\n1. `__tests__\u002F\u003Cfilename>.test.\u003Cext>` (Jest convention)\n2. `\u003Cfilename>.test.\u003Cext>` (co-located)\n3. `\u003Cfilename>.spec.\u003Cext>` (alternative convention)\n4. `test\u002F\u003Cfilename>_test.\u003Cext>` (Go\u002FPython convention)\n5. `tests\u002Ftest_\u003Cfilename>.\u003Cext>` (pytest convention)\n6. `\u003Cfilename>_test.go` (Go convention)\n\nUse Glob to find matches. If found, run only that test file:\n\n| Framework | Command |\n|-----------|---------|\n| Vitest | `npx vitest run \u003Ctest-file>` |\n| Jest | `npx jest \u003Ctest-file>` |\n| Playwright | `npx playwright test \u003Ctest-file>` |\n| pytest | `python -m pytest \u003Ctest-file>` |\n| Go | `go test -run \u003CTestName> .\u002F\u003Cpackage>\u002F` |\n| Cargo | `cargo test \u003Ctest_name>` |\n\nIf no test file found, ask: \"No tests found for this file. Want me to generate them? Run `\u002Ftest-detect generate \u003Cfile>`\"\n\n### Step 5: Generate tests\n\nRead the source file and analyze:\n1. Identify all exported functions\u002Fclasses\u002Fcomponents\n2. Determine the appropriate test patterns for the framework\n3. Generate a test file with:\n   - Import statements\n   - `describe` block per function\u002Fclass\n   - `it`\u002F`test` blocks covering: happy path, edge cases, error cases\n   - Framework-appropriate assertions and mocking\n\n**Save to the conventional location** for the detected framework:\n- Jest\u002FVitest: `__tests__\u002F\u003Cfilename>.test.\u003Cext>` or `\u003Cfilename>.test.\u003Cext>` (match existing convention)\n- pytest: `tests\u002Ftest_\u003Cfilename>.py`\n- Go: `\u003Cfilename>_test.go` (same directory)\n- RSpec: `spec\u002F\u003Cfilename>_spec.rb`\n\nShow the generated file path and ask if the user wants to run the new tests.\n\n## Tips\n\n- If multiple frameworks are detected (e.g., Vitest for unit tests + Playwright for e2e), mention both and default to the unit test framework\n- For monorepos, detect from the closest config file to the current directory\n- If `package.json` has both `test` and `test:unit`\u002F`test:e2e` scripts, prefer the specific one when context is clear\n","# Test Detect\n\nAutomatically detect the testing framework in the current project and run the right tests.\n\n## Workflow\n\n### Step 1: Detect the testing framework\n\nCheck for these files in order (first match wins):\n\n| Check | Framework | Run Command |\n|-------|-----------|-------------|\n| `vitest.config.*` exists OR `vitest` in devDeps | **Vitest** | `npx vitest run` |\n| `jest.config.*` exists OR `jest` in devDeps | **Jest** | `npx jest` |\n| `playwright.config.*` exists | **Playwright** | `npx playwright test` |\n| `cypress.config.*` exists | **Cypress** | `npx cypress run` |\n| `pytest.ini` or `conftest.py` or `pyproject.toml` with `[tool.pytest]` | **pytest** | `python -m pytest` |\n| `go.mod` exists | **Go test** | `go test .\u002F...` |\n| `Cargo.toml` exists | **Rust\u002Fcargo** | `cargo test` |\n| `mix.exs` exists | **ExUnit** | `mix test` |\n| `Gemfile` with `rspec` | **RSpec** | `bundle exec rspec` |\n| `package.json` has `scripts.test` | **npm test** | `npm test` |\n\nReport the detected framework before proceeding.\n\n### Step 2: Parse arguments\n\nCheck `$ARGUMENTS` for the mode:\n\n- **No arguments** or **\"all\"**: Run the full test suite (Step 3)\n- **File path** (e.g., `src\u002Fauth\u002Flogin.ts`): Run tests for that file (Step 4)\n- **\"generate\" + file path** (e.g., `generate src\u002Futils.ts`): Generate tests (Step 5)\n\n### Step 3: Run full test suite\n\nRun the detected test command. After completion:\n\n- Report total tests, passed, failed, skipped\n- If tests fail, show the first 3 failure messages with file:line references\n- Suggest: \"Run `\u002Ftest-detect \u003Cfailing-file>` to investigate a specific failure\"\n\n### Step 4: Run tests for a specific file\n\nGiven a source file path, find its test file:\n\n**Search strategy** (try in order):\n1. `__tests__\u002F\u003Cfilename>.test.\u003Cext>` (Jest convention)\n2. `\u003Cfilename>.test.\u003Cext>` (co-located)\n3. `\u003Cfilename>.spec.\u003Cext>` (alternative convention)\n4. `test\u002F\u003Cfilename>_test.\u003Cext>` (Go\u002FPython convention)\n5. `tests\u002Ftest_\u003Cfilename>.\u003Cext>` (pytest convention)\n6. `\u003Cfilename>_test.go` (Go convention)\n\nUse Glob to find matches. If found, run only that test file:\n\n| Framework | Command |\n|-----------|---------|\n| Vitest | `npx vitest run \u003Ctest-file>` |\n| Jest | `npx jest \u003Ctest-file>` |\n| Playwright | `npx playwright test \u003Ctest-file>` |\n| pytest | `python -m pytest \u003Ctest-file>` |\n| Go | `go test -run \u003CTestName> .\u002F\u003Cpackage>\u002F` |\n| Cargo | `cargo test \u003Ctest_name>` |\n\nIf no test file found, ask: \"No tests found for this file. Want me to generate them? Run `\u002Ftest-detect generate \u003Cfile>`\"\n\n### Step 5: Generate tests\n\nRead the source file and analyze:\n1. Identify all exported functions\u002Fclasses\u002Fcomponents\n2. Determine the appropriate test patterns for the framework\n3. Generate a test file with:\n   - Import statements\n   - `describe` block per function\u002Fclass\n   - `it`\u002F`test` blocks covering: happy path, edge cases, error cases\n   - Framework-appropriate assertions and mocking\n\n**Save to the conventional location** for the detected framework:\n- Jest\u002FVitest: `__tests__\u002F\u003Cfilename>.test.\u003Cext>` or `\u003Cfilename>.test.\u003Cext>` (match existing convention)\n- pytest: `tests\u002Ftest_\u003Cfilename>.py`\n- Go: `\u003Cfilename>_test.go` (same directory)\n- RSpec: `spec\u002F\u003Cfilename>_spec.rb`\n\nShow the generated file path and ask if the user wants to run the new tests.\n\n## Tips\n\n- If multiple frameworks are detected (e.g., Vitest for unit tests + Playwright for e2e), mention both and default to the unit test framework\n- For monorepos, detect from the closest config file to the current directory\n- If `package.json` has both `test` and `test:unit`\u002F`test:e2e` scripts, prefer the specific one when context is clear\n",{"name":5,"description":7},"main","e3744adb7654df443f12927f3e001252b3a26b6d","cli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ftest-detect","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates","https:\u002F\u002Fgithub.com\u002FKrismithReddy12","2026-07-29 08:15:10",{"source":8,"skillName":5,"commands":30,"prompt":40,"zipAvailable":41},[31,34,37],{"tool":32,"command":33},"npx","npx skills add KrismithReddy12\u002Fclaude-code-templates --skill test-detect",{"tool":35,"command":36},"bunx","bunx skills add KrismithReddy12\u002Fclaude-code-templates --skill test-detect",{"tool":38,"command":39},"pnpm","pnpm dlx skills add KrismithReddy12\u002Fclaude-code-templates --skill test-detect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ftest-detect\u002FSKILL.md",true,[],[44,51,60,67,74,81],{"skillNo":45,"name":46,"nameZh":6,"description":47,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":48,"categories":49,"keywords":50,"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":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":55,"licenseFileUrl":56,"sourceHtmlUrl":57,"categories":58,"keywords":59,"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":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"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":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"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":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"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":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"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",[],[]]