copilot-address-reviews
逐条验证并处理 GitHub Copilot 的 PR 审查意见,修复并提交代码
相关性达标的全量 Skills(含未精选长尾)· 共 6259 个
逐条验证并处理 GitHub Copilot 的 PR 审查意见,修复并提交代码
对现有 PR 执行分级审查并在满足条件时自动把关合并的管道
测评一个 AI skill(SKILL.md 那种技能包)并生成一份简约的单页长滚动 HTML。指向一个 skill 文件夹,自动读 SKILL.md 及配套文件,讲解它是什么、适合谁、怎么装、结构架构、工作流程,并做六维打分。产出一个可直接在浏览器打开、可分享的单文件 HTML。触发词:测评这个skill、skill测评、讲清楚这个skill、给这个skill做个介绍页、skill radar、评估一下这个技能包。
Use this skill when asked to prepare a release checklist from repository metadata.
Use this skill when asked to review a small service and summarize its important modules.
Review a repository and explain its architecture when asked.
Statically audit Agent Skill directories for invalid SKILL.md structure, weak metadata, broken local references, packaging problems, and risky script or instruction patterns. Use when reviewing, validating, publishing, installing, or CI-checking a Codex, Claude Code, or compatible Agent Skill, especially before trusting a third-party Skill.
Convert a PDF to one clean markdown file, preserving wrapped tables and rendering diagrams as faithful transcription.
Sets up a multi-repo workspace so one session can see a whole system — sibling repos plus the cross-cutting folders no single repo owns — and generates the root CLAUDE.md map by reading each repo rather than being told. Use when starting work across several related repos, onboarding onto an unfamiliar system, or when Claude keeps missing context that lives in a sibling repo. Trigger: "set up the workspace", "map this project", "I have several repos", "onboard me onto this", "create the root CLAUDE.md".
Builds a print-quality PDF user manual for an application — learns the product by reading the codebase, drives the real UI with Playwright to capture screenshots, writes the prose against what was actually captured, and renders a paginated PDF with cover, table of contents, figures and callouts. Use when asked for a user manual, operator guide, onboarding handbook, client handover documentation, or training material. Trigger: "make a user manual", "write documentation for this app", "operator guide", "client handover doc", "PDF manual", "training guide".
Gives Claude Code non-interactive SSH access to a server and then writes a server-info folder by interrogating the machine — services, ports, deploy paths, logs, databases — rather than being told. Use when adding a dev or production server to a workspace, onboarding onto infrastructure nobody documented, or when Claude cannot reach a machine it needs. Trigger: "connect to the server", "set up ssh", "document this server", "add the dev server", "why can't you reach the box".
Validates work completed by /executor agents. Reviews contract compliance, test quality, edge cases, security, performance, and integration correctness in a fresh context, refutes its own findings before reporting them, and gates the verdict on recorded exit codes. Runs after a phase or the full plan is implemented. Trigger: "review phase", "validate the work", "check what was implemented", "run review", "quality check".
Restores working context after a /clear or /compact by reading the most recent session handoff plus current git state, then reports where things stand and what the next step is. Use at the start of a session, after clearing or compacting, when picking up work from a previous day, or when taking over someone else's branch. Trigger: "resume", "pick up where we left off", "what was I doing", "restore context", "continue from the handoff", "catch me up".
Deep multi-perspective codebase investigation. Use when: analyzing feasibility of a new feature, auditing code for issues, investigating bugs, evaluating technical debt, or assessing any change before planning. Dispatches investigations across the dimensions that matter for the question asked, refutes every finding before reporting it, and synthesizes into one actionable report. Trigger: "investigate this", "is this feasible", "analyze my codebase", "audit this", "what would it take to", "assess this", "can we do this", "deep dive", "research this before we start".
Writes a session handoff to disk before a context reset — what's done, what changed, what was decided, what was ruled out, and the single next step — then tells you whether to /clear or /compact. Use when a session is getting long or slow, before compacting, at the end of a work block, or when handing work to another person or session. Trigger: "write a handoff", "save progress", "save state", "session is getting slow", "before I compact", "wrap up", "I'm stopping here".
Verifies frontend changes in a real browser — screenshots at multiple viewports, console errors, accessibility snapshot — then fixes what it finds and re-verifies. Scopes to routes touched by the current diff when no URL is given. Use after changing UI code, before shipping a frontend change, when a page "looks wrong", or when asked whether something actually works in the browser. Trigger: "check the UI", "does this look right", "screenshot the page", "verify the frontend", "review the design", "test it in the browser".
Implements a plan created by /architect. Reads the plan, claims a phase, works one task at a time in an isolated branch or worktree, verifies externally, commits, and records state in its own single-writer file. Designed for multi-agent parallel execution. Trigger: "execute the plan", "implement phase", "continue the plan", "work on next task", "pick up where we left off".
Orchestrates the full plan-execute-review pipeline. Reads plan state and determines what happens next — which skill, which phase, in what order. Runs advisory by default, or autonomously behind explicit guardrails. Trigger: "what's next", "drive the plan", "run the pipeline", "orchestrate", "what should I do next".
Records durable technical decisions with their reasoning, and searches them before a settled question gets re-opened. Use when an architectural, scope, tooling or vendor choice is made or reversed, when someone asks "why is it like this", or before proposing an approach that may already have been rejected. Trigger: "log this decision", "why did we choose", "did we try", "have we decided", "record that we're not doing", "was this considered".
Connects Claude Code to a ClickUp workspace and writes its own reference notes — workspace, spaces, folders, list IDs, assignee IDs, and the API quirks it hits — so future sessions can read and update tasks without rediscovering the workspace every time. Use when wiring a task tracker into a workspace or when task IDs keep getting looked up by hand. Trigger: "connect clickup", "set up the task board", "read my tasks", "sync tasks", "what's assigned to me".
Analyzes a problem and generates a phased execution plan with progress tracking, shared contracts, dependency graphs, per-phase isolation, and task-level detail. Use when tackling any large feature, refactor, migration, or complex fix. Trigger: "plan this", "break this down", "architect this", "create a plan".
Produce, creatively direct, revise, review, recover, and machine-check complete hand-drawn videos from Chinese stories, scripts, diary entries, comic pages, or ordered images. Use for narrative-arc selection, style bake-offs, multi-shot planning, deterministic hand-drawn motion, resumable image providers, continuity, scene retakes, multi-ratio rendering, page flips, automatic local sound design or narration, semantic and pixel QA, visual review, snapshots, and final MP4 delivery.
将 biji.com/得到大脑订阅博主的笔记导出为 Markdown。
通过 Rube MCP(Composio)自动化管理 ConvertKit 的订阅者、标签与广播。
作为写作伙伴提供研究、提纲、逐段润色与引用支持,提升内容质量。
通过 Composio/Rube MCP 自动化创建、搜索与管理 Confluence 页面与空间。
提供 nmap、metasploit、hydra 等渗透测试常用命令参考。
用于规划与执行渗透测试的全面检查表与方法论。
提供PDF读取、提取、合并、拆分与表单处理等操作指南与示例。
为 Next.js 14+ 提供高级全栈开发与优化支持。
配置与测试常见网络服务(HTTP/HTTPS/SNMP/SMB)以搭建渗透测试实验环境。
指导使用 Metasploit 进行漏洞利用、载荷生成与后渗透操作。
分析日志并做错误聚类、频率与时间分布报告以定位根因与高发时段。
为前端代码库配置 i18n、替换硬编码文案并校验中英文覆盖与复数规则。
提供生产级 Bash 脚本模板,用于自动化常见 Linux 运维任务。
系统化枚举与利用 Linux 常见提权向量以获取更高权限。
系统化检测与利用 Insecure Direct Object Reference(IDOR)漏洞的方法论。
按步增加并发对 HTTP 服务压测,收集 p50/p90/p99 并检测性能拐点。
检测与利用 HTML 注入漏洞,评估内容注入与页面篡改风险(授权测试)。
识别与利用路径遍历漏洞以读取服务端任意文件(用于授权测试)。