ReddRadar
Topic: code-review
652 skills in this topic.
-
requesting-code-review
完成任务、实现重要功能或合并前使用，用于验证工作成果是否符合要求
jnMetaCode/superpowers-zh 771
-
chinese-commit-conventions
中文 Git 提交规范 — 适配国内团队的 commit message 规范和 changelog 自动化
jnMetaCode/superpowers-zh 771
-
mcp-builder
MCP 服务器构建方法论 — 系统化构建生产级 MCP 工具，让 AI 助手连接外部能力
jnMetaCode/superpowers-zh 771
-
dispatching-parallel-agents
当面对 2 个以上可以独立进行、无共享状态或顺序依赖的任务时使用
jnMetaCode/superpowers-zh 771
-
systematic-debugging
遇到任何 bug、测试失败或异常行为时使用，在提出修复方案之前执行
jnMetaCode/superpowers-zh 771
-
workflow-runner
在 Claude Code / OpenClaw / Cursor 中直接运行 agency-orchestrator YAML 工作流——无需 API key，使用当前会话的 LLM 作为执行引擎。当用户提供 .yaml 工作流文件或要求多角色协作完成任务时触发。
jnMetaCode/superpowers-zh 771
-
chinese-documentation
中文技术文档写作规范——排版、术语、结构一步到位，告别机翻味
jnMetaCode/superpowers-zh 771
-
chinese-git-workflow
适配国内 Git 平台和团队习惯的工作流规范——Gitee、Coding、极狐 GitLab 全覆盖
jnMetaCode/superpowers-zh 771
-
subagent-driven-development
当在当前会话中执行包含独立任务的实现计划时使用
jnMetaCode/superpowers-zh 771
-
test-driven-development
在实现任何功能或修复 bug 时使用，在编写实现代码之前
jnMetaCode/superpowers-zh 771
-
writing-plans
当你有规格说明或需求用于多步骤任务时使用，在动手写代码之前
jnMetaCode/superpowers-zh 771
-
writing-skills
当创建新技能、编辑现有技能或在部署前验证技能是否有效时使用
jnMetaCode/superpowers-zh 771
-
executing-plans
当你有一份书面实现计划需要在单独的会话中执行，并设有审查检查点时使用
jnMetaCode/superpowers-zh 771
-
chinese-code-review
中文代码审查规范——在保持专业严谨的同时，用符合国内团队文化的方式给出有效反馈
jnMetaCode/superpowers-zh 771
-
brainstorming
在任何创造性工作之前必须使用此技能——创建功能、构建组件、添加功能或修改行为。在实现之前先探索用户意图、需求和设计。
jnMetaCode/superpowers-zh 771
-
using-superpowers
在开始任何对话时使用——确立如何查找和使用技能，要求在任何响应（包括澄清性问题）之前调用 Skill 工具
jnMetaCode/superpowers-zh 771
-
flow-next-opencode-work
Execute a Flow epic or task systematically with git setup, task tracking, quality checks, and commit workflow. Use when implementing a plan or working through a spec. Triggers on /flow-next:work with Flow IDs (fn-1, fn-1.2).
gmickel/flow-next-opencode 34
-
browser
Browser automation via agent-browser CLI. Use when you need to navigate websites, verify deployed UI, test web apps, read online documentation, scrape data, fill forms, capture baseline screenshots before design work, or inspect current page state. Triggers on "check the page", "verify UI", "test the site", "read docs at", "look up API", "visit URL", "browse", "screenshot", "scrape", "e2e test", "login flow", "capture baseline", "see how it looks", "inspect current", "before redesign".
gmickel/flow-next-opencode 34
-
flow-next-opencode-prime
Comprehensive codebase assessment for agent and production readiness. Scans 8 pillars (48 criteria), verifies commands work, checks GitHub settings. Reports everything, fixes agent readiness only. Triggers on /flow-next:prime.
gmickel/flow-next-opencode 34
-
flow-next-opencode
Manage .flow/ tasks and epics. Triggers: 'show me my tasks', 'list epics', 'what tasks are there', 'add a task', 'create task', 'what's ready', 'task status', 'show fn-1'. NOT for /flow-next:plan or /flow-next:work.
gmickel/flow-next-opencode 34
-
flow-next-opencode-rp-explorer
Token-efficient codebase exploration using RepoPrompt CLI. Use when user says "use rp to..." or "use repoprompt to..." followed by explore, find, understand, search, or similar actions.
gmickel/flow-next-opencode 34
-
flow-next-opencode-impl-review
John Carmack-level implementation review via RepoPrompt or OpenCode. Use when reviewing code changes, PRs, or implementations. Triggers on /flow-next:impl-review.
gmickel/flow-next-opencode 34
-
flow-next-opencode-setup
Local install of flowctl CLI and CLAUDE.md/AGENTS.md instructions. Use when user runs /flow-next:setup.
gmickel/flow-next-opencode 34
-
flow-next-opencode-export-context
Export RepoPrompt context for external LLM review (ChatGPT, Claude web, etc.). Use when you want to review code or plans with an external model. Triggers on /flow-next:export-context.
gmickel/flow-next-opencode 34