[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73FD5Z2C3YC62VX1XKJ0DDR":3,"skill-same:01M73FD5Z2C3YC62VX1XKJ0DDR":48},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M73FD5Z2C3YC62VX1XKJ0DDR","receiving-code-review",null,"Use when you receive review feedback on your own code or changes. Triggers on: 'reviewer said', 'PR feedback', 'review comments', 'address the feedback', 'fix the review'. Classifies feedback into must-fix \u002F optional \u002F reject-with-reason.","Horonomos-laps\u002FYana-AI","Horonomos-laps","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F355299122?v=4","01M76B3QPXE88ET2SQPDPVATZT"," Horonomos-laps","01M72ZQRJPCYPSSWT4D00VJR2A",13,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Freceiving-code-review\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: receiving-code-review\ndescription: \"Use when you receive review feedback on your own code or changes. Triggers on: 'reviewer said', 'PR feedback', 'review comments', 'address the feedback', 'fix the review'. Classifies feedback into must-fix \u002F optional \u002F reject-with-reason.\"\n---\n\n# Receiving Code Review Skill\n\nReview feedback is not a to-do list to blindly execute.\nClassify each item, act on what matters, and justify what you decline.\n\n## When to use this skill\n\n- You receive review comments on a PR or diff you wrote\n- Someone flags issues in code you produced\n- User asks you to \"address the feedback\" or \"fix the review comments\"\n\n## Step 1 — Read all feedback before acting\n\nDo not start editing on the first comment. Read everything first.\nBuild a complete picture of what the reviewer is asking.\n\n## Step 2 — Classify each comment\n\n| Category | Definition | Action |\n|----------|-----------|--------|\n| **Must fix** | Correctness bug, security issue, data loss risk | Fix immediately |\n| **Should fix** | Real concern, reasonable improvement | Fix unless there's a strong reason not to |\n| **Optional** | Style, preference, minor nitpick | Fix if fast (\u003C5 min), otherwise note and move on |\n| **Reject** | Disagrees with an intentional design choice | Respond with reasoning, do not change code |\n\n## Step 3 — Act\n\nFor each **must-fix** and **should-fix**:\n1. Make the change\n2. Confirm the fix with evidence (diff or test output)\n3. Reply to the reviewer with what you changed\n\nFor each **optional**:\n- If fast: do it\n- If not: \"Noted, deferring — [why]\"\n\nFor each **reject**:\n- Write a clear explanation: \"This is intentional because [X]. I'm keeping it as is.\"\n- Do not change the code under social pressure alone\n\n## Step 4 — Do not over-accept\n\nSigns you are over-accepting:\n- Applying every comment without reading context\n- Changing code you are confident was correct\n- Letting the reviewer's style override your project's conventions\n\nIf a comment would break something or contradict a documented decision: push back.\n\n## Response format (for PR reply)\n\n```markdown\nThanks for the review. Here's what I did:\n\n**Fixed:**\n- [comment ref] [what I changed] — [file:line]\n\n**Deferred:**\n- [comment ref] [why — e.g. out of scope, separate ticket]\n\n**Not changing:**\n- [comment ref] [reason — e.g. this is intentional because X]\n```\n\n## After applying changes\n\nRun tests and use `verify-before-done` before marking the PR ready again.\n","# Receiving Code Review Skill\n\nReview feedback is not a to-do list to blindly execute.\nClassify each item, act on what matters, and justify what you decline.\n\n## When to use this skill\n\n- You receive review comments on a PR or diff you wrote\n- Someone flags issues in code you produced\n- User asks you to \"address the feedback\" or \"fix the review comments\"\n\n## Step 1 — Read all feedback before acting\n\nDo not start editing on the first comment. Read everything first.\nBuild a complete picture of what the reviewer is asking.\n\n## Step 2 — Classify each comment\n\n| Category | Definition | Action |\n|----------|-----------|--------|\n| **Must fix** | Correctness bug, security issue, data loss risk | Fix immediately |\n| **Should fix** | Real concern, reasonable improvement | Fix unless there's a strong reason not to |\n| **Optional** | Style, preference, minor nitpick | Fix if fast (\u003C5 min), otherwise note and move on |\n| **Reject** | Disagrees with an intentional design choice | Respond with reasoning, do not change code |\n\n## Step 3 — Act\n\nFor each **must-fix** and **should-fix**:\n1. Make the change\n2. Confirm the fix with evidence (diff or test output)\n3. Reply to the reviewer with what you changed\n\nFor each **optional**:\n- If fast: do it\n- If not: \"Noted, deferring — [why]\"\n\nFor each **reject**:\n- Write a clear explanation: \"This is intentional because [X]. I'm keeping it as is.\"\n- Do not change the code under social pressure alone\n\n## Step 4 — Do not over-accept\n\nSigns you are over-accepting:\n- Applying every comment without reading context\n- Changing code you are confident was correct\n- Letting the reviewer's style override your project's conventions\n\nIf a comment would break something or contradict a documented decision: push back.\n\n## Response format (for PR reply)\n\n```markdown\nThanks for the review. Here's what I did:\n\n**Fixed:**\n- [comment ref] [what I changed] — [file:line]\n\n**Deferred:**\n- [comment ref] [why — e.g. out of scope, separate ticket]\n\n**Not changing:**\n- [comment ref] [reason — e.g. this is intentional because X]\n```\n\n## After applying changes\n\nRun tests and use `verify-before-done` before marking the PR ready again.\n",{"name":5,"description":7},"main","481dcd7dd2e288b9d627a2bd017db70e64e6c6fa","core\u002Fskills\u002Freceiving-code-review",1,"https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI","https:\u002F\u002Fyana.vutam.link\u002F","https:\u002F\u002Fgithub.com\u002FHoronomos-laps","https:\u002F\u002Fyana.vutam.link","An open-source governed runtime & execution environment for multi-agent AI systems.","2026-11-11 23:56:26",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add Horonomos-laps\u002FYana-AI --skill receiving-code-review",{"tool":40,"command":41},"bunx","bunx skills add Horonomos-laps\u002FYana-AI --skill receiving-code-review",{"tool":43,"command":44},"pnpm","pnpm dlx skills add Horonomos-laps\u002FYana-AI --skill receiving-code-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Freceiving-code-review\u002FSKILL.md",true,[],[49,57,64,72,80,88],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":53,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M735GKET5YVYKAY62W2P5YXB","openai--sentry--sentry","Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.","MIT","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fopenai--sentry--sentry\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},"01M73DCAP83T17HY7SMGK7MGFE","ito-basket-compare","Compare Itô prediction-market baskets against a user's knowledge base, portfolio notes, financial context, watchlist, or research thesis. Use for read-only basket comparison and gap analysis without investment advice or live trading.","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fito-basket-compare\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":68,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M734CYEMZFDR3KH6SW0JP8TD","implementing-network-traffic-baselining","Build network traffic baselines from NetFlow\u002FIPFIX data using Python pandas for statistical analysis, z-score anomaly detection, and hourly\u002Fdaily traffic pattern profiling","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":76,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M73ASZ6NJRJM44Z2P84NGQ3Q","detecting-evasion-techniques-in-endpoint-logs","Detects defense evasion techniques used by adversaries in endpoint logs including log tampering, timestomping, process injection, and security tool disabling. Use when investigating suspicious endpoint behavior, building detection rules for evasion tactics, or conducting threat hunting for stealthy adversary activity. Activates for requests involving evasion detection, defense evasion analysis, log tampering detection, or MITRE ATT&CK TA0005.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":84,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M734AFNXD06Z78QRK0VKGT7Q","implementing-microsegmentation-with-guardicore","Implementing microsegmentation using Akamai Guardicore Segmentation to map application dependencies, create granular network policies, visualize east-west traffic flows, and enforce least-privilege communication between workloads across data centers and cloud.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"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":91,"categories":92,"keywords":93,"publishedAt":19},"01M736TK27QMCXK0DVCH25SJN5","ramdisk-tmpfs-patterns","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Framdisk-tmpfs-patterns\u002FSKILL.md",[],[]]