[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6J90TH24CDS6G2ASNW17SHH":3,"skill-same:01M6J90TH24CDS6G2ASNW17SHH":81},{"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":46,"linkOnly":47,"markdownContent":48,"markdownBody":49,"frontMatter":50,"refName":60,"commitSha":61,"skillDirectory":62,"forksCount":54,"repositoryHtmlUrl":63,"repositoryHomepageUrl":6,"ownerHtmlUrl":64,"ownerBlogUrl":65,"ownerDescription":66,"updatedAt":67,"install":68,"resources":80},"01M6J90TH24CDS6G2ASNW17SHH","devops-review-implementing",null,"Process and implement code review feedback systematically. Use when user provides reviewer comments, PR feedback, code review notes, or asks to implement suggestions from reviews.","Flissel\u002Fvibemind-os","Flissel","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F104565236?v=4","01M6J8Q88NWAJGKPC5TEG9YCNV","Felix Baumann","01M6J8Q8D7XAFY44P70XTJFZBW",1,"MIT","https:\u002F\u002Fgithub.com\u002FFlissel\u002Fvibemind-os\u002Fblob\u002Fmaster\u002Fskills\u002Fdevops\u002Freview-implementing\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45],"review","devops review implementing","implementing","review implementing","devops","when","code review","review feedback","true","reviews","comments","imported","use","repo","code review feedback","reviewer","feedback","pr feedback","code","pr","notes","implement","2026-11-10 10:12:30",false,"---\nname: devops-review-implementing\ndescription: Process and implement code review feedback systematically. Use when user\n  provides reviewer comments, PR feedback, code review notes, or asks to implement\n  suggestions from reviews.\napp: devops\nrequires_approval: true\nagents:\n- '*'\ninputs: []\nexpected_state:\n  description: Imported skill — behavior matches source repo\n  verification_tool: none\nconfidence: 1.0\nattempts: 0\nsuccesses: 0\nlast_adjusted: '2026-05-11T21:21:56+00:00'\n---\n\n# Review Feedback Implementation\n\nSystematically process and implement changes based on code review feedback.\n\n## When to Use\n\n- Provides reviewer comments or feedback\n- Pastes PR review notes\n- Mentions implementing review suggestions\n- Says \"address these comments\" or \"implement feedback\"\n- Shares list of changes requested by reviewers\n\n## Systematic Workflow\n\n### 1. Parse Reviewer Notes\n\nIdentify individual feedback items:\n- Split numbered lists (1., 2., etc.)\n- Handle bullet points or unnumbered feedback\n- Extract distinct change requests\n- Clarify ambiguous items before starting\n\n### 2. Create Todo List\n\nUse TodoWrite tool to create actionable tasks:\n- Each feedback item becomes one or more todos\n- Break down complex feedback into smaller tasks\n- Make tasks specific and measurable\n- Mark first task as `in_progress` before starting\n\nExample:\n```\n- Add type hints to extract function\n- Fix duplicate tag detection logic\n- Update docstring in chain.py\n- Add unit test for edge case\n```\n\n### 3. Implement Changes Systematically\n\nFor each todo item:\n\n**Locate relevant code:**\n- Use Grep to search for functions\u002Fclasses\n- Use Glob to find files by pattern\n- Read current implementation\n\n**Make changes:**\n- Use Edit tool for modifications\n- Follow project conventions (CLAUDE.md)\n- Preserve existing functionality unless changing behavior\n\n**Verify changes:**\n- Check syntax correctness\n- Run relevant tests if applicable\n- Ensure changes address reviewer's intent\n\n**Update status:**\n- Mark todo as `completed` immediately after finishing\n- Move to next todo (only one `in_progress` at a time)\n\n### 4. Handle Different Feedback Types\n\n**Code changes:**\n- Use Edit tool for existing code\n- Follow type hint conventions (PEP 604\u002F585)\n- Maintain consistent style\n\n**New features:**\n- Create new files with Write tool if needed\n- Add corresponding tests\n- Update documentation\n\n**Documentation:**\n- Update docstrings following project style\n- Modify markdown files as needed\n- Keep explanations concise\n\n**Tests:**\n- Write tests as functions, not classes\n- Use descriptive names\n- Follow pytest conventions\n\n**Refactoring:**\n- Preserve functionality\n- Improve code structure\n- Run tests to verify no regressions\n\n### 5. Validation\n\nAfter implementing changes:\n- Run affected tests\n- Check for linting errors: `uv run ruff check`\n- Verify changes don't break existing functionality\n\n### 6. Communication\n\nKeep user informed:\n- Update todo list in real-time\n- Ask for clarification on ambiguous feedback\n- Report blockers or challenges\n- Summarize changes at completion\n\n## Edge Cases\n\n**Conflicting feedback:**\n- Ask user for guidance\n- Explain conflict clearly\n\n**Breaking changes required:**\n- Notify user before implementing\n- Discuss impact and alternatives\n\n**Tests fail after changes:**\n- Fix tests before marking todo complete\n- Ensure all related tests pass\n\n**Referenced code doesn't exist:**\n- Ask user for clarification\n- Verify understanding before proceeding\n\n## Important Guidelines\n\n- **Always use TodoWrite** for tracking progress\n- **Mark todos completed immediately** after each item\n- **Only one todo in_progress** at any time\n- **Don't batch completions** - update status in real-time\n- **Ask questions** for unclear feedback\n- **Run tests** if changes affect tested code\n- **Follow CLAUDE.md conventions** for all code changes\n- **Use conventional commits** if creating commits afterward\n","# Review Feedback Implementation\n\nSystematically process and implement changes based on code review feedback.\n\n## When to Use\n\n- Provides reviewer comments or feedback\n- Pastes PR review notes\n- Mentions implementing review suggestions\n- Says \"address these comments\" or \"implement feedback\"\n- Shares list of changes requested by reviewers\n\n## Systematic Workflow\n\n### 1. Parse Reviewer Notes\n\nIdentify individual feedback items:\n- Split numbered lists (1., 2., etc.)\n- Handle bullet points or unnumbered feedback\n- Extract distinct change requests\n- Clarify ambiguous items before starting\n\n### 2. Create Todo List\n\nUse TodoWrite tool to create actionable tasks:\n- Each feedback item becomes one or more todos\n- Break down complex feedback into smaller tasks\n- Make tasks specific and measurable\n- Mark first task as `in_progress` before starting\n\nExample:\n```\n- Add type hints to extract function\n- Fix duplicate tag detection logic\n- Update docstring in chain.py\n- Add unit test for edge case\n```\n\n### 3. Implement Changes Systematically\n\nFor each todo item:\n\n**Locate relevant code:**\n- Use Grep to search for functions\u002Fclasses\n- Use Glob to find files by pattern\n- Read current implementation\n\n**Make changes:**\n- Use Edit tool for modifications\n- Follow project conventions (CLAUDE.md)\n- Preserve existing functionality unless changing behavior\n\n**Verify changes:**\n- Check syntax correctness\n- Run relevant tests if applicable\n- Ensure changes address reviewer's intent\n\n**Update status:**\n- Mark todo as `completed` immediately after finishing\n- Move to next todo (only one `in_progress` at a time)\n\n### 4. Handle Different Feedback Types\n\n**Code changes:**\n- Use Edit tool for existing code\n- Follow type hint conventions (PEP 604\u002F585)\n- Maintain consistent style\n\n**New features:**\n- Create new files with Write tool if needed\n- Add corresponding tests\n- Update documentation\n\n**Documentation:**\n- Update docstrings following project style\n- Modify markdown files as needed\n- Keep explanations concise\n\n**Tests:**\n- Write tests as functions, not classes\n- Use descriptive names\n- Follow pytest conventions\n\n**Refactoring:**\n- Preserve functionality\n- Improve code structure\n- Run tests to verify no regressions\n\n### 5. Validation\n\nAfter implementing changes:\n- Run affected tests\n- Check for linting errors: `uv run ruff check`\n- Verify changes don't break existing functionality\n\n### 6. Communication\n\nKeep user informed:\n- Update todo list in real-time\n- Ask for clarification on ambiguous feedback\n- Report blockers or challenges\n- Summarize changes at completion\n\n## Edge Cases\n\n**Conflicting feedback:**\n- Ask user for guidance\n- Explain conflict clearly\n\n**Breaking changes required:**\n- Notify user before implementing\n- Discuss impact and alternatives\n\n**Tests fail after changes:**\n- Fix tests before marking todo complete\n- Ensure all related tests pass\n\n**Referenced code doesn't exist:**\n- Ask user for clarification\n- Verify understanding before proceeding\n\n## Important Guidelines\n\n- **Always use TodoWrite** for tracking progress\n- **Mark todos completed immediately** after each item\n- **Only one todo in_progress** at any time\n- **Don't batch completions** - update status in real-time\n- **Ask questions** for unclear feedback\n- **Run tests** if changes affect tested code\n- **Follow CLAUDE.md conventions** for all code changes\n- **Use conventional commits** if creating commits afterward\n",{"app":28,"name":5,"agents":51,"inputs":53,"attempts":54,"successes":54,"confidence":14,"description":7,"last_adjusted":55,"expected_state":56,"requires_approval":59},[52],"*",[],0,"2026-05-11T21:21:56+00:00",{"description":57,"verification_tool":58},"Imported skill — behavior matches source repo","none",true,"master","5f13b5d2b532c0ab6f847e3aa24d4bfe66f7d461","skills\u002Fdevops\u002Freview-implementing","https:\u002F\u002Fgithub.com\u002FFlissel\u002Fvibemind-os","https:\u002F\u002Fgithub.com\u002FFlissel","https:\u002F\u002Fvibemind.space","Co-founder & CTO, VibeMind - a voice-first agentic OS for non-technical founders. Agents that do the work, not describe it.","2026-11-15 02:57:54",{"source":8,"skillName":5,"commands":69,"prompt":79,"zipAvailable":59},[70,73,76],{"tool":71,"command":72},"npx","npx skills add Flissel\u002Fvibemind-os --skill devops-review-implementing",{"tool":74,"command":75},"bunx","bunx skills add Flissel\u002Fvibemind-os --skill devops-review-implementing",{"tool":77,"command":78},"pnpm","pnpm dlx skills add Flissel\u002Fvibemind-os --skill devops-review-implementing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FFlissel\u002Fvibemind-os\u002Fblob\u002Fmaster\u002Fskills\u002Fdevops\u002Freview-implementing\u002FSKILL.md",[],[82,89,96,124,132,146],{"skillNo":83,"name":24,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":46},"01M6JAA67M92TRE7GWDJDBTA9T","Review a change.","https:\u002F\u002Fgithub.com\u002FFlissel\u002Fvibemind-os\u002Fblob\u002Fmaster\u002Fspaces\u002Frowboat\u002Frowboat\u002Fpackages\u002Fopenai-plugin-runtime\u002Ftest\u002Ffixtures\u002Fcomplete-plugin\u002Fskills\u002Freview\u002FSKILL.md",[],[24,88],"change",{"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":46},"01M6JAA3DZR55G8ZY493BE9NBB","triage","Triage a change.","https:\u002F\u002Fgithub.com\u002FFlissel\u002Fvibemind-os\u002Fblob\u002Fmaster\u002Fspaces\u002Frowboat\u002Frowboat\u002Fpackages\u002Fopenai-plugin-runtime\u002Ftest\u002Ffixtures\u002Fcomplete-plugin\u002Fskills\u002Fgroup\u002Ftriage\u002FSKILL.md",[],[91,88],{"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":46},"01M6JA9XPVHENK0FQN7HBK54NV","zentrale-werkzeuge","Werkzeuge der Zentrale – nutzen bei GitHub-Fragen (Projekte updaten, Repos, Issues, PRs, Commits, CI\u002FActions-Status, README), bei Fragen zum eigenen Gitea (Sicherung\u002FSpiegel, Repos, Issues, Commits), wenn neueste Docs\u002FDoku zu einer Bibliothek oder einem Dienst geholt werden sollen, wenn ein Dashboard aus meinen Daten gebaut werden soll und wenn ich sage 'auf meinem PC suchen' oder 'such auf dem Rechner nach …'.","https:\u002F\u002Fgithub.com\u002FFlissel\u002Fvibemind-os\u002Fblob\u002Fmaster\u002Fspaces\u002Frowboat\u002Fdeploy\u002Fheadless\u002Fskills\u002Fzentrale-werkzeuge\u002FSKILL.md",[],[103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,123],"zentrale werkzeuge","grep","file","README","list","fetch","todo","gitea","add","URL","mkdir","prs","commits","ci","actions","issues","status","repos","dashboard","github","docs",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":46},"01M6JA9SQPX187CVC148SQT1SP","wissen-suchen","Bedeutungssuche im Rowboat-Wissen – IMMER zuerst nutzen, wenn nach Kunden, Kontakten, Themen, Interessen, Notizen oder 'was wissen wir über …' gefragt wird, besonders wenn die genauen Wörter unklar sind.","https:\u002F\u002Fgithub.com\u002FFlissel\u002Fvibemind-os\u002Fblob\u002Fmaster\u002Fspaces\u002Frowboat\u002Fdeploy\u002Fheadless\u002Fskills\u002Fwissen-suchen\u002FSKILL.md",[],[131],"wissen suchen",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":46},"01M6JA9P6GNFPE21101SDZS3BT","reel-aus-material","Reel aus vorhandenen Laura-Videos: passende Stellen im Transkript finden; spricht dort eine Person, bleibt ihr Originalton (mit Untertiteln aus dem Transkript), sonst trägt ein eingesprochener Satz den Clip. Bei Aufträgen der Art 'material'.","https:\u002F\u002Fgithub.com\u002FFlissel\u002Fvibemind-os\u002Fblob\u002Fmaster\u002Fspaces\u002Fmarketing\u002Fvideo_claw\u002Fskills\u002Freel-aus-material\u002FSKILL.md",[],[139,140,141,142,143,144,145],"material","reel","reel aus material","person","videos","Art","clip",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":152,"publishedAt":46},"01M6JA9KSATRT42ACWT66514ZP","reel-aus-bildern","Reel ohne Filmmaterial: Titelkarte, 3–5 Markenbilder mit wechselnder Bewegung, Schlusskarte mit Handlung; Farben und Logo der Firma. Bei Aufträgen der Art 'bilder'.","https:\u002F\u002Fgithub.com\u002FFlissel\u002Fvibemind-os\u002Fblob\u002Fmaster\u002Fspaces\u002Fmarketing\u002Fvideo_claw\u002Fskills\u002Freel-aus-bildern\u002FSKILL.md",[],[140,153,154,144],"reel aus bildern","logo"]