re2zero

End-to-end automation: discover open-source GitHub repos, find fixable issues, analyze difficulty, fork/clone, implement fixes with self-testing, and submit merge-ready PRs. Supports two modes: target a specific repo/issue, or auto-discover active projects by domain (Linux, systems, CLI, etc.). Use when the user says "fix issue", "help me contribute", "find issues to fix", "auto-fix", "hunt for issues", "search repos and fix issues", "帮我去github找issue修", or references a GitHub issue/URL that should be resolved. Also use when the user wants to contribute to open-source but doesn't know where to start. Make sure to use this skill whenever the user mentions GitHub issues, PRs, open-source contribution, or finding bugs to fix in external repos, even if they don't explicitly invoke the skill name.

This skill should be used when the user asks to "find the root cause", "找根因", "为什么会出现这个问题", "why did this happen", "debug this issue", "排查问题", "analyze this bug", "分析这个bug", "what's causing this", "问题出在哪", "dig deeper", "深挖原因", or needs to systematically trace a problem back to its fundamental cause rather than just addressing symptoms.

Provides comprehensive code review guidance for React 19, Vue 3, Rust, TypeScript, Java, Python, and C/C++. Helps catch bugs, improve code quality, and give constructive feedback. Use when: reviewing pull requests, conducting PR reviews, code review, reviewing code changes, establishing review standards, mentoring developers, architecture reviews, security audits, checking code quality, finding bugs, giving feedback on code.

This skill should be used when the user asks to "create a mermaid diagram", "fix mermaid error", "mermaid syntax error", "diagram not rendering", "flowchart not working", "sequence diagram broken", "escape special characters in mermaid", or mentions "mermaid", "flowchart", "sequence diagram", "class diagram", "state diagram", "ER diagram", "gantt chart". Prevents common syntax errors with special characters, reserved words, escaping rules, and provides v11 syntax support.

Use when developing Deepin/UOS desktop applications with DTK widgets, GVfs file operations, DBus system integration, or Polkit authentication. Qt6/Qt5 dual support.

Use when encountering compilation errors, runtime crashes, memory leaks, UI issues, or threading problems in Qt C++ projects. Also use when MOC errors, undefined vtable references, missing Q_OBJECT macros, or signal-slot connection failures occur.

Use when generating Chinese format Excel reports from GitHub code reviews with AI analysis and filtering by date, branch, or reviewers

Use when maintaining Debian packages that need Qt5/Qt6 dual support, CMakeLists.txt has hard-coded Qt5/Qt6 or DTK5/DTK6 versions, or projects need dynamic library linking based on detected Qt version for deepin V25/V20 compatibility

GPUI framework and gpui-component UI library knowledge. Covers framework fundamentals (Actions, Async tasks, Context management, Entity state, Events, Focus, ElementId) and gpui-component components (Button, Input, Select, Dialog, Tabs, Sidebar, List, Table, Chart, Dock, Slider, Switch, Toggle, Combobox, etc.). Use when building any GPUI application — from framework-level concepts (actions, keybindings, async I/O, entity lifecycle, re-entrancy) to UI components and theming. Make sure to use this skill whenever working with GPUI, gpui-component, or any Rust UI framework based on GPUI — even if the user doesn't explicitly mention GPUI. Also use when the user asks about gpui_component::init, Root, WindowExt, or component patterns.