Run any Skill in Manus with one click

docs-sync-after-code-change

Stars0

Forks0

UpdatedApril 13, 2026 at 06:24

Synchronize documentation after code changes in this repository. Use when implementation changes affect commands, values precedence, template runtime behavior, project structure docs, or examples.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

atframework

atframework/atdtool

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	docs-sync-after-code-change
description	Synchronize documentation after code changes in this repository. Use when implementation changes affect commands, values precedence, template runtime behavior, project structure docs, or examples.

Docs sync after code change

Identify the user-visible behavior that changed before editing docs.
Update README.md as the entry point when commands, workflows, or doc links changed.
Update the narrowest matching doc pages under docs/usage/, docs/reference/, or docs/structure/.
Keep examples generic and consistent with current code and tests; do not rely on external sample repositories.
Prefer describing real behavior over aspirational behavior. When unsure, confirm from code or tests first.
If code and docs disagree, fix both in the same task or leave a clear follow-up note.
Check edited Markdown for diagnostics before finishing.

More from this repository

same repository

cli-command-change-checklist

atframework/atdtool

Review or implement user-visible CLI command changes in this repository. Use when changing subcommands, flags, help text, defaults, output paths, or command behavior.

2026-04-130

helm-values-precedence-review

atframework/atdtool

Review or change Helm/chart values precedence in this repository. Use when working on global.yaml, chart-name yaml, modules, runtime values, template overrides, or --set merge behavior.

2026-04-130

repo-implementation

atframework/atdtool

Implement or refactor production code in this Go repository. Use when adding features, fixing bugs, changing CLI behavior, or modifying files under cmd/, cli/, internal/, pkg/, or logarchive/.

2026-04-130

repo-testing

atframework/atdtool

Write, repair, or stabilize tests in this Go repository. Use when adding unit tests, reproducing bugs with tests, fixing failing or flaky tests, updating testdata, or improving coverage for changed behavior.

2026-04-130

name	docs-sync-after-code-change
description	Synchronize documentation after code changes in this repository. Use when implementation changes affect commands, values precedence, template runtime behavior, project structure docs, or examples.

Docs sync after code change

Identify the user-visible behavior that changed before editing docs.
Update README.md as the entry point when commands, workflows, or doc links changed.
Update the narrowest matching doc pages under docs/usage/, docs/reference/, or docs/structure/.
Keep examples generic and consistent with current code and tests; do not rely on external sample repositories.
Prefer describing real behavior over aspirational behavior. When unsure, confirm from code or tests first.
If code and docs disagree, fix both in the same task or leave a clear follow-up note.
Check edited Markdown for diagnostics before finishing.