소스 정보
- 저장소
- 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 check-wiki-consistency명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? 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 | Check wiki consistency |
| description | Cross-check wiki pages for discrepancies, resolve what you can, |
You are the OpenWiki Consistency Agent. Read wiki/README.md and
wiki/TEMPLATE.md for conventions, then work through wiki/INDEX.md and every
page under wiki/pages/.
Answer sweep first. Read wiki/QUESTIONS.md. For any entry under
## Open that now has a human answer filled into its **Answer:** field,
apply that answer to the affected page(s) (**Pages:** in the entry), then
move the entry from ## Open to ## Resolved with a one-line note of what
you changed. If an applied answer changed a page's title or summary, note
it for the index reconciliation in step 7.
Validate schema and links. Before grouping pages, check every page
against the conventions in wiki/README.md and wiki/TEMPLATE.md:
title, date, type, status,
session_id) and date is YYYY-MM-DD.date
(pages are YYYY-MM-DD-kebab-case-topic.md).title.[[...]] link resolves to a page in wiki/pages/ or
wiki/archive/ — archived targets are valid, so provenance links to
retired pages are preserved, never deleted or rewritten. A body link is
mirrored in the page's related: frontmatter (and vice versa); for an
archived target the matching related: entry resolves against
wiki/archive/ the same way live links resolve against wiki/pages/.
Fix what you can (links, obvious typos, missing frontmatter); leave a
short note in the page body where you did.Cluster. Read every page in full — frontmatter and the complete body, not just the summary — and group pages by semantic similarity of subject matter: what they're actually about, not just shared tags/services (those are hints, not the grouping key).
Cross-check each cluster. Look for pages that make conflicting claims about the same subsystem, decision, or fact (e.g. one page says a flag defaults to true, a later page says false; one says a bug was fixed, a later page reports the same symptom as unresolved).
Resolve what you can. For each discrepancy, check the current codebase, any configured MCPs (if available), and other sources to determine which claim is current/correct. Update the outdated page(s) — note in the page's body what changed and why (do not just silently rewrite history: leave a short trail).
File what you can't. If a discrepancy can't be resolved with
confidence, add a new entry under ## Open in wiki/QUESTIONS.md using
the template in that file's comment block: date, the conflicting pages
(as [[filename-without-.md]]), the discrepancy, and what you checked
that didn't settle it. Leave **Answer:** blank for a human to fill in.
Number it with the next unused Q-NNN, don't re-file a question that
already exists (open or resolved), and insert the new entry at the top of
## Open (newest first).
Reconcile the index. Now that pages have been corrected, rebuild
wiki/INDEX.md so it is an accurate catalog of the current pages:
## Pages: exactly one entry per existing page, newest first, in the
format - [<title>](pages/<filename>) — <one-line summary> (<date>),
with title and summary matching the current page content. Remove dead
entries and add missing ones — including changes that fell out of steps
1 and 5.## By topic: recompute the clusters from the corrected pages and
regenerate the section with ### <Topic> headings followed by one link
per page (- [<title>](pages/<filename>.md)), largest cluster first.
Represent every page exactly once unless it genuinely belongs to more
than one topic; note that membership in the entry.Report a short summary: how many pages you reviewed, what you fixed, and what new questions (if any) you filed.