[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CTJHS4ZPSFGMDDXZPARCBW":3,"skill-same:01M6CTJHS4ZPSFGMDDXZPARCBW":60},{"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":32,"linkOnly":33,"markdownContent":34,"markdownBody":35,"frontMatter":36,"refName":38,"commitSha":39,"skillDirectory":40,"forksCount":41,"repositoryHtmlUrl":42,"repositoryHomepageUrl":42,"ownerHtmlUrl":43,"ownerBlogUrl":6,"ownerDescription":44,"updatedAt":45,"install":46,"resources":59},"01M6CTJHS4ZPSFGMDDXZPARCBW","iterate-pr",null,"Iterate on a PR until CI passes. Use when you need to fix CI failures, address review feedback, or continuously push fixes until all checks are green. Automates the feedback-fix-push-wait cycle.","Sam-06060\u002Fjarvis-assistant","Sam-06060","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F208600848?v=4","01M6CRKT7C7FXD21V6HXF293S0","Samson Frank Ganta","01M6CRKTBEKYFD8YX5Z1GT99EE",6,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fiterate-pr\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31],"pr","iterate pr","review","fix ci failures","fix ci","push","ci","feedback","fix","use","community","cycle","green","2026-11-10 10:12:30",false,"---\nname: iterate-pr\ndescription: Iterate on a PR until CI passes. Use when you need to fix CI failures, address review feedback, or continuously push fixes until all checks are green. Automates the feedback-fix-push-wait cycle.\nrisk: critical\nsource: community\n---\n\n# Iterate on PR Until CI Passes\n\nContinuously iterate on the current branch until all CI checks pass and review feedback is addressed.\n\n**Requires**: GitHub CLI (`gh`) authenticated.\n\n**Important**: All scripts must be run from the repository root directory (where `.git` is located), not from the skill directory. Use the full path to the script via `${CLAUDE_SKILL_ROOT}`.\n\n## Bundled Scripts\n\n### `scripts\u002Ffetch_pr_checks.py`\n\nFetches CI check status and extracts failure snippets from logs.\n\n```bash\nuv run ${CLAUDE_SKILL_ROOT}\u002Fscripts\u002Ffetch_pr_checks.py [--pr NUMBER]\n```\n\nReturns JSON:\n```json\n{\n  \"pr\": {\"number\": 123, \"branch\": \"feat\u002Ffoo\"},\n  \"summary\": {\"total\": 5, \"passed\": 3, \"failed\": 2, \"pending\": 0},\n  \"checks\": [\n    {\"name\": \"tests\", \"status\": \"fail\", \"log_snippet\": \"...\", \"run_id\": 123},\n    {\"name\": \"lint\", \"status\": \"pass\"}\n  ]\n}\n```\n\n### `scripts\u002Ffetch_pr_feedback.py`\n\nFetches and categorizes PR review feedback using the [LOGAF scale](https:\u002F\u002Fdevelop.sentry.dev\u002Fengineering-practices\u002Fcode-review\u002F#logaf-scale).\n\n```bash\nuv run ${CLAUDE_SKILL_ROOT}\u002Fscripts\u002Ffetch_pr_feedback.py [--pr NUMBER]\n```\n\nReturns JSON with feedback categorized as:\n- `high` - Must address before merge (`h:`, blocker, changes requested)\n- `medium` - Should address (`m:`, standard feedback)\n- `low` - Optional (`l:`, nit, style, suggestion)\n- `bot` - Informational automated comments (Codecov, Dependabot, etc.)\n- `resolved` - Already resolved threads\n\nReview bot feedback (from Sentry, Warden, Cursor, Bugbot, CodeQL, etc.) appears in `high`\u002F`medium`\u002F`low` with `review_bot: true` — it is NOT placed in the `bot` bucket.\n\nEach feedback item may also include:\n- `thread_id` - GraphQL node ID for inline review comments (used for replies)\n\n## Workflow\n\n### 1. Identify PR\n\n```bash\ngh pr view --json number,url,headRefName\n```\n\nStop if no PR exists for the current branch.\n\n### 2. Gather Review Feedback\n\nRun `${CLAUDE_SKILL_ROOT}\u002Fscripts\u002Ffetch_pr_feedback.py` to get categorized feedback already posted on the PR.\n\n### 3. Handle Feedback by LOGAF Priority\n\n**Auto-fix (no prompt):**\n- `high` - must address (blockers, security, changes requested)\n- `medium` - should address (standard feedback)\n\nWhen fixing feedback:\n- Understand the root cause, not just the surface symptom\n- Check for similar issues in nearby code or related files\n- Fix all instances, not just the one mentioned\n\nThis includes review bot feedback (items with `review_bot: true`). Treat it the same as human feedback:\n- Real issue found → fix it\n- False positive → skip, but explain why in a brief comment\n- Never silently ignore review bot feedback — always verify the finding\n\n**Prompt user for selection:**\n- `low` - present numbered list and ask which to address:\n\n```\nFound 3 low-priority suggestions:\n1. [l] \"Consider renaming this variable\" - @reviewer in api.py:42\n2. [nit] \"Could use a list comprehension\" - @reviewer in utils.py:18\n3. [style] \"Add a docstring\" - @reviewer in models.py:55\n\nWhich would you like to address? (e.g., \"1,3\" or \"all\" or \"none\")\n```\n\n**Skip silently:**\n- `resolved` threads\n- `bot` comments (informational only — Codecov, Dependabot, etc.)\n\n#### Replying to Comments\n\nAfter processing each inline review comment, reply on the PR thread to acknowledge the action taken. Only reply to items with a `thread_id` (inline review comments).\n\n**When to reply:**\n- `high` and `medium` items — whether fixed or determined to be false positives\n- `low` items — whether fixed or declined by the user\n\n**How to reply:** Use the `addPullRequestReviewThreadReply` GraphQL mutation with `pullRequestReviewThreadId` and `body` inputs.\n\n**Reply format:**\n- 1-2 sentences: what was changed, why it's not an issue, or acknowledgment of declined items\n- End every reply with `\\n\\n*— Claude Code*`\n- Before replying, check if the thread already has a reply ending with `*- Claude Code*` or `*— Claude Code*` to avoid duplicates on re-loops\n- If the `gh api` call fails, log and continue — do not block the workflow\n\n### 4. Check CI Status\n\nRun `${CLAUDE_SKILL_ROOT}\u002Fscripts\u002Ffetch_pr_checks.py` to get structured failure data.\n\n**Wait if pending:** If review bot checks (sentry, warden, cursor, bugbot, seer, codeql) are still running, wait before proceeding—they post actionable feedback that must be evaluated. Informational bots (codecov) are not worth waiting for.\n\n### 5. Fix CI Failures\n\nFor each failure in the script output:\n1. Read the `log_snippet` and trace backwards from the error to understand WHY it failed — not just what failed\n2. Read the relevant code and check for related issues (e.g., if a type error in one call site, check other call sites)\n3. Fix the root cause with minimal, targeted changes\n4. Find existing tests for the affected code and run them. If the fix introduces behavior not covered by existing tests, extend them to cover it (add a test case, not a whole new test file)\n\nDo NOT assume what failed based on check name alone—always read the logs. Do NOT \"quick fix and hope\" — understand the failure thoroughly before changing code.\n\n### 6. Verify Locally, Then Commit and Push\n\nBefore committing, verify your fixes locally:\n- If you fixed a test failure: re-run that specific test locally\n- If you fixed a lint\u002Ftype error: re-run the linter or type checker on affected files\n- For any code fix: run existing tests covering the changed code\n\nIf local verification fails, fix before proceeding — do not push known-broken code.\n\n```bash\ngit add \u003Cfiles>\ngit commit -m \"fix: \u003Cdescriptive message>\"\ngit push\n```\n\n### 7. Monitor CI and Address Feedback\n\nPoll CI status and review feedback in a loop instead of blocking:\n\n1. Run `uv run ${CLAUDE_SKILL_ROOT}\u002Fscripts\u002Ffetch_pr_checks.py` to get current CI status\n2. If all checks passed → proceed to exit conditions\n3. If any checks failed (none pending) → return to step 5\n4. If checks are still pending:\n   a. Run `uv run ${CLAUDE_SKILL_ROOT}\u002Fscripts\u002Ffetch_pr_feedback.py` for new review feedback\n   b. Address any new high\u002Fmedium feedback immediately (same as step 3)\n   c. If changes were needed, commit and push (this restarts CI), then continue polling\n   d. Sleep 30 seconds, then repeat from sub-step 1\n5. After all checks pass, do a final feedback check: `sleep 10`, then run `uv run ${CLAUDE_SKILL_ROOT}\u002Fscripts\u002Ffetch_pr_feedback.py`. Address any new high\u002Fmedium feedback — if changes are needed, return to step 6.\n\n### 8. Repeat\n\nIf step 7 required code changes (from new feedback after CI passed), return to step 2 for a fresh cycle. CI failures during monitoring are already handled within step 7's polling loop.\n\n## Exit Conditions\n\n**Success:** All checks pass, post-CI feedback re-check is clean (no new unaddressed high\u002Fmedium feedback including review bot findings), user has decided on low-priority items.\n\n**Ask for help:** Same failure after 2 attempts, feedback needs clarification, infrastructure issues.\n\n**Stop:** No PR exists, branch needs rebase.\n\n## Fallback\n\nIf scripts fail, use `gh` CLI directly:\n- `gh pr checks name,state,bucket,link`\n- `gh run view \u003Crun-id> --log-failed`\n- `gh api repos\u002F{owner}\u002F{repo}\u002Fpulls\u002F{number}\u002Fcomments`\n\n\n## When to Use\nUse this skill when tackling tasks related to its primary domain or functionality as described above.\n","# Iterate on PR Until CI Passes\n\nContinuously iterate on the current branch until all CI checks pass and review feedback is addressed.\n\n**Requires**: GitHub CLI (`gh`) authenticated.\n\n**Important**: All scripts must be run from the repository root directory (where `.git` is located), not from the skill directory. Use the full path to the script via `${CLAUDE_SKILL_ROOT}`.\n\n## Bundled Scripts\n\n### `scripts\u002Ffetch_pr_checks.py`\n\nFetches CI check status and extracts failure snippets from logs.\n\n```bash\nuv run ${CLAUDE_SKILL_ROOT}\u002Fscripts\u002Ffetch_pr_checks.py [--pr NUMBER]\n```\n\nReturns JSON:\n```json\n{\n  \"pr\": {\"number\": 123, \"branch\": \"feat\u002Ffoo\"},\n  \"summary\": {\"total\": 5, \"passed\": 3, \"failed\": 2, \"pending\": 0},\n  \"checks\": [\n    {\"name\": \"tests\", \"status\": \"fail\", \"log_snippet\": \"...\", \"run_id\": 123},\n    {\"name\": \"lint\", \"status\": \"pass\"}\n  ]\n}\n```\n\n### `scripts\u002Ffetch_pr_feedback.py`\n\nFetches and categorizes PR review feedback using the [LOGAF scale](https:\u002F\u002Fdevelop.sentry.dev\u002Fengineering-practices\u002Fcode-review\u002F#logaf-scale).\n\n```bash\nuv run ${CLAUDE_SKILL_ROOT}\u002Fscripts\u002Ffetch_pr_feedback.py [--pr NUMBER]\n```\n\nReturns JSON with feedback categorized as:\n- `high` - Must address before merge (`h:`, blocker, changes requested)\n- `medium` - Should address (`m:`, standard feedback)\n- `low` - Optional (`l:`, nit, style, suggestion)\n- `bot` - Informational automated comments (Codecov, Dependabot, etc.)\n- `resolved` - Already resolved threads\n\nReview bot feedback (from Sentry, Warden, Cursor, Bugbot, CodeQL, etc.) appears in `high`\u002F`medium`\u002F`low` with `review_bot: true` — it is NOT placed in the `bot` bucket.\n\nEach feedback item may also include:\n- `thread_id` - GraphQL node ID for inline review comments (used for replies)\n\n## Workflow\n\n### 1. Identify PR\n\n```bash\ngh pr view --json number,url,headRefName\n```\n\nStop if no PR exists for the current branch.\n\n### 2. Gather Review Feedback\n\nRun `${CLAUDE_SKILL_ROOT}\u002Fscripts\u002Ffetch_pr_feedback.py` to get categorized feedback already posted on the PR.\n\n### 3. Handle Feedback by LOGAF Priority\n\n**Auto-fix (no prompt):**\n- `high` - must address (blockers, security, changes requested)\n- `medium` - should address (standard feedback)\n\nWhen fixing feedback:\n- Understand the root cause, not just the surface symptom\n- Check for similar issues in nearby code or related files\n- Fix all instances, not just the one mentioned\n\nThis includes review bot feedback (items with `review_bot: true`). Treat it the same as human feedback:\n- Real issue found → fix it\n- False positive → skip, but explain why in a brief comment\n- Never silently ignore review bot feedback — always verify the finding\n\n**Prompt user for selection:**\n- `low` - present numbered list and ask which to address:\n\n```\nFound 3 low-priority suggestions:\n1. [l] \"Consider renaming this variable\" - @reviewer in api.py:42\n2. [nit] \"Could use a list comprehension\" - @reviewer in utils.py:18\n3. [style] \"Add a docstring\" - @reviewer in models.py:55\n\nWhich would you like to address? (e.g., \"1,3\" or \"all\" or \"none\")\n```\n\n**Skip silently:**\n- `resolved` threads\n- `bot` comments (informational only — Codecov, Dependabot, etc.)\n\n#### Replying to Comments\n\nAfter processing each inline review comment, reply on the PR thread to acknowledge the action taken. Only reply to items with a `thread_id` (inline review comments).\n\n**When to reply:**\n- `high` and `medium` items — whether fixed or determined to be false positives\n- `low` items — whether fixed or declined by the user\n\n**How to reply:** Use the `addPullRequestReviewThreadReply` GraphQL mutation with `pullRequestReviewThreadId` and `body` inputs.\n\n**Reply format:**\n- 1-2 sentences: what was changed, why it's not an issue, or acknowledgment of declined items\n- End every reply with `\\n\\n*— Claude Code*`\n- Before replying, check if the thread already has a reply ending with `*- Claude Code*` or `*— Claude Code*` to avoid duplicates on re-loops\n- If the `gh api` call fails, log and continue — do not block the workflow\n\n### 4. Check CI Status\n\nRun `${CLAUDE_SKILL_ROOT}\u002Fscripts\u002Ffetch_pr_checks.py` to get structured failure data.\n\n**Wait if pending:** If review bot checks (sentry, warden, cursor, bugbot, seer, codeql) are still running, wait before proceeding—they post actionable feedback that must be evaluated. Informational bots (codecov) are not worth waiting for.\n\n### 5. Fix CI Failures\n\nFor each failure in the script output:\n1. Read the `log_snippet` and trace backwards from the error to understand WHY it failed — not just what failed\n2. Read the relevant code and check for related issues (e.g., if a type error in one call site, check other call sites)\n3. Fix the root cause with minimal, targeted changes\n4. Find existing tests for the affected code and run them. If the fix introduces behavior not covered by existing tests, extend them to cover it (add a test case, not a whole new test file)\n\nDo NOT assume what failed based on check name alone—always read the logs. Do NOT \"quick fix and hope\" — understand the failure thoroughly before changing code.\n\n### 6. Verify Locally, Then Commit and Push\n\nBefore committing, verify your fixes locally:\n- If you fixed a test failure: re-run that specific test locally\n- If you fixed a lint\u002Ftype error: re-run the linter or type checker on affected files\n- For any code fix: run existing tests covering the changed code\n\nIf local verification fails, fix before proceeding — do not push known-broken code.\n\n```bash\ngit add \u003Cfiles>\ngit commit -m \"fix: \u003Cdescriptive message>\"\ngit push\n```\n\n### 7. Monitor CI and Address Feedback\n\nPoll CI status and review feedback in a loop instead of blocking:\n\n1. Run `uv run ${CLAUDE_SKILL_ROOT}\u002Fscripts\u002Ffetch_pr_checks.py` to get current CI status\n2. If all checks passed → proceed to exit conditions\n3. If any checks failed (none pending) → return to step 5\n4. If checks are still pending:\n   a. Run `uv run ${CLAUDE_SKILL_ROOT}\u002Fscripts\u002Ffetch_pr_feedback.py` for new review feedback\n   b. Address any new high\u002Fmedium feedback immediately (same as step 3)\n   c. If changes were needed, commit and push (this restarts CI), then continue polling\n   d. Sleep 30 seconds, then repeat from sub-step 1\n5. After all checks pass, do a final feedback check: `sleep 10`, then run `uv run ${CLAUDE_SKILL_ROOT}\u002Fscripts\u002Ffetch_pr_feedback.py`. Address any new high\u002Fmedium feedback — if changes are needed, return to step 6.\n\n### 8. Repeat\n\nIf step 7 required code changes (from new feedback after CI passed), return to step 2 for a fresh cycle. CI failures during monitoring are already handled within step 7's polling loop.\n\n## Exit Conditions\n\n**Success:** All checks pass, post-CI feedback re-check is clean (no new unaddressed high\u002Fmedium feedback including review bot findings), user has decided on low-priority items.\n\n**Ask for help:** Same failure after 2 attempts, feedback needs clarification, infrastructure issues.\n\n**Stop:** No PR exists, branch needs rebase.\n\n## Fallback\n\nIf scripts fail, use `gh` CLI directly:\n- `gh pr checks name,state,bucket,link`\n- `gh run view \u003Crun-id> --log-failed`\n- `gh api repos\u002F{owner}\u002F{repo}\u002Fpulls\u002F{number}\u002Fcomments`\n\n\n## When to Use\nUse this skill when tackling tasks related to its primary domain or functionality as described above.\n",{"name":5,"risk":37,"source":29,"description":7},"critical","main","a50a3aa6b39fb0e1b7db88bef1bfc9c93606e126","modules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fiterate-pr",0,"https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant","https:\u002F\u002Fgithub.com\u002FSam-06060","Mobile Application Developer | Kotlin | Flutter, KMP, Swfit, Android,Swift UI | Building at Saar It Resources | Creator of Jarvis (AI Assistant)","2026-06-23 05:13:38",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add Sam-06060\u002Fjarvis-assistant --skill iterate-pr",{"tool":52,"command":53},"bunx","bunx skills add Sam-06060\u002Fjarvis-assistant --skill iterate-pr",{"tool":55,"command":56},"pnpm","pnpm dlx skills add Sam-06060\u002Fjarvis-assistant --skill iterate-pr","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fiterate-pr\u002FSKILL.md",true,[],[61,74,90,116,135,162],{"skillNo":62,"name":63,"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":64,"categories":65,"keywords":71,"publishedAt":32},"01M6GDRVS6FXX3ESH0C9DW01C0","test_skill","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fscratch\u002Ftest_skill\u002FSKILL.md",[66],{"categoryNo":67,"categoryName":68,"taxonomyType":69,"taxonomyTypeDesc":70},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[72,73],"Test Skill","test",{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":32},"01M6GDRQ40HX22MA6XWC31RHHK","zustand-store-ts","Create Zustand stores following established patterns with proper TypeScript types and middleware.","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzustand-store-ts\u002FSKILL.md",[],[81,82,83,84,85,86,87,29,88,89],"zustand store ts","zustand","store","with","types","middleware","patterns","create","typescript",{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":99,"publishedAt":32},"01M6GDRKEA0WE670SPFWX5GKCN","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\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzoom-automation\u002FSKILL.md",[96],{"categoryNo":97,"categoryName":98,"taxonomyType":69,"taxonomyTypeDesc":70},"01JBSEEDCAT000000000000023","Skill与智能体开发",[100,101,102,103,104,105,106,107,108,109,37,110,111,112,29,113,114,115],"automation","zoom automation","zoom","first","Tools","search","MCP","via","meeting","automate","creation","webinars","composio","recordings","management","tracking",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":123,"publishedAt":32},"01M6GDRFS1452PC71JQ38S24HR","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\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzoho-crm-automation\u002FSKILL.md",[122],{"categoryNo":97,"categoryName":98,"taxonomyType":69,"taxonomyTypeDesc":70},[124,100,125,126,127,128,129,29,105,130,112,131,37,109,104,132,88,133,106,134],"crm automation","zoho crm","crm","zoho crm automation","zoho","leads","contacts","records","update","tasks","manage",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":144,"publishedAt":32},"01M6GDRCKQBAVTGHX5XBH26KPZ","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\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzod-validation-expert\u002FSKILL.md",[141],{"categoryNo":142,"categoryName":143,"taxonomyType":69,"taxonomyTypeDesc":70},"01JBSEEDCAT000000000000009","前端开发",[145,146,147,148,149,89,150,151,152,153,154,155,84,156,157,158,159,29,160,161],"expert","zod","zod validation expert","validation","react","safe","parsing","errors","schema validation","react hook form","hook","trpc","form","type","next","schema","Next.js",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":169,"publishedAt":32},"01M6GDR658B08K4MY0RWD4A6EH","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\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzeroize-audit\u002FSKILL.md",[168],{"categoryNo":97,"categoryName":98,"taxonomyType":69,"taxonomyTypeDesc":70},[170,171,172,173,174,175,176,177,29,178,179,180,181,182,183,184,185,186,187,106],"zeroize audit","audit","write","passwords","get","project","c++","activate","assembly","read","Bash","secrets","analysis","data","flow","verification","code","rust"]