菜单
Process PR feedback, user corrections, code review findings, or self-observed patterns and update project memory, rules, and standards accordingly. Use proactively after receiving PR review comments, user corrections, or when patterns emerge from code review or self-reflection.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | learn-from-feedback |
| description | Process PR feedback, user corrections, code review findings, or self-observed patterns and update project memory, rules, and standards accordingly. Use proactively after receiving PR review comments, user corrections, or when patterns emerge from code review or self-reflection. |
When receiving feedback (PR comments, user corrections, code review findings) or observing patterns yourself during implementation, update the project's knowledge base so the same issues don't recur.
gh pr view $ARGUMENTS --comments) or parse the correction from contextreflect skill, or patterns noticed during implementation.claude/skills/coding-standards/SKILL.md.claude/rules/domain.md.claude/rules/testing.mdCLAUDE.md (Git Workflow section) or relevant skillMEMORY.md).claude/rules/testing.md (test helpers) or .claude/skills/coding-standards/SKILL.md (code patterns) so the pattern fires proactively next timeduklog coding standards, testing requirements, and review checklist. Use when reviewing code, writing tests, or checking quality.
Create a pull request after code review
Post-implementation retrospective. Run after completing any non-trivial task to extract patterns, surprises, and lessons and persist them to rules and memory without waiting for user feedback. Use proactively after creating a PR or finishing a significant feature.
Commit changes after running CI checks
Search Rust crate documentation for a type, trait, function, or method. Usage: /search-rust-doc {crate} {query}