소스 정보
- 저장소
- manti-by/demetra
- 최근 소스 활동
- 2026년 8월 20일 11:52
- 감지된 SKILL.md 언어
- 영어
- 스타
- 5
- 포크
- 0
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
메뉴
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/manti-by/demetra --skill merge-duplicated-wiki-pages명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
Generate two-word app release names based on space phenomena. Use when naming app versions, release codenames, milestones, or build labels with a consistent cosmic theme.
Revalidate AGENTS.md against the current codebase, wiki pages,
Archive old wiki pages (default > 3 months) by extracting any
SKILL.md 표시 중
| name | Merge duplicated wiki pages |
| description | Find and merge near-duplicate wiki pages (at least ~85% similar, |
You are the OpenWiki Dedup Agent. Read wiki/README.md and wiki/TEMPLATE.md
for conventions, then work through every page under wiki/pages/.
Read all pages. Read every .md file in wiki/pages/. Parse the
frontmatter (title, date, type, status, session_id, services, tickets,
tags, related) and the full body for each page.
Pairwise comparison. Compare every page against every other page once. For each pair, assess semantic similarity of the subject matter and content. A pair is a near-duplicate if they are at least approximately 85% similar — covering almost the same session, investigation, or topic from the same angle, or one is a different write-up of the same session. This includes exact duplicates. Consider overlapping TL;DRs, same session_id (a strong signal), nearly identical title/tags, and body content that restates the same findings. Distinct pages about different subsystems or different sessions are NOT duplicates even if they share tags.
Decide what to merge. Only auto-merge pairs that are the same session:
identical session_id, or clearly the same session recorded twice. For
pages from distinct sessions, do NOT merge — instead cross-link the two
pages: add each to the other's related frontmatter and add a
reciprocal body [[...]] link on both pages (the consistency agent
requires the two representations to stay in sync), then move on. If the
two pages make materially conflicting claims (opposite statuses,
contradicting facts), do NOT auto-merge: verify which claim is current
against the codebase/docs first, or file a question in
wiki/QUESTIONS.md and skip the pair.
Merge each eligible pair. For each near-duplicate pair, pick a survivor filename and merge the second page into it:
date: in frontmatter). If the
dates are equal, prefer the page with the more complete, more accurate
content; tie-break deterministically (e.g. lexicographically smaller
filename). Do NOT infer recency from session_id.title, date, session_id,
type, status, branch. Union services, tickets, tags, and
related (deduplicated). When singular fields disagree, keep the value
from the page whose claims you verified in step 3 and note the choice in
the body. Remove BOTH the survivor filename and the deleted filename from
the merged related list — a page must not link to itself.[[...]]) from both pages so nothing points at the deleted
filename.Clean up. Delete the duplicate page file from wiki/pages/.
Update metadata. After each merge, update every wiki file that references the deleted page:
wiki/INDEX.md — remove the deleted entry from ## Pages and from
## By topic; if the survivor's title or summary changed, update its
entry in both sections. Keep newest-first order.wiki/QUESTIONS.md — point any **Pages:** reference at the survivor or
drop the deleted filename.wiki/.openwiki-sessions.json — redirect every mapping whose value is
the deleted filename to the survivor; drop any stale entry whose key is a
different session id but whose value is the survivor filename.related: frontmatter and body [[...]]
links that reference the deleted filename to point at the survivor (or
remove them if the content was fully merged).Repeat steps 2-6 until no more eligible near-duplicates are found (a merged page might now be similar to another page).
Report: how many duplicate pairs were found, which pages were merged (survivor ← deleted), which distinct-session pairs were cross-linked instead, and what changed in the INDEX.