[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MKC86TED4C51K560AVGD95":3,"skill-same:01M6MKC86TED4C51K560AVGD95":70},{"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":23,"publishedAt":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":46,"ownerHtmlUrl":47,"ownerBlogUrl":48,"ownerDescription":49,"updatedAt":50,"install":51,"resources":63},"01M6MKC86TED4C51K560AVGD95","skill-review-response",null,"Use when a reviewer, CI bot, or another AI leaves feedback to address","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fnyldn\u002Fclaude-octopus\u002Fskills\u002Fskill-review-response\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34],"review","review response","skill review response","skill review","bot","ci","feedback","reviewer","use","true","when","2026-11-10 10:12:30",false,"---\nname: skill-review-response\ndescription: \"Use when a reviewer, CI bot, or another AI leaves feedback to address\"\ndisable-model-invocation: true\n---\n\n> **Host: Codex CLI** — This skill was designed for Claude Code and adapted for Codex.\n> Cross-reference commands use installed skill names in Codex rather than `\u002Focto:*` slash commands.\n> Use the active Codex shell and subagent tools. Do not claim a provider, model, or host subagent is available until the current session exposes it.\n> For host tool equivalents, see `skills\u002Fblocks\u002Fcodex-host-adapter.md`.\n\n\n# Receiving Code Review\n\n## Core Principle\n\nCode review requires technical evaluation, not performative agreement.\n\n**Never blindly implement review feedback.** Verify it's correct for THIS codebase before changing anything.\n\n## The Response Pattern\n\n```\nWHEN receiving code review feedback:\n\n1. READ    — Complete feedback without reacting\n2. RESTATE — Summarize the requirement in your own words\n3. VERIFY  — Check against actual codebase state\n4. EVALUATE — Is this technically sound for THIS context?\n5. RESPOND — Technical acknowledgment OR reasoned pushback\n6. IMPLEMENT — One item at a time, verify each change\n```\n\n## Forbidden Responses\n\n**NEVER say:**\n- \"You're absolutely right!\" (without verification)\n- \"Great catch!\" (before confirming it IS a catch)\n- \"I'll fix that right away!\" (before evaluating whether it needs fixing)\n- \"Done!\" (without running verification — see skill-verification-gate)\n\n**These are social performance, not technical evaluation.** They lead to:\n- Implementing wrong suggestions\n- Introducing bugs to \"fix\" non-issues\n- Wasting time on style preferences disguised as bugs\n\n## Evaluation Checklist\n\nFor each piece of feedback:\n\n| Question | If YES | If NO |\n|----------|--------|-------|\n| Is the issue real? (verify in code) | Continue evaluation | Push back with evidence |\n| Does the suggested fix work here? | Continue evaluation | Propose alternative |\n| Does fixing this break something else? | Fix both or push back | Implement the fix |\n| Is this a style preference or a real problem? | Acknowledge, deprioritize | Fix it |\n| Was this already considered and rejected? | Explain the trade-off | Implement |\n\n## How to Push Back\n\nWhen feedback is wrong or doesn't apply:\n\n```markdown\n> Reviewer: \"This function should handle null input\"\n>\n> Response: \"Checked — this function is only called from `processUser()`\n> (line 47) which validates non-null before dispatch. Adding null handling\n> here would be dead code. The caller contract guarantees non-null.\"\n```\n\nProvide:\n1. What you checked\n2. Why the suggestion doesn't apply\n3. Evidence (line numbers, call sites, tests)\n\n## Multi-Provider Review Context\n\nIn Claude Octopus workflows, review feedback comes from multiple sources:\n\n- **Codex review** — tends toward enterprise patterns, may over-engineer\n- **Antigravity review** — tends toward ecosystem conformity, may suggest unnecessary dependencies\n- **Claude review** — tends toward elegance, may under-engineer error handling\n- **Sonnet review** — tends toward thoroughness, may flag low-priority issues\n\nWhen providers disagree:\n- Check which provider's suggestion matches the ACTUAL codebase conventions\n- The codebase's existing patterns win over any provider's preferences\n- If two providers flag the same issue, it's probably real\n\n## Handling Feedback Loops\n\nWhen a reviewer flags an issue and you fix it:\n\n1. Make the fix\n2. **Run verification** (skill-verification-gate) — prove the fix works\n3. **Re-read the original feedback** — did you address the root cause or just the symptom?\n4. If the reviewer re-reviews and finds new issues, that's normal — don't get frustrated\n5. Each round should have FEWER issues, not different ones\n\nIf the same issue keeps coming back:\n- You're fixing symptoms, not the root cause\n- Stop and re-read the feedback from scratch\n- Ask the reviewer to clarify if the issue is ambiguous\n\n## When Review Feedback Conflicts with Requirements\n\nIf a reviewer suggests something that contradicts the spec\u002Frequirements:\n\n1. Note the conflict explicitly\n2. Check if the spec is wrong (it might be)\n3. If spec is correct: implement the spec, note the reviewer's concern for future consideration\n4. If spec is wrong: flag to the user before changing anything\n\n**Requirements trump review suggestions. User intent trumps both.**\n","> **Host: Codex CLI** — This skill was designed for Claude Code and adapted for Codex.\n> Cross-reference commands use installed skill names in Codex rather than `\u002Focto:*` slash commands.\n> Use the active Codex shell and subagent tools. Do not claim a provider, model, or host subagent is available until the current session exposes it.\n> For host tool equivalents, see `skills\u002Fblocks\u002Fcodex-host-adapter.md`.\n\n\n# Receiving Code Review\n\n## Core Principle\n\nCode review requires technical evaluation, not performative agreement.\n\n**Never blindly implement review feedback.** Verify it's correct for THIS codebase before changing anything.\n\n## The Response Pattern\n\n```\nWHEN receiving code review feedback:\n\n1. READ    — Complete feedback without reacting\n2. RESTATE — Summarize the requirement in your own words\n3. VERIFY  — Check against actual codebase state\n4. EVALUATE — Is this technically sound for THIS context?\n5. RESPOND — Technical acknowledgment OR reasoned pushback\n6. IMPLEMENT — One item at a time, verify each change\n```\n\n## Forbidden Responses\n\n**NEVER say:**\n- \"You're absolutely right!\" (without verification)\n- \"Great catch!\" (before confirming it IS a catch)\n- \"I'll fix that right away!\" (before evaluating whether it needs fixing)\n- \"Done!\" (without running verification — see skill-verification-gate)\n\n**These are social performance, not technical evaluation.** They lead to:\n- Implementing wrong suggestions\n- Introducing bugs to \"fix\" non-issues\n- Wasting time on style preferences disguised as bugs\n\n## Evaluation Checklist\n\nFor each piece of feedback:\n\n| Question | If YES | If NO |\n|----------|--------|-------|\n| Is the issue real? (verify in code) | Continue evaluation | Push back with evidence |\n| Does the suggested fix work here? | Continue evaluation | Propose alternative |\n| Does fixing this break something else? | Fix both or push back | Implement the fix |\n| Is this a style preference or a real problem? | Acknowledge, deprioritize | Fix it |\n| Was this already considered and rejected? | Explain the trade-off | Implement |\n\n## How to Push Back\n\nWhen feedback is wrong or doesn't apply:\n\n```markdown\n> Reviewer: \"This function should handle null input\"\n>\n> Response: \"Checked — this function is only called from `processUser()`\n> (line 47) which validates non-null before dispatch. Adding null handling\n> here would be dead code. The caller contract guarantees non-null.\"\n```\n\nProvide:\n1. What you checked\n2. Why the suggestion doesn't apply\n3. Evidence (line numbers, call sites, tests)\n\n## Multi-Provider Review Context\n\nIn Claude Octopus workflows, review feedback comes from multiple sources:\n\n- **Codex review** — tends toward enterprise patterns, may over-engineer\n- **Antigravity review** — tends toward ecosystem conformity, may suggest unnecessary dependencies\n- **Claude review** — tends toward elegance, may under-engineer error handling\n- **Sonnet review** — tends toward thoroughness, may flag low-priority issues\n\nWhen providers disagree:\n- Check which provider's suggestion matches the ACTUAL codebase conventions\n- The codebase's existing patterns win over any provider's preferences\n- If two providers flag the same issue, it's probably real\n\n## Handling Feedback Loops\n\nWhen a reviewer flags an issue and you fix it:\n\n1. Make the fix\n2. **Run verification** (skill-verification-gate) — prove the fix works\n3. **Re-read the original feedback** — did you address the root cause or just the symptom?\n4. If the reviewer re-reviews and finds new issues, that's normal — don't get frustrated\n5. Each round should have FEWER issues, not different ones\n\nIf the same issue keeps coming back:\n- You're fixing symptoms, not the root cause\n- Stop and re-read the feedback from scratch\n- Ask the reviewer to clarify if the issue is ambiguous\n\n## When Review Feedback Conflicts with Requirements\n\nIf a reviewer suggests something that contradicts the spec\u002Frequirements:\n\n1. Note the conflict explicitly\n2. Check if the spec is wrong (it might be)\n3. If spec is correct: implement the spec, note the reviewer's concern for future consideration\n4. If spec is wrong: flag to the user before changing anything\n\n**Requirements trump review suggestions. User intent trumps both.**\n",{"name":5,"description":7,"disable-model-invocation":40},true,"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fnyldn\u002Fclaude-octopus\u002Fskills\u002Fskill-review-response",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":40},[53,56,59],{"tool":54,"command":55},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill skill-review-response",{"tool":57,"command":58},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill skill-review-response",{"tool":60,"command":61},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill skill-review-response","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fnyldn\u002Fclaude-octopus\u002Fskills\u002Fskill-review-response\u002FSKILL.md",[64],{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"agents\u002Fopenai.yaml","REFERENCE","参考文档",176,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fnyldn\u002Fclaude-octopus\u002Fskills\u002Fskill-review-response\u002Fagents\u002Fopenai.yaml",[71,79,86,93,118,142],{"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":78},"01M746ZWACVKMZ1BJXJZHYJSSX","migrate-to-e2e","Moves an existing Playwright, Cypress, Selenium, Appium, Detox, Maestro, or TesterArmy suite to e2e one slice at a time, with the old suite running beside the new one until each ported test is proven. Keeps a MIGRATION.md progress file so any later session resumes where the last stopped. Optionally plants a defect to show both suites catch it. Use for \u002Fmigrate-to-e2e, \"migrate our tests to e2e\", \"port these Maestro flows\", \"move our TesterArmy tests\", or when a project has an e2e config and an older suite still running.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fmigrate-to-e2e\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":78},"01M746ZPTAX1Q0FBKAB1CYND7E","e2e","Writes, runs, and debugs end-to-end tests for web and mobile apps with e2e, the agentic test runner, which mixes agent.act goals with exact locator assertions on a Playwright browser or an iOS or Android device. Also drives a project's running app live over the e2e MCP server to look at a screen, check a UI change, take a screenshot or record a video, and try a locator; and runs bug bashes, parallel e2e explore runs with each bug proven by a repro test. Use when a project depends on e2e or has an e2e.config.ts, when asked for end-to-end, browser, mobile, or agentic UI tests, to check a change in the running app, to QA or bug bash an app or branch, or when an e2e run fails.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fe2e\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":78},"01M746ZJN784HVHMDP9MQGCSGG","create-verification-skill","Generate a project-local verify-\u003Capp> skill on top of e2e, so any coding agent can launch the app, check it is worth driving, exercise a feature the way a user does, keep evidence, and bug bash it. Writes the skill, a feature map with one explore charter per feature, and proves it once. Use for \u002Fcreate-verification-skill, \"make a verification skill for this repo\", or when a project has no scripted way to prove UI behavior.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fcreate-verification-skill\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":35},"01M716A6ETNB9B1SQ3GXZC75VR","deja-search","deja-vu memory — search the user's past AI coding sessions with the deja CLI. Holds what they already settled and never wrote into the repo (naming rules, banned or already-tried tools, required checks before merge, preferred values, who owns what). Use before your first edit in a task, before you call a change done or ready to merge, before you recommend a tool, library, design or reviewer, before re-debugging an error that may already be solved, when they say 'didn't we fix this before', 'what did we decide about X' or 'I already have that', and before telling them something on this machine does not exist.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-search\u002FSKILL.md",[],[100,101,102,103,104,105,106,107,108,109,110,34,111,112,31,113,114,115,116,117],"search","deja search","never","error","ready","memory","re","decide","fix","design","debugging","you","done","io","change","cli","merge","past",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":35},"01M716A3J2W5SENSE9VGMXB375","deja-reflect","End-of-session reflection and memory curation with deja-vu. Review what was decided, what commands broke and what repaired them, and record durable project rules or decisions with deja remember so the next session starts with them.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-reflect\u002FSKILL.md",[],[125,126,24,113,127,128,129,130,131,132,133,134,135,136,105,137,138,139,140,141],"deja reflect","reflect","with","record","github","next","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":155,"publishedAt":35},"01M715T3RR4BAYSR57HPPTJ0PF","revid","Make, edit, export and post AI videos with Revid (revid.ai) through the Revid MCP server. Use whenever the user wants a short-form or long-form video made (from an idea, a script, a URL, an article, a PDF, a tweet, a product page, their own clips, or a song), wants to find what is going viral on TikTok, YouTube, Instagram or X before making something, wants to edit or re-export an existing Revid project, generate a standalone AI image or clip, make a series episode, or publish and schedule a finished video to connected social accounts. Covers setup (hosted MCP with OAuth, or an API key), the 36 tools, credits, polling and the rules for publishing. Routes to the more specific revid-* skills when one fits.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftmakersas\u002Frevid-skills\u002Fskills\u002Frevid\u002FSKILL.md",[148,151,152],{"categoryNo":149,"categoryName":150,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":153,"categoryName":154,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[144,156,157,158,159,160,161,138,162,106,163,164,165,166,34,167,168,169,170,171],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","image","mcp server","schedule","api","publish"]