[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73C4CJME3V39KBW9JMRE8KP":3,"skill-same:01M73C4CJME3V39KBW9JMRE8KP":49},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M73C4CJME3V39KBW9JMRE8KP","vibers-code-review",null,"Human review workflow for AI-generated GitHub projects with spec-based feedback, security review, and follow-up PRs from the Vibers service.","kalash33\u002Fkstack","kalash33","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F90259149?v=4","01M7365X8Q0B73NYHA730SMZWN","Kalash Poddar","01M7365X9D0JK47C3Q0YCCK9Z2",0,"MIT","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fvibers-code-review\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: vibers-code-review\ndescription: Human review workflow for AI-generated GitHub projects with spec-based feedback, security review, and follow-up PRs from the Vibers service.\nrisk: critical\nsource: https:\u002F\u002Fgithub.com\u002Fmarsiandeployer\u002Fvibers-action\ndate_added: \"2026-03-17\"\n---\n\n# Vibers — Human Code Review for AI-Generated Projects\n\nYou push code. We review it against your spec, fix issues, and send a PR.\n\n## When to Use\n\nUse this skill when:\n\n- You want human review for AI-generated code pushed to GitHub\n- You have a project spec and want reviewers to check implementation against it\n- You want review feedback delivered as a follow-up PR with suggested fixes\n- You are comfortable granting the Vibers service collaborator access to the repository\n\n## Quick Start (3 steps)\n\n### Step 1. Add collaborator\n\nGo to your repo → Settings → Collaborators → Add **`marsiandeployer`**\n\n### Step 2. Add GitHub Action\n\nCreate `.github\u002Fworkflows\u002Fvibers.yml`:\n\n```yaml\nname: Vibers Code Review\non:\n  push:\n    branches: [main]\n\njobs:\n  review:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n        with:\n          fetch-depth: 2\n      - uses: marsiandeployer\u002Fvibers-action@v1\n        with:\n          spec_url: 'https:\u002F\u002Fdocs.google.com\u002Fdocument\u002Fd\u002FYOUR_SPEC_ID\u002Fedit'\n          telegram_contact: '@your_telegram'\n```\n\n| Parameter | What it does |\n|-----------|-------------|\n| `spec_url` | Link to your spec (Google Doc, Notion, etc.). **Must be publicly accessible** (or \"anyone with the link can view\"). Without access to spec, review is impossible. |\n| `review_scope` | `full` (default), `security`, or `spec-compliance` |\n| `telegram_contact` | Your Telegram — we'll message you when review is ready |\n\n### Step 3. Add commit rules to your AI agent\n\nAdd this block to your project's `CLAUDE.md`, `.cursorrules`, or `AGENTS.md`:\n\n```markdown\n## Commit messages\n\nEvery commit MUST include a \"How to test\" section in the body:\n- Live URL to open and verify the change\n- Step-by-step what to click\u002Fcheck\n- Test credentials if login is required\n- Expected result for each step\n\nExample:\n  feat: Add user registration form\n\n  How to test:\n  - Open https:\u002F\u002Fmyapp.vercel.app\u002Fregister\n  - Fill in email\u002Fpassword, submit\n  - Check that confirmation email arrives\n  - Try submitting with invalid email — should show error\n  - Login: test@example.com \u002F demo123\n```\n\nWithout \"How to test\" the reviewer has to guess what to verify, and the review takes longer.\n\n**Done.** Now every push triggers a notification. You'll get a PR with fixes, usually within 24 hours.\n\n## What Happens After Setup\n\n1. You push code → GitHub Action sends us the commit details\n2. We read your spec and review changed files\n3. We fix issues directly in code and submit a PR\n4. You review the PR, merge or comment\n\nWe check: spec compliance, security (OWASP top 10), AI hallucinations (fake APIs\u002Fimports), logic bugs, UI issues.\n\nWe don't check: code style (use ESLint\u002FPrettier), performance benchmarks, full QA (use Playwright\u002FCypress).\n\n## Limitations\n\n- Requires a GitHub repository and adding `marsiandeployer` as a collaborator\n- The referenced spec must be accessible to the review workflow\n- The service is not a replacement for full QA, benchmark testing, or local security review\n- Turnaround depends on the external Vibers review service\n\n## Pricing\n\n| Plan | Rate | Details |\n|------|------|---------|\n| **Promo** | $1\u002Fhour | Full review + PRs with fixes. We ask for honest feedback in return. |\n| **Standard** | $15\u002Fhour | Full review + security audit + priority turnaround. |\n\nNo subscriptions. No contracts. Pay per review.\n\n## Feedback & Support\n\nSend feedback directly from your agent:\n\n```bash\ncurl -X POST https:\u002F\u002Fvibers.onout.org\u002Ffeedback \\\n  -H 'Content-Type: application\u002Fjson' \\\n  -d '{\"message\": \"Your question or issue\", \"repo\": \"https:\u002F\u002Fgithub.com\u002Fyou\u002Fyour-repo\"}'\n```\n\nBoth `message` and `repo` are required. Response: `{\"status\": \"accepted\"}`.\n\nContacts:\n- Telegram: [@onoutnoxon](https:\u002F\u002Ft.me\u002Fonoutnoxon)\n- Moltbook: [moltbook.com](https:\u002F\u002Fmoltbook.com) — user **noxon**\n- GitHub: [marsiandeployer](https:\u002F\u002Fgithub.com\u002Fmarsiandeployer)\n\n## FAQ\n\n**Do I need an API key?**\nNo. Add collaborator + action, that's it.\n\n**What languages?**\nJS\u002FTS, Python, React, Next.js, Django, Flask, and more. If it's on GitHub, we review it.\n\n**What if I disagree with a fix?**\nComment on the PR. We discuss and adjust.\n\n**Can I use this without GitHub?**\nYes — write to Telegram with your code and spec.\n","# Vibers — Human Code Review for AI-Generated Projects\n\nYou push code. We review it against your spec, fix issues, and send a PR.\n\n## When to Use\n\nUse this skill when:\n\n- You want human review for AI-generated code pushed to GitHub\n- You have a project spec and want reviewers to check implementation against it\n- You want review feedback delivered as a follow-up PR with suggested fixes\n- You are comfortable granting the Vibers service collaborator access to the repository\n\n## Quick Start (3 steps)\n\n### Step 1. Add collaborator\n\nGo to your repo → Settings → Collaborators → Add **`marsiandeployer`**\n\n### Step 2. Add GitHub Action\n\nCreate `.github\u002Fworkflows\u002Fvibers.yml`:\n\n```yaml\nname: Vibers Code Review\non:\n  push:\n    branches: [main]\n\njobs:\n  review:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n        with:\n          fetch-depth: 2\n      - uses: marsiandeployer\u002Fvibers-action@v1\n        with:\n          spec_url: 'https:\u002F\u002Fdocs.google.com\u002Fdocument\u002Fd\u002FYOUR_SPEC_ID\u002Fedit'\n          telegram_contact: '@your_telegram'\n```\n\n| Parameter | What it does |\n|-----------|-------------|\n| `spec_url` | Link to your spec (Google Doc, Notion, etc.). **Must be publicly accessible** (or \"anyone with the link can view\"). Without access to spec, review is impossible. |\n| `review_scope` | `full` (default), `security`, or `spec-compliance` |\n| `telegram_contact` | Your Telegram — we'll message you when review is ready |\n\n### Step 3. Add commit rules to your AI agent\n\nAdd this block to your project's `CLAUDE.md`, `.cursorrules`, or `AGENTS.md`:\n\n```markdown\n## Commit messages\n\nEvery commit MUST include a \"How to test\" section in the body:\n- Live URL to open and verify the change\n- Step-by-step what to click\u002Fcheck\n- Test credentials if login is required\n- Expected result for each step\n\nExample:\n  feat: Add user registration form\n\n  How to test:\n  - Open https:\u002F\u002Fmyapp.vercel.app\u002Fregister\n  - Fill in email\u002Fpassword, submit\n  - Check that confirmation email arrives\n  - Try submitting with invalid email — should show error\n  - Login: test@example.com \u002F demo123\n```\n\nWithout \"How to test\" the reviewer has to guess what to verify, and the review takes longer.\n\n**Done.** Now every push triggers a notification. You'll get a PR with fixes, usually within 24 hours.\n\n## What Happens After Setup\n\n1. You push code → GitHub Action sends us the commit details\n2. We read your spec and review changed files\n3. We fix issues directly in code and submit a PR\n4. You review the PR, merge or comment\n\nWe check: spec compliance, security (OWASP top 10), AI hallucinations (fake APIs\u002Fimports), logic bugs, UI issues.\n\nWe don't check: code style (use ESLint\u002FPrettier), performance benchmarks, full QA (use Playwright\u002FCypress).\n\n## Limitations\n\n- Requires a GitHub repository and adding `marsiandeployer` as a collaborator\n- The referenced spec must be accessible to the review workflow\n- The service is not a replacement for full QA, benchmark testing, or local security review\n- Turnaround depends on the external Vibers review service\n\n## Pricing\n\n| Plan | Rate | Details |\n|------|------|---------|\n| **Promo** | $1\u002Fhour | Full review + PRs with fixes. We ask for honest feedback in return. |\n| **Standard** | $15\u002Fhour | Full review + security audit + priority turnaround. |\n\nNo subscriptions. No contracts. Pay per review.\n\n## Feedback & Support\n\nSend feedback directly from your agent:\n\n```bash\ncurl -X POST https:\u002F\u002Fvibers.onout.org\u002Ffeedback \\\n  -H 'Content-Type: application\u002Fjson' \\\n  -d '{\"message\": \"Your question or issue\", \"repo\": \"https:\u002F\u002Fgithub.com\u002Fyou\u002Fyour-repo\"}'\n```\n\nBoth `message` and `repo` are required. Response: `{\"status\": \"accepted\"}`.\n\nContacts:\n- Telegram: [@onoutnoxon](https:\u002F\u002Ft.me\u002Fonoutnoxon)\n- Moltbook: [moltbook.com](https:\u002F\u002Fmoltbook.com) — user **noxon**\n- GitHub: [marsiandeployer](https:\u002F\u002Fgithub.com\u002Fmarsiandeployer)\n\n## FAQ\n\n**Do I need an API key?**\nNo. Add collaborator + action, that's it.\n\n**What languages?**\nJS\u002FTS, Python, React, Next.js, Django, Flask, and more. If it's on GitHub, we review it.\n\n**What if I disagree with a fix?**\nComment on the PR. We discuss and adjust.\n\n**Can I use this without GitHub?**\nYes — write to Telegram with your code and spec.\n",{"name":5,"risk":24,"source":25,"date_added":26,"description":7},"critical","https:\u002F\u002Fgithub.com\u002Fmarsiandeployer\u002Fvibers-action","2026-03-17","main","b30820b3248f6676d5389f0ccabd4e5250c9c536","skills\u002Fvibers-code-review","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack","https:\u002F\u002Fgithub.com\u002Fkalash33","kalashpoddar.me","Tech-savvy Full Stack Developer 🚀 | Cybersecurity enthusiast 🔒 | Passionate about innovation and securing the digital world 🌐 | Let's code securely! 💻🔐","2026-05-20 04:11:22",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add kalash33\u002Fkstack --skill vibers-code-review",{"tool":41,"command":42},"bunx","bunx skills add kalash33\u002Fkstack --skill vibers-code-review",{"tool":44,"command":45},"pnpm","pnpm dlx skills add kalash33\u002Fkstack --skill vibers-code-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fvibers-code-review\u002FSKILL.md",true,[],[50,57,64,71,78,85],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M73CFERCR43JCAP606E41EFB","zustand-store-ts","Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state\u002Faction separation. Use when building React state management, creating global stores, or implementing reacti...","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M73CFCMFVTAQEMTZ5HR10X8V","zoom-automation","Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-automation\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M73CFAA7EBWXJVXDQ1X555MB","zoho-crm-automation","Automate Zoho CRM tasks via Rube MCP (Composio): create\u002Fupdate records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzoho-crm-automation\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M73CF80XCM9K81567MJ8QZFW","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzod-validation-expert\u002FSKILL.md",[],[],{"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":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M73CF4YPMF3RA8ZJDXZSMD93","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M73CF2S25EN3XNAMKY47XHPS","zendesk-automation","Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzendesk-automation\u002FSKILL.md",[],[]]