[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M753HVT107NEJEHCV7KNG2SY":3,"skill-same:01M753HVT107NEJEHCV7KNG2SY":74},{"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":28,"commitSha":29,"skillDirectory":30,"forksCount":14,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M753HVT107NEJEHCV7KNG2SY","fix-coderabbit-review",null,"End-to-end remediation workflow for PR review feedback by PR number. Use when Codex must export CodeRabbit issues for a PR, fix every issue completely, commit all fixes in a single commit, and resolve GitHub review threads afterward. Don't use for general PR reviews unrelated to CodeRabbit, draft PRs without review threads, or merge-strategy decisions.","haryelramalho\u002Fskills","haryelramalho","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F38708454?v=4","01M753ESC6XNS6GXGV5X9YMKGA","Haryel Ramalho","01M753ESCSPRNDTEJRVRYY1VJ0",0,"MIT","https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcommunity\u002Ffix-coderabbit-review\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: fix-coderabbit-review\ndescription: End-to-end remediation workflow for PR review feedback by PR number. Use when Codex must export CodeRabbit issues for a PR, fix every issue completely, commit all fixes in a single commit, and resolve GitHub review threads afterward. Don't use for general PR reviews unrelated to CodeRabbit, draft PRs without review threads, or merge-strategy decisions.\nmetadata:\n  author: Pedro Nauck\n  github: https:\u002F\u002Fgithub.com\u002Fpedronauck\n  repository: https:\u002F\u002Fgithub.com\u002Fpedronauck\u002Fskills\n---\n# Fix CodeRabbit Review\n\nExecute PR review remediation in a strict sequence: export issues, fix all issues, commit once, resolve threads.\n\nCore principle: evaluate each review item technically before changing code. Do not apply suggestions blindly.\n\n## Required Inputs\n\n- PR number (integer).\n- `GITHUB_TOKEN` in environment.\n- `gh` authenticated for the target repository.\n\n## Workflow\n\n1. Export review issues for the PR.\n2. Triage and validate every unresolved issue.\n3. Fix every validated issue completely.\n4. Commit all remediation changes together in one commit.\n5. Resolve review threads and mark exported issues resolved.\n\nRun commands from repository root.\n\n## Step 1: Export CodeRabbit Issues\n\nUse bundled exporter script:\n\n```bash\nPR_NUMBER=\u003Cpr-number>\nuv run .claude\u002Fskills\u002Ffix-coderabbit-review\u002Fscripts\u002Fpr_review.py \"$PR_NUMBER\" --hide-resolved\n```\n\nRead generated files in:\n\n- `ai-docs\u002Freviews-pr-\u003CPR_NUMBER>\u002F_summary.md`\n- `ai-docs\u002Freviews-pr-\u003CPR_NUMBER>\u002Fissues\u002F*.md`\n\nIf `_summary.md` shows unresolved issues, continue until all are addressed in code.\n\n## Step 2: Triage and Validate Issues\n\nReview each unresolved issue file before implementation.\n\nFor each issue:\n\n1. Restate the concrete technical change required.\n2. Verify against current codebase behavior and tests.\n3. Decide one of:\n   - `VALID`: suggestion is correct and should be implemented.\n   - `INVALID`: suggestion is incorrect or not actionable for this codebase.\n\nRules:\n\n- If an issue is ambiguous, treat it as `INVALID`, document rationale and assumptions in the issue file, and continue execution.\n- If an issue is `INVALID`, document technical rationale directly in the issue file and do not force a bad change.\n- Prefer technical evidence over agreement language.\n\n## Step 3: Fix Issues Completely\n\nProcess all unresolved issue files under `ai-docs\u002Freviews-pr-\u003CPR_NUMBER>\u002Fissues\u002F`.\n\n- Implement production-quality fixes in source code.\n- Add or update tests so each fix is verified.\n- Execute fixes one issue at a time and validate each before moving to the next.\n- Do not leave partial fixes.\n- Do not skip issues unless they are invalid; for invalid issues, keep rationale in the issue file.\n\nAfter finishing all issue fixes, run full verification before commit:\n\n```bash\npnpm run lint\npnpm run typecheck\npnpm run test\n```\n\n## Step 4: Commit All Fixes Together\n\nCreate exactly one remediation commit containing all related code, test, and issue-tracking changes.\n\n```bash\ngit add -A\ngit commit -m \"fix(repo): resolve PR #\u003CPR_NUMBER> review issues\"\n```\n\nDo not split fixes across multiple commits.\n\n## Step 5: Resolve Review Threads\n\nAfter the single commit is created, resolve exported issue threads.\n\nDetermine the issue range from issue files (example: `001` to `018`) and run:\n\n```bash\nuv run .claude\u002Fskills\u002Ffix-coderabbit-review\u002Fscripts\u002Fresolve_pr_issues.py \\\n  --pr-dir ai-docs\u002Freviews-pr-\u003CPR_NUMBER> \\\n  --from \u003Cfirst-issue-number> \\\n  --to \u003Clast-issue-number>\n```\n\nRe-open `ai-docs\u002Freviews-pr-\u003CPR_NUMBER>\u002F_summary.md` and confirm unresolved count is `0`.\n\nIf thread resolution fails for specific IDs, keep those issues marked unresolved and report exact failures instead of claiming completion.\n\n## Output Contract\n\nDeliver:\n\n- One commit containing all remediation changes.\n- Per-issue technical disposition (`VALID` or `INVALID`) recorded during triage.\n- Updated `ai-docs\u002Freviews-pr-\u003CPR_NUMBER>\u002Fissues\u002F*.md` statuses.\n- Updated `ai-docs\u002Freviews-pr-\u003CPR_NUMBER>\u002F_summary.md` counts\u002Fchecklist.\n- Resolved review threads for addressed issues.\n","# Fix CodeRabbit Review\n\nExecute PR review remediation in a strict sequence: export issues, fix all issues, commit once, resolve threads.\n\nCore principle: evaluate each review item technically before changing code. Do not apply suggestions blindly.\n\n## Required Inputs\n\n- PR number (integer).\n- `GITHUB_TOKEN` in environment.\n- `gh` authenticated for the target repository.\n\n## Workflow\n\n1. Export review issues for the PR.\n2. Triage and validate every unresolved issue.\n3. Fix every validated issue completely.\n4. Commit all remediation changes together in one commit.\n5. Resolve review threads and mark exported issues resolved.\n\nRun commands from repository root.\n\n## Step 1: Export CodeRabbit Issues\n\nUse bundled exporter script:\n\n```bash\nPR_NUMBER=\u003Cpr-number>\nuv run .claude\u002Fskills\u002Ffix-coderabbit-review\u002Fscripts\u002Fpr_review.py \"$PR_NUMBER\" --hide-resolved\n```\n\nRead generated files in:\n\n- `ai-docs\u002Freviews-pr-\u003CPR_NUMBER>\u002F_summary.md`\n- `ai-docs\u002Freviews-pr-\u003CPR_NUMBER>\u002Fissues\u002F*.md`\n\nIf `_summary.md` shows unresolved issues, continue until all are addressed in code.\n\n## Step 2: Triage and Validate Issues\n\nReview each unresolved issue file before implementation.\n\nFor each issue:\n\n1. Restate the concrete technical change required.\n2. Verify against current codebase behavior and tests.\n3. Decide one of:\n   - `VALID`: suggestion is correct and should be implemented.\n   - `INVALID`: suggestion is incorrect or not actionable for this codebase.\n\nRules:\n\n- If an issue is ambiguous, treat it as `INVALID`, document rationale and assumptions in the issue file, and continue execution.\n- If an issue is `INVALID`, document technical rationale directly in the issue file and do not force a bad change.\n- Prefer technical evidence over agreement language.\n\n## Step 3: Fix Issues Completely\n\nProcess all unresolved issue files under `ai-docs\u002Freviews-pr-\u003CPR_NUMBER>\u002Fissues\u002F`.\n\n- Implement production-quality fixes in source code.\n- Add or update tests so each fix is verified.\n- Execute fixes one issue at a time and validate each before moving to the next.\n- Do not leave partial fixes.\n- Do not skip issues unless they are invalid; for invalid issues, keep rationale in the issue file.\n\nAfter finishing all issue fixes, run full verification before commit:\n\n```bash\npnpm run lint\npnpm run typecheck\npnpm run test\n```\n\n## Step 4: Commit All Fixes Together\n\nCreate exactly one remediation commit containing all related code, test, and issue-tracking changes.\n\n```bash\ngit add -A\ngit commit -m \"fix(repo): resolve PR #\u003CPR_NUMBER> review issues\"\n```\n\nDo not split fixes across multiple commits.\n\n## Step 5: Resolve Review Threads\n\nAfter the single commit is created, resolve exported issue threads.\n\nDetermine the issue range from issue files (example: `001` to `018`) and run:\n\n```bash\nuv run .claude\u002Fskills\u002Ffix-coderabbit-review\u002Fscripts\u002Fresolve_pr_issues.py \\\n  --pr-dir ai-docs\u002Freviews-pr-\u003CPR_NUMBER> \\\n  --from \u003Cfirst-issue-number> \\\n  --to \u003Clast-issue-number>\n```\n\nRe-open `ai-docs\u002Freviews-pr-\u003CPR_NUMBER>\u002F_summary.md` and confirm unresolved count is `0`.\n\nIf thread resolution fails for specific IDs, keep those issues marked unresolved and report exact failures instead of claiming completion.\n\n## Output Contract\n\nDeliver:\n\n- One commit containing all remediation changes.\n- Per-issue technical disposition (`VALID` or `INVALID`) recorded during triage.\n- Updated `ai-docs\u002Freviews-pr-\u003CPR_NUMBER>\u002Fissues\u002F*.md` statuses.\n- Updated `ai-docs\u002Freviews-pr-\u003CPR_NUMBER>\u002F_summary.md` counts\u002Fchecklist.\n- Resolved review threads for addressed issues.\n",{"name":5,"metadata":24,"description":7},{"author":25,"github":26,"repository":27},"Pedro Nauck","https:\u002F\u002Fgithub.com\u002Fpedronauck","https:\u002F\u002Fgithub.com\u002Fpedronauck\u002Fskills","main","a5b533be2d244bbf3e5606e851742f0e0ba99423","skills\u002Fcommunity\u002Ffix-coderabbit-review","https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills","https:\u002F\u002Fgithub.com\u002Fharyelramalho","linkedin.com\u002Fin\u002Fharyelramalho\u002F","Software Engineer @ SKORR •  Former Vice President of the Junior Computer Association - TecnoJr","2026-07-16 01:34:58",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add haryelramalho\u002Fskills --skill fix-coderabbit-review",{"tool":42,"command":43},"bunx","bunx skills add haryelramalho\u002Fskills --skill fix-coderabbit-review",{"tool":45,"command":46},"pnpm","pnpm dlx skills add haryelramalho\u002Fskills --skill fix-coderabbit-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcommunity\u002Ffix-coderabbit-review\u002FSKILL.md",true,[50,56,62,66,70],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"agents\u002Fopenai.yaml","REFERENCE","参考文档",289,"https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcommunity\u002Ffix-coderabbit-review\u002Fagents\u002Fopenai.yaml",{"path":57,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":60,"sourceHtmlUrl":61},"scripts\u002Fpr_review.py","SCRIPT","脚本",36298,"https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcommunity\u002Ffix-coderabbit-review\u002Fscripts\u002Fpr_review.py",{"path":63,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":64,"sourceHtmlUrl":65},"scripts\u002Fpr-review.ts",38732,"https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcommunity\u002Ffix-coderabbit-review\u002Fscripts\u002Fpr-review.ts",{"path":67,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":68,"sourceHtmlUrl":69},"scripts\u002Fresolve_pr_issues.py",7756,"https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcommunity\u002Ffix-coderabbit-review\u002Fscripts\u002Fresolve_pr_issues.py",{"path":71,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":72,"sourceHtmlUrl":73},"scripts\u002Fresolve_pr_issues.sh",6287,"https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcommunity\u002Ffix-coderabbit-review\u002Fscripts\u002Fresolve_pr_issues.sh",[75,82,89,96,103,110],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M753YDMKSDB7320THEQ2CVW5","to-prompt-opus","Use when preparing or rewriting prompts for Claude Opus 4.8, Anthropic API agents, XML-structured prompts, long-context document work, coding agents, research synthesis, frontend\u002Fdesign tasks, or model-specific prompt optimization. Do not use for GPT\u002FOpenAI prompts or raw context packaging without Opus-specific tuning.","https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fmine\u002Fto-prompt-opus\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M753YAP95W4K2MCEAEEAV6YA","to-prompt-gpt","Use when preparing or rewriting prompts for GPT-5.5, OpenAI API agents, Responses workflows, coding agents, research synthesis, support assistants, or model-specific prompt optimization. Do not use for Claude\u002FOpus prompts or raw context packaging without GPT-specific tuning.","https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fmine\u002Fto-prompt-gpt\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M753Y700AZ0GVJDNW9Q1Q54F","plan-refactor-qa","Plans and runs qa-report before executing Compozy refactor tasks. Use when the user provides a refactor or issue slug and wants Codex to inspect the matching .compozy\u002Ftasks directory, related PRD\u002FTechSpec\u002FADR\u002Ftask artifacts, affected code, and existing tests, then invoke $qa-report with a repository-grounded prompt. Do not use to run tests, execute qa-execution, implement code, or perform post-refactor verification.","https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fmine\u002Fplan-refactor-qa\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M753XZENG0Z8S2ET75EM8CGB","multi-tool-branch-review","Orchestrates a multi-tool branch review of the current git branch against a base branch. By default it runs two independent thermo-nuclear maintainability audits, one on Codex GPT-5.5 xhigh and one on Claude Opus xhigh, then consolidates the findings into a single remediation plan via writing-plans. If the user explicitly asks for native reviews, it can add the Claude native review pass, the Codex native review pass, or both. Use when the user wants a deep cross-model review of a branch or PR before merge, or asks to review this branch with multiple tools or models. Encodes known infra failure modes and their fixes (missing Claude ACP adapter, Codex MCP auth hangs, false-positive report files, long jobs orphaned inside subagents). Do not use for reviewing a single uncommitted snippet, for non-git work, for running only one reviewer, or when the user only wants a quick lint or test run.","https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fmine\u002Fmulti-tool-branch-review\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":19},"01M753XQM40XCK55BH5WPA88EW","create-pr-with-template","Create a GitHub Pull Request with gh CLI and prefer repository PR templates automatically. Use this whenever the user asks to open\u002Fcreate a PR, especially when template compliance is needed. If multiple templates exist, ask the user which template to use.","https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fmine\u002Fcreate-pr-with-template\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":19},"01M753XJMBJ8VFPRCDCC1JJ9G4","ui-craft","Provides guardrails for user-facing UI work: usability heuristics, accessibility floors, design-system discipline, component states, microcopy, motion, dark mode, responsive behavior, and human-AI UX. Use when designing, generating, reviewing, or refactoring visible product surfaces such as components, pages, dashboards, forms, dialogs, loading\u002Fempty\u002Ferror states, or AI interfaces. Do not use for backend-only work, infrastructure, CLI\u002FTUI design, or pure documentation editing.","https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated\u002Fui-craft\u002FSKILL.md",[],[]]