Community编程与开发github.com

everyinc/ce-resolve-pr-feedback

通过并行评估有效性和修复问题来解决PR审查反馈。适用于处理PR审查评论、解决审查线程或修复代码审查反馈。

ce-resolve-pr-feedback 是什么?

此技能用于高效处理GitHub PR(拉取请求)的审查反馈。它通过并行方式,首先评估每条评论或建议的有效性,然后自动或引导用户修复问题。适用于Claude Code等AI编码代理平台,帮助开发者快速响应代码审查意见,减少人工逐条审查和修复的工作量。其工作流程包括解析PR评论、判断是否为有效反馈、对有效反馈生成修复方案,并可能自动创建新的提交来应用更改。该技能能显著提升团队协作效率,确保审查闭环。

兼容平台~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/everyinc/compound-engineering-plugin/tree/main/skills/ce-resolve-pr-feedback

Installed? Explore more 编程与开发 skills: steipete/bluebubbles, steipete/eightctl, steipete/blucli · View all 6 →

在你喜欢的 AI 中提问

打开一个已预加载此 Agent Skill 的新对话。

文档

ce-resolve-pr-feedback 是做什么的?

通过并行评估有效性和修复问题来解决PR审查反馈。适用于处理PR审查评论、解决审查线程或修复代码审查反馈。

概述

此技能旨在帮助AI代理(如Claude Code)高效处理PR(拉取请求)中的审查反馈。它通过并行工作流,先评估每条反馈的有效性,再对有效反馈应用修复,从而加速代码审查的闭环流程。

使用方法

当收到PR审查评论时,可以调用此技能来:

  • 列出所有未解决的审查线程
  • 评估每条评论是否有效(例如,建议是否合理、是否已被其他更改覆盖)
  • 对有效反馈生成并应用代码修复
  • 标记已解决的线程并提交新的更改

支持平台

  • Claude Code
  • 其他支持MCP(模型上下文协议)的AI编码代理

工作流程

  1. 获取反馈:从PR中获取所有未解决的审查评论
  2. 并行评估:同时评估每条评论的有效性(例如,检查代码上下文、依赖关系)
  3. 修复问题:对有效评论生成修补程序,并应用更改
  4. 更新状态:标记线程为已解决,并创建新的提交(可选)

配置

需要设置以下环境变量:

  • GITHUB_TOKEN:具有PR读写权限的GitHub个人访问令牌
  • GITHUB_REPOSITORY:目标仓库(例如 owner/repo)

示例

# 假设在仓库根目录下运行
# 该技能会自动检测当前分支对应的PR

注意事项

  • 确保有足够的权限访问目标仓库和PR
  • 评估反馈时,可能需要对项目结构和编码规范有一定了解
  • 自动生成的修复可能需要人工审查后再提交

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

everyinc/ce-agent-native-architecture

Build applications where agents are first-class citizens. Use this skill when designing autonomous agents, creating MCP tools, implementing self-modifying systems, or building apps where features are outcomes achieved by agents operating in a loop.

everyinc/ce-agent-native-audit

Run comprehensive agent-native architecture review with scored principles

everyinc/ce-brainstorm

Explore requirements and approaches through collaborative dialogue, then write a right-sized requirements document. Use when the user says "let's brainstorm", "what should we build", or "help me think through X", presents a vague or ambitious feature request, or seems unsure about scope or direction -- even without explicitly asking to brainstorm.

everyinc/ce-clean-gone-branches

Clean up local branches whose remote tracking branch is gone. Use when the user says "clean up branches", "delete gone branches", "prune local branches", "clean gone", or wants to remove stale local branches that no longer exist on the remote. Also handles removing associated worktrees for branches that have them.

everyinc/ce-code-review

Structured code review using tiered persona agents, confidence-gated findings, and a merge/dedup pipeline. In interactive mode it applies safe, verified fixes and commits them when the working tree is clean (it never pushes); in mode:agent it reports only and the caller applies. Use when reviewing code changes before creating a PR.

everyinc/ce-commit

Create a git commit with a clear, value-communicating message. Use when the user says "commit", "commit this", "save my changes", "create a commit", or wants to commit staged or unstaged work. Produces well-structured commit messages that follow repo conventions when they exist, and defaults to conventional commit format otherwise.

everyinc/ce-commit-push-pr

Commit, push, and open a PR with an adaptive, value-first description that scales in depth with the change. Use when the user says "commit and PR", "ship this", "create a PR", or "open a pull request". Also handles description-only flows ("write a PR description", "rewrite the PR body", "describe this PR") without committing or pushing.

