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

doc-sync

スター5

フォーク3

更新日2026年5月18日 12:15

Apply when verifying that comments and docs match the current code state. Used by the `tech-writer` agent. Encodes the project's WHY-only comment rule and the doc surfaces that must stay in sync (CLAUDE.md, README.md, config.example.{json,yaml}).

インストール

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

Manusで実行

ソース

greeddj

greeddj/imapsync-go

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

ダウンロード

Manusで実行

Doc sync

Read .claude/rules/docs.md first.

What stays in sync with code

Doc surface	Source of truth for its content
CLAUDE.md "Common commands"	`Justfile` (`just --list`)
CLAUDE.md "Architecture" sections 1–5	`internal/` layout and behaviour
CLAUDE.md "Conventions"	`internal/config/config.go`, CLI flag definitions, vendored state
README.md install/run	binary name, Justfile targets
README.md examples	actual CLI flags and config examples
`config.example.json`	every field in `internal/config/config.go`, populated with realistic values
`config.example.yaml`	same fields and same values as the JSON, just YAML-formatted

Comment audit one-liner

For changed Go files:

git diff main -- '*.go' | grep -E '^\+\s*//'

For each match, apply the checklist in .claude/rules/docs.md "Comment audit checklist".

CLI surface check

go run ./cmd/imapsync-go --help
go run ./cmd/imapsync-go sync --help
go run ./cmd/imapsync-go show --help

Compare against README.md and CLAUDE.md mentions. If a flag is documented but missing from --help, docs are stale.

Config surface check

grep -E '^\s*[A-Z][a-zA-Z]*\s+' internal/config/config.go | grep 'json:\|yaml:'

Every field tagged here must appear in both example files.

When the two example configs disagree

They must have the same set of fields and equivalent values. If they don't, fix the one that drifted — usually you can infer which is current by checking the most recent commit that touched internal/config/config.go.

When code and docs disagree and you can't tell which is right

Do not silently pick a winner. Report to architect with:

Where docs say X (file:line).
Where code now does Y (file:line).
Which one is consistent with the rest of the system, in your best judgement.
Your recommendation, but flagged as recommendation, not action.

このリポジトリの他の Skills

同じリポジトリ

coverage-audit

greeddj/imapsync-go

Apply when auditing test coverage on changed packages. Used by the `tester` agent. Encodes the project's stance: branch and invariant coverage matter more than total %, deliberate exclusions must be recorded with reasoning.

2026-05-185

idiomatic-go-review

greeddj/imapsync-go

Apply when reviewing Go code in this repo for idiom, allocation cost, struct layout, error wrapping, concurrency safety. Triggered by review-style requests on `.go` files, by the `architect` agent when forming verdicts, and by the `developer` agent self-checking before reporting. Loads the project's Go-style rule set.

2026-05-185

imap-sync-correctness

greeddj/imapsync-go

Apply when reviewing or writing code that touches the IMAP sync flow — anything in internal/client, internal/app/sync.go, internal/app/worker.go, internal/app/show.go. Encodes the non-obvious correctness traps specific to IMAP and to this tool's plan-confirm-execute model.

2026-05-185

security-audit

greeddj/imapsync-go

Apply when auditing changes for security in this repo. Used by the `security` agent. Encodes the threat model (operator trusted, IMAP servers + network partially trusted, no listening sockets) and the standing checklist.

2026-05-185

Doc sync

What stays in sync with code

Doc surface

Source of truth for its content

CLAUDE.md "Common commands"

Justfile (just --list)

CLAUDE.md "Architecture" sections 1–5

internal/ layout and behaviour

CLAUDE.md "Conventions"

internal/config/config.go, CLI flag definitions, vendored state

README.md install/run

binary name, Justfile targets

README.md examples

actual CLI flags and config examples

config.example.json

every field in internal/config/config.go, populated with realistic values

config.example.yaml

same fields and same values as the JSON, just YAML-formatted

Comment audit one-liner

For changed Go files:

git diff main -- '*.go' | grep -E '^\+\s*//'

For each match, apply the checklist in .claude/rules/docs.md "Comment audit checklist".

CLI surface check

go run ./cmd/imapsync-go --help go run ./cmd/imapsync-go sync --help go run ./cmd/imapsync-go show --help

Compare against README.md and CLAUDE.md mentions. If a flag is documented but missing from --help, docs are stale.

Config surface check

grep -E '^\s*[A-Z][a-zA-Z]*\s+' internal/config/config.go | grep 'json:\|yaml:'

Every field tagged here must appear in both example files.

When the two example configs disagree

When code and docs disagree and you can't tell which is right

Do not silently pick a winner. Report to architect with:

Where docs say X (file:line).

Where code now does Y (file:line).

Which one is consistent with the rest of the system, in your best judgement.

Your recommendation, but flagged as recommendation, not action.

name	doc-sync
description	Apply when verifying that comments and docs match the current code state. Used by the `tech-writer` agent. Encodes the project's WHY-only comment rule and the doc surfaces that must stay in sync (CLAUDE.md, README.md, config.example.{json,yaml}).