القائمة
DEPRECATED — use the pair-* skill series (e.g. pair-consult / pair-optimize) instead. Evaluates inline feedback annotations on a markdown plan by verifying each critique against the codebase and context using subagents.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Audit and improve AGENTS.md files in repositories, keeping CLAUDE.md as a one-line @AGENTS.md reference so the same project memory works across tools (Claude Code, Codex, Gemini CLI, …). Use when user asks to check, audit, update, improve, or fix AGENTS.md (or CLAUDE.md) files. Scans for all such files, evaluates quality against templates, outputs quality report, then makes targeted updates. Also use when the user mentions "AGENTS.md maintenance" or cross-tool "project memory optimization".
Graph a skill's flow — steps, artifacts, invocations — render it with draw-graphology, and report checkable weak links — each verified by two independent subagents — as a handoff file of lessons for improve-skills.
Summarize the CURRENT Claude session's work into a very concise 3P (Progress/Plans/Problems) Slack status report, draft it to the user for review, then place it as a native Slack draft for a final look before they send. User-invoked mid-session (`/slack-comm`) when you need to report what you just did in a tight, matter-of-fact format. Not for org-scale newsletters or pulling other people's updates.
Fold one lesson into one existing skill, behind a confirmation gate.
Unattended cleanup loop — scan the codebase for readability debt and run up to N targets (default 5) through a cleaner/reviewer/tester trio; verified cleanups land as per-target refactor commits on a clean-loop/<date> branch. Not a performance tool (pair-ratchet) and not for polishing just-written code (simplify-python).
Create data-driven network graph visualizations with graphology + sigma.js. Use when the user wants to visualize a network, dependency graph, knowledge graph, call graph, org/relationship map, communities/clusters, or any node-edge dataset too large to place by hand.
| name | get-feedback-markdown-plan |
| version | 1.0.0 |
| description | DEPRECATED — use the pair-* skill series (e.g. pair-consult / pair-optimize) instead. Evaluates inline feedback annotations on a markdown plan by verifying each critique against the codebase and context using subagents. |
⚠️ Deprecated. Use the
pair-*skill series (e.g.pair-consult,pair-optimize) instead. This skill is no longer installed and is kept only for reference.
You have a markdown plan with inline feedback annotations (e.g., [CODEX], [Claude], or similar tags). Your job is to verify whether each annotation is correct by checking it against the codebase and project context.
Parse — Extract all inline annotations from the plan. For each one, capture the annotation text and the plan section it refers to.
Group — Cluster related annotations that share context (e.g., multiple comments about the same service, same migration step, or same data flow). Each group becomes one subagent task.
Verify — Launch one subagent per group in parallel. Each subagent receives:
Report — Present a summary table:
| # | Annotation | Verdict | Reason |
|---|---|---|---|
| 1 | ... | Correct / Wrong / Inconclusive | One-line explanation |
Then list the annotations that were Wrong with full reasoning, so the user knows which feedback to ignore.
