ワンクリックでManusで任意のスキルを実行

docs-update

スター0

フォーク0

更新日2026年7月2日 11:10

Keep the charter's documents, status labels, README index, and CHANGELOG in sync after adding, editing, promoting, or retiring a Markdown document in this repo. Use after any non-trivial change to a document.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

robertschaub

robertschaub/our-ai-charter

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

/docs-update — keep the document set coherent

A small, repeatable pass to run after you change a document, so the repository stays internally consistent. This repo is documents-only: "done" means the prose and its surrounding index, labels, and change log all agree.

When to use

After you add, rename, substantially edit, promote (e.g. DRAFT → PUBLISHED), or retire any .md document under docs/.

Procedure

Status banner. A top-of-file status banner — a plain > **Status: …** blockquote (not a typed callout) — belongs on the normative docs (Charter Commitments, evaluation protocol, certification model, one-pager) and the outreach/parliamentary drafts (Non-Paper, Aktionsplan, Postulat), labelled DRAFT; on PUBLISHED <date> pages; and on the docs/wip/ notes, labelled WORKING NOTES — see AGENTS.md. If the doc is one of those, confirm its banner is present and accurate; otherwise (briefings, evidence, strategy, background) it carries no banner. The README index notes each document's status either way.
README index. Open the README. It presents Our AI Charter / the Public AI Network (this whole effort) — its overview, AI-infrastructure pillar, published articles, and the strategy/outreach/evidence — with AI Assurance & Certification as the trust-and-evidence building block, each document's status labelled inline. Move or add the document to the right section with a one-line description that matches its current framing. Remove stale entries.
Cross-links. Check that links between documents (and from the README) resolve — relative paths and correct filenames. Fix anything a rename broke.
CHANGELOG. Add a dated entry (ISO YYYY-MM-DD) in the CHANGELOG: what changed and, for the protocol/charter, the version bump. Keep entries terse and factual.
Public-repo check. Confirm nothing private/internal or any secret was introduced — this is a public repo (see AGENTS.md).
Commit. Use a conventional commit, e.g. docs(protocol): tighten the support rubric or docs: promote charter-commitments to published.

Output

A short summary: which document changed, its label before/after, the index/changelog edits made, and any broken links found and fixed.

このリポジトリの他の Skills

同じリポジトリ

privacy-guard

robertschaub/our-ai-charter

Redact strictly-personal content from text before it crosses a trust boundary, replacing each removed span with a typed placeholder (never the real value). Use automatically BEFORE: (1) sending text to an external model (scripts/agents/invoke-gpt or invoke-gemini, or text you propose the user paste into another AI); (2) writing or committing to a PUBLIC repo; (3) publishing, posting, or sharing text (issue, PR, email, site, or a DM to a third party). Also on request — "redact", "anonymise", "de-identify", "strip personal info / PII", or /privacy-guard. Does NOT redact text that stays inside a private repo for the maintainer's own use.

2026-07-080

doc-guard

robertschaub/our-ai-charter

Keep repository documentation lean, clear, and readable. Use automatically before adding a new document, substantially expanding or rewriting Markdown, adding explanatory/background sections, adding FAQs/glossaries/templates, introducing repeated framing, or reviewing a documentation diff for clutter, filler, duplication, over-broad prose, stale links, or readability problems.

2026-07-020

/docs-update — keep the document set coherent

When to use

After you add, rename, substantially edit, promote (e.g. DRAFT → PUBLISHED), or retire any .md document under docs/.

Procedure

Status banner. A top-of-file status banner — a plain > **Status: …** blockquote (not a typed callout) — belongs on the normative docs (Charter Commitments, evaluation protocol, certification model, one-pager) and the outreach/parliamentary drafts (Non-Paper, Aktionsplan, Postulat), labelled DRAFT; on PUBLISHED <date> pages; and on the docs/wip/ notes, labelled WORKING NOTES — see AGENTS.md. If the doc is one of those, confirm its banner is present and accurate; otherwise (briefings, evidence, strategy, background) it carries no banner. The README index notes each document's status either way.

README index. Open the README. It presents Our AI Charter / the Public AI Network (this whole effort) — its overview, AI-infrastructure pillar, published articles, and the strategy/outreach/evidence — with AI Assurance & Certification as the trust-and-evidence building block, each document's status labelled inline. Move or add the document to the right section with a one-line description that matches its current framing. Remove stale entries.

Cross-links. Check that links between documents (and from the README) resolve — relative paths and correct filenames. Fix anything a rename broke.

CHANGELOG. Add a dated entry (ISO YYYY-MM-DD) in the CHANGELOG: what changed and, for the protocol/charter, the version bump. Keep entries terse and factual.

Public-repo check. Confirm nothing private/internal or any secret was introduced — this is a public repo (see AGENTS.md).

Commit. Use a conventional commit, e.g. docs(protocol): tighten the support rubric or docs: promote charter-commitments to published.

Output

A short summary: which document changed, its label before/after, the index/changelog edits made, and any broken links found and fixed.

name	docs-update
description	Keep the charter's documents, status labels, README index, and CHANGELOG in sync after adding, editing, promoting, or retiring a Markdown document in this repo. Use after any non-trivial change to a document.