ai-wiki-consolidate-drafts

Use when handle-local AI wiki drafts have grown into a noisy backlog and related notes should be clustered, refined, or promoted without directly rewriting shared docs by default.

Aller à l'installation

Dépôt: BochengYin/ai-wiki-toolkit
Dernière activité de la source: 21 avril 2026 à 10:48
Langue détectée de SKILL.md: anglais
Étoiles: 6
Forks: 0

Options d'installation

Le prompt qui vérifie d'abord la source est sélectionné par défaut. Vous pouvez passer à une commande directe ou télécharger une copie locale.

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.

npx skills add https://github.com/BochengYin/ai-wiki-toolkit --skill ai-wiki-consolidate-drafts

La commande reste sur une seule ligne. Faites défiler horizontalement pour la vérifier avant de la copier.

Vous préférez une copie locale ? Téléchargez les fichiers actuellement disponibles dans SkillsMP.

Vérifiez les fichiers source

Lisez SKILL.md et les fichiers associés affichés par SkillsMP avant de décider de l'installer.

Explorateur de fichiers

6 fichiers

SKILL.md

Instructions source · Aperçu en lecture seule

Retour à la recherche Retour à l’installation

ai-wiki-update-check

Produce the mandatory end-of-task AI wiki write-back outcome for ai-wiki-toolkit. Use it to record only public/local trial-error memory or reusable clarification memory, then emit the required final status line.

2026-06-14

ai-wiki-reuse-check

Produce the mandatory end-of-task AI wiki reuse evidence for ai-wiki-toolkit. Use it to classify task relevance, record consulted user-owned docs, append local telemetry, and emit the user-facing footer.

2026-04-25

ai-wiki-release-tag

Use after a release-prep PR is merged when the repo is ready to create and push a semantic release tag from main.

2026-04-21

Tout voir dans ce dépôt

AI Wiki Consolidate Drafts

Use this skill when ai-wiki/people/*/drafts/ has accumulated related notes and the next step is to consolidate them into clearer draft clusters, promotion candidates, or explicit conflicts and supersessions.

Workflow

Read the relevant draft set, usually under one handle in ai-wiki/people/*/drafts/.

Read nearby context that may confirm or narrow the consolidation target:

ai-wiki/conventions/index.md
ai-wiki/decisions.md
ai-wiki/review-patterns/index.md
ai-wiki/problems/index.md
ai-wiki/features/index.md
relevant files under ai-wiki/trails/ when chronology matters
ai-wiki/metrics/ and _toolkit/metrics/*.json only as weak signals

Cluster drafts by durable topic, repeated failure mode, or repeated rule, not by filename alone.

For each cluster, choose one next action using references/candidate-types.md.

Use references/promotion-targets.md to propose the best destination when a cluster is mature enough for shared or repo-level memory.

Use references/conflict-and-supersession.md to flag conflicts, refinements, or supersession instead of silently merging away differences.

Default to refining handle-local drafts first. Do not directly rewrite ai-wiki/conventions/*.md, ai-wiki/review-patterns/*.md, ai-wiki/problems/*.md, or ai-wiki/features/*.md unless the user explicitly asks for promotion or doc creation.

Emit the result using references/output-contract.md.

Rules

Cluster first, judge second.

Do not promote every repeated draft.

Metrics may support prioritization, but they are weak signals and must not be the sole basis for promotion.

Make the suggested target path explicit whenever the action is Refine draft or Promotion candidate.

If a cluster is still unstable, keep it local and explain what evidence is still missing.

Shared conventions and review patterns still require human confirmation before writing shared docs.