跳到正文
FunCoding

搜索

搜索文档、Skill 和 MCP

second-brain-merge

Merge two pages that describe the same thing, preserving every distinct claim, redirecting inbound links, and recording the merge. Use this skill when the user approves a duplicate merge, says "these are the same page", "merge X into Y", or asks to clean up near-duplicates that a lint run proposed. Do NOT use to merge pages on your own judgement, to delete a page outright, or to split one page into several.

代码质量与审查1kskills/second-brain-merge/SKILL.md

安装

把这段话发给 Claude Code、Codex 或 Cursor。智能体会先检查安全性,你确认后才安装。

读取 https://funcoding.ai/skills/undefined-ui/second-brain-os/second-brain-merge/install.md ,按里面的步骤帮我安装这个 Skill。

SKILL.md

Merge duplicate pages

A merge is irreversible in the way that matters: afterwards you cannot tell which claim came from which page. Two ideas that look identical from their summaries are often a general case and a specific one.

Core rule

Never merge unprompted. Propose, wait for approval, then follow the procedure exactly.

Workflow

  1. Pick the survivor by canonical name, not by which page is longer.
  2. Merge content. Every distinct claim survives with its source. Overlapping claims collapse; differing ones both stay, following the contradiction rules.
  3. Merge aliases, including the dead page's title as an alias on the survivor. This is what keeps old links and the user's memory working.
  4. Redirect inbound links to the survivor. Check every backlink.
  5. Delete the old page, or leave a stub only if it was linked from outside the vault.
  6. Record in log.md: both names, the date, and why.

Output format

Merged: [[old]] -> [[survivor]]
Claims kept from old page: <n>
Aliases added: <list>
Inbound links redirected: <n>
Conflicts recorded: <none | description>

Calibration

If the two pages disagree about anything factual, that is a signal they may not be duplicates. Surface the disagreement and ask before proceeding.

Never merge a page marked maintained_by: human into another without explicit confirmation naming that page.

相似的 Skill

claude-api
anthropics/skills180k

claude-api

Reference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file).

代码质量与审查

ponytail-review
DietrichGebert/ponytail158k

ponytail-review

Quality review of a change: is the logic right, is it safe, does it hold under real load, is risky code tested, is it fast enough, and is every line needed. Reads the connected code, not only the diff. Each finding is explained in plain English. Use for "review this", "code review", "review the last commit", "review my PR", "is this over-engineered", /ponytail-review.

代码质量与审查

code-review-and-quality
addyosmani/agent-skills103k

code-review-and-quality

Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch. Use when asked to review a diff or a pull request, even when the diff is pasted inline.

代码质量与审查

documentation-and-adrs
addyosmani/agent-skills103k

documentation-and-adrs

Records decisions and documentation. Use when you need to document an architecture decision (ADR) or the reasoning behind a design choice, when changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.

代码质量与审查

code-simplification
addyosmani/agent-skills103k

code-simplification

Simplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity.

代码质量与审查

understand
Egonex-AI/Understand-Anything86k

understand

Analyze a codebase to produce an interactive knowledge graph for understanding architecture, components, and relationships

代码质量与审查