[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77RYYVVMG0CD1AGBC08Y51G":3,"skill-same:01M77RYYVVMG0CD1AGBC08Y51G":45},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":20,"frontMatter":21,"refName":22,"commitSha":23,"skillDirectory":24,"forksCount":25,"repositoryHtmlUrl":26,"repositoryHomepageUrl":27,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M77RYYVVMG0CD1AGBC08Y51G","pr-advocacy",null,"Lord1Egypt\u002Fawesome-skill-forge","Lord1Egypt","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99746359?v=4","01M7592YDNT0XK9WJ0T2MQVPDN","Mohamed Mounir Ali AL Keshita","01M75GRFNHC8VZNWEB8DKDE433",3,"MIT","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fcommunity\u002Fclawhub\u002Fp\u002Fpr-advocacy\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"# PR Advocacy Skill\n\n## Purpose\nActively monitor, respond to, and drive Pull Request reviews to completion. This skill ensures PRs don't get stuck in review limbo and addresses maintainer feedback promptly.\n\n## Core Responsibilities\n\n### 1. PR Status Monitoring\n- Check PR status every heartbeat cycle (1 hour)\n- Monitor CI\u002FCD check results\n- Track reviewer comments and requested changes\n- Identify blocking vs non-blocking feedback\n\n### 2. Professional Response Protocol\n- Acknowledge all reviewer feedback within 24 hours\n- Provide clear, technical responses to questions\n- Implement requested changes promptly when valid\n- Politely justify decisions when disagreeing with feedback\n\n### 3. Proactive Issue Resolution\n- Fix CI\u002FCD failures immediately\n- Address merge conflicts proactively  \n- Update documentation when code changes\n- Add tests for edge cases identified by reviewers\n\n### 4. PR Health Assessment\n- **Green Status**: All checks pass, no pending reviews → Wait for merge\n- **Yellow Status**: Minor feedback, passing checks → Respond and wait\n- **Red Status**: Failing checks or major feedback → Immediate action required\n- **Stale Status**: No activity for 48+ hours → Gentle ping to reviewers\n\n## PR Status Processing Rules\n\n### OPEN State Handling\nWhen a PR is in OPEN state:\n- **Check for maintainer\u002Freviewer comments** pointing out issues\n- **If feedback requires changes**:\n  - Analyze the specific feedback content\n  - Create fixes according to maintainer suggestions\n  - Automatically commit changes to the PR branch\n  - Update PR description if needed\n  - Record fix details for learning\n- **If no issues found**:\n  - Continue monitoring CI\u002FCD status\n  - Wait for merge approval\n\n### CLOSED\u002FREJECTED State Handling  \nWhen a PR is CLOSED or REJECTED:\n- **Immediately remove from active tracking list**\n- **Stop all monitoring activities** for this PR\n- **Record closure reason** for future learning and improvement\n- **Do not attempt to resubmit** unless explicitly instructed\n\n### MERGED State Handling\nWhen a PR is successfully MERGED:\n- **Remove from active tracking list**\n- **Add to merged records** for success tracking\n- **Celebrate the contribution!**\n- **Update skills and workflows** based on successful patterns\n\n## Real-time Tracking List Synchronization\n\n### Automatic Updates\n- **After any PR status change**, immediately update the tracking list file\n- **When PRs are added\u002Fremoved**, synchronize the tracking list in real-time\n- **Prevent information loss** by ensuring all changes are persisted to disk\n- **Maintain accurate state** by writing updates immediately after processing\n\n### Tracking List File Management\n- **Location**: `\u002FUsers\u002Fhope\u002F.openclaw\u002Fagents\u002Fcoding\u002Fworkspace\u002Fmemory\u002Fpr-tracking-list.md`\n- **Format**: Markdown with clear sections for active, closed, and merged PRs\n- **Updates**: Atomic writes to prevent corruption during concurrent access\n- **Backup**: Maintain version history through git commits for rollback capability\n\n### Synchronization Workflow\n1. **Detect PR status change** (OPEN\u002FCLOSED\u002FMERGED)\n2. **Process the change** according to status rules\n3. **Update tracking list file** immediately with new state\n4. **Verify file integrity** to ensure no data loss\n5. **Log the update** for audit trail and debugging\n\n### Error Handling\n- **File write failures**: Retry with exponential backoff\n- **Concurrent access**: Use atomic file operations to prevent race conditions\n- **Data corruption**: Validate file format before and after updates\n- **Recovery**: Maintain backup copies for emergency restoration\n\n## Implementation Guidelines\n\n### Check Status Analysis\n```bash\n# Check PR status and checks\ngh pr view \u003CPR_NUMBER> --json statusCheckRollup,reviewDecision\n\n# Common check statuses:\n# - SUCCESS: All good\n# - FAILURE: Needs immediate fixing  \n# - PENDING: Still running\n# - NEUTRAL: Non-blocking (like coverage)\n```\n\n### Reviewer Feedback Response Template\n```\nThanks for the review! \n\nFor [specific comment]:\n- [Action taken or explanation]\n- [Technical justification if disagreeing]\n\nI've [implemented the change \u002F pushed an update \u002F clarified the approach] in [commit reference].\n\nLet me know if you need any additional changes!\n```\n\n### Common PR Issues & Solutions\n\n#### CI\u002FCD Failures\n- **Lint errors**: Run `npm run lint -- --fix` locally first\n- **Test failures**: Reproduce locally, add missing test cases\n- **Build errors**: Verify dependencies, check Node.js version compatibility\n\n#### Code Review Feedback  \n- **Style issues**: Follow project's `.editorconfig` and style guide\n- **Architecture concerns**: Reference existing patterns in codebase\n- **Security concerns**: Prioritize security fixes, add validation layers\n\n#### Documentation Gaps\n- **Missing docs**: Add\u002Fupdate relevant documentation files\n- **Inconsistent formatting**: Use project's markdown template\n- **Outdated examples**: Update code examples to match new implementation\n\n## Automation Integration\n\n### Heartbeat Integration\n- Integrate with existing heartbeat monitoring system (every hour)\n- Add PR status to daily summary reports\n- Escalate stale PRs after 48 hours of inactivity\n\n### Memory Tracking\n- Maintain PR tracking list in workspace memory\n- **Automatically clean up closed\u002Frejected PRs** from tracking list\n- **Real-time synchronization** of tracking list file after any PR status change\n- Record resolution outcomes for learning\n- Update core memory with successful advocacy patterns\n\n### Automatic Response Workflow\n1. **Detect feedback** on OPEN PRs\n2. **Analyze requirements** and create appropriate fixes\n3. **Commit changes** to existing PR branch\n4. **Update tracking status** and notify maintainers\n5. **Handle closure** by removing from active monitoring\n6. **Synchronize tracking list file** immediately after any change\n\n## Success Metrics\n\n- **Response time**: \u003C 24 hours to reviewer feedback\n- **Resolution rate**: > 90% of PRs merged within 7 days  \n- **Rework rate**: \u003C 10% of PRs require major revisions after initial review\n- **Maintainer satisfaction**: Positive feedback from maintainers on communication quality\n- **Data integrity**: 100% tracking list accuracy with zero information loss\n\n## Best Practices\n\n### Communication\n- Be concise but thorough in responses\n- Use code blocks for technical explanations\n- Reference specific line numbers when discussing changes\n- Thank reviewers for their time and expertise\n\n### Technical Excellence  \n- Ensure changes are minimal and focused\n- Maintain backward compatibility when possible\n- Follow project conventions exactly\n- Test changes thoroughly before pushing\n\n### Professionalism\n- Never argue with reviewers; seek to understand their perspective\n- Admit mistakes quickly and fix them\n- Offer to help with related issues when appropriate\n- Celebrate successful merges and thank maintainers",{},"master","4aa004da461d820f4ea5499e58eb8d196cf99016","community\u002Fclawhub\u002Fp\u002Fpr-advocacy",0,"https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge","https:\u002F\u002Fskill-explorer-rho.vercel.app","https:\u002F\u002Fgithub.com\u002FLord1Egypt","Unbreakable. Unstoppable. Unmatched⚡.\r\n Speaker of machine tongues 🤖  | World-builder of decentralized dreams 🌐 | Defender of the digital realm🛡️.","2026-06-10 08:21:01",{"source":7,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add Lord1Egypt\u002Fawesome-skill-forge --skill pr-advocacy",{"tool":37,"command":38},"bunx","bunx skills add Lord1Egypt\u002Fawesome-skill-forge --skill pr-advocacy",{"tool":40,"command":41},"pnpm","pnpm dlx skills add Lord1Egypt\u002Fawesome-skill-forge --skill pr-advocacy","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fcommunity\u002Fclawhub\u002Fp\u002Fpr-advocacy\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M785WKJB99G3STR1NF9NRTJW","youtube-content","YouTube transcripts to summaries, threads, blogs.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fyoutube-content\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":18},"01M785WEFHB0G2S9YA6EPR3H0E","xurl","X\u002FTwitter via xurl CLI: post, search, DM, media, v2 API.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fxurl\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M785W98EDN4EFJXJPMQEHCRC","touchdesigner-mcp","Control a running TouchDesigner instance via twozero MCP — create operators, set parameters, wire connections, execute Python, build real-time visuals. 36 native tools.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Ftouchdesigner-mcp\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M785W5S9FP3QBH2V191E025P","test-driven-development","TDD: enforce RED-GREEN-REFACTOR, tests before code.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Ftest-driven-development\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M785W2AS08NSSH9YATCV6FJB","teams-meeting-pipeline","Operate the Teams meeting summary pipeline via Hermes CLI — summarize meetings, inspect pipeline status, replay jobs, manage Microsoft Graph subscriptions.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fteams-meeting-pipeline\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M785VXKW4T34BTP1SCHW1R7F","systematic-debugging","4-phase root cause debugging: understand bugs before fixing.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fsystematic-debugging\u002FSKILL.md",[],[]]