everyinc/ce-compound

Document a recently solved problem to compound your team's knowledge or CONCEPTS.md, the project's shared domain vocabulary.

everyinc/ce-compound-refresh

Refresh stale learning and pattern docs under docs/solutions/ by reviewing them against the current codebase, then updating, consolidating, or deleting drifted ones. Use when the user asks to "refresh my learnings", "audit docs/solutions/", "clean up stale learnings", or "consolidate overlapping docs", or when ce-compound flags an older doc as superseded. Do not trigger for general refactor, debugging, or code-review work unless the user has explicitly pointed at docs/solutions/.

everyinc/ce-debug

Systematically find root causes and fix bugs. Use when debugging errors, investigating test failures, reproducing bugs from issue trackers (GitHub, Linear, Jira), or when stuck on a problem after failed fix attempts. Also use when the user says 'debug this', 'why is this failing', 'fix this bug', 'trace this error', or pastes stack traces, error messages, or issue references.

everyinc/ce-demo-reel

Capture a visual demo reel (GIF, terminal recording, screenshots) for PR descriptions. Use when shipping UI changes, CLI features, or any work with observable behavior that benefits from visual proof. Also use when asked to add a demo, record a GIF, screenshot a feature, show what changed visually, create a demo reel, capture evidence, add proof to a PR, or create a before/after comparison.

everyinc/ce-dhh-rails-style

This skill should be used when writing Ruby and Rails code in DHH's distinctive 37signals style. It applies when writing Ruby code, Rails applications, creating models, controllers, or any Ruby file. Triggers on Ruby/Rails code generation, refactoring requests, code review, or when the user mentions DHH, 37signals, Basecamp, HEY, or Campfire style. Embodies REST purity, fat models, thin controllers, Current attributes, Hotwire patterns, and the "clarity over cleverness" philosophy.

everyinc/ce-doc-review

Review requirements or plan documents using parallel persona agents that surface role-specific issues. Use when a requirements document or plan document exists and the user wants to improve it.

everyinc/ce-frontend-design

Build web interfaces with genuine design quality, not AI slop. Use for any frontend work - landing pages, web apps, dashboards, admin panels, components, interactive experiences. Activates for both greenfield builds and modifications to existing applications. Detects existing design systems and respects them. Covers composition, typography, color, motion, and copy. Verifies results via screenshots before declaring done.

everyinc/ce-gemini-imagegen

This skill should be used when generating and editing images using the Gemini API (Nano Banana Pro). It applies when creating images from text prompts, editing existing images, applying style transfers, generating logos with text, creating stickers, product mockups, or any image generation/manipulation task. Supports text-to-image, image editing, multi-turn refinement, and composition from multiple reference images.

everyinc/ce-ideate

Generate and critically evaluate grounded ideas about a topic. Use when asking what to improve, requesting idea generation, exploring surprising directions, or wanting the AI to proactively suggest strong options before brainstorming one in depth. Triggers on phrases like 'what should I improve', 'give me ideas', 'ideate on X', 'surprise me', 'what would you change', or any request for AI-generated suggestions rather than refining the user's own idea.

everyinc/ce-optimize

Run metric-driven iterative optimization loops -- define a measurable goal, run parallel experiments, measure each against hard gates or LLM-as-judge scores, keep improvements, and converge on the best solution. Use when optimizing clustering quality, search relevance, build performance, prompt quality, or any measurable outcome that benefits from systematic experimentation.

everyinc/ce-plan

Create structured plans for multi-step tasks -- software features, research workflows, events, study plans, or any goal that benefits from breakdown. Also deepens existing plans with interactive sub-agent review. Use when the user says 'plan this', 'create a plan', 'how should we build', 'break this down', or when a brainstorm doc is ready for planning. Use 'deepen the plan' or 'deepening pass' for the deepening flow. For exploratory requests, prefer ce-brainstorm first.

everyinc/ce-polish-beta

[BETA] Start the dev server, open the feature in a browser, and iterate on improvements together.

everyinc/ce-product-pulse

Generate a time-windowed pulse report on what users experienced and how the product performed - usage, quality, errors, signals worth investigating. Use when the user says 'run a pulse', 'show me the pulse', 'how are we doing', 'weekly recap', 'launch-day check', or passes a time window like '24h' or '7d'. Configures via .compound-engineering/config.local.yaml and saves reports to docs/pulse-reports/.

相关技能