Run any Skill in Manus with one click

documentation-refresh

Stars6

Forks0

UpdatedJuly 17, 2026 at 15:38

Use this skill when refreshing Weft public documentation, AGENTS.md, CLAUDE.md, or mirrored skills from recent pull requests.

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

stevekinney

stevekinney/weft

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	documentation-refresh
description	Use this skill when refreshing Weft public documentation, AGENTS.md, CLAUDE.md, or mirrored skills from recent pull requests.

Documentation Refresh

When to use

A task asks to review recent pull requests and update documentation.
Public documentation, agent guidance, and mirrored skills must stay aligned.
A documentation-only pull request needs evidence grounded in merged code or review feedback.

Workflow

Start from the requested pull request window. If an earlier documentation refresh already covered part of the window, treat that refresh as the lower bound instead of documenting the same behavior twice.
Gather evidence before editing: pull request titles, bodies, changed files, review comments, and verification commands. Prefer merged pull requests; do not document open pull request behavior as shipped.
Map behavior changes to the right surface. User-facing runtime behavior belongs in README.md or documentation/**; agent workflow lessons belong in AGENTS.md, CLAUDE.md, .agents/skills/**, and .claude/skills/**.
If the window contains only a documentation-refresh pull request, use it as the new lower bound. Do not invent a public-doc edit; state in the pull request evidence that no post-refresh runtime, API, or workflow behavior landed.
Keep each update anchored to exact contracts, commands, and file paths. Avoid generic advice that could apply to any repository.
Mirror skill changes between .agents/skills and .claude/skills when the same workflow applies to both agent surfaces.
In the pull request body, include an evidence section that names the source pull requests and the contracts or workflows documented.

Verification

Run the documentation gates that match the edited surfaces:

bun run format
bun run verify:documentation
bun run verify:markdown-doctests
bun run typecheck
bun run validate

Run bun run verify:jsdoc:doctests when public JSDoc examples change. Run bun run scripts/check-type-ergonomics.ts when type-shape documentation or declaration examples change.

More from this repository

same repository

coverage-harness-design

stevekinney/weft

Use this skill when restoring or protecting Weft coverage with LCOV-backed branch targeting, structural test doubles, coverage allowlists, conformance fixtures, or tests for hard-to-reach protocol, schema, lifecycle, and CLI paths.

2026-07-166

async-lifecycle-races

stevekinney/weft

Use this skill when a Weft change touches ack-gated flows, pending promises, WebSocket workers, shutdown, disposal, cancellation, retries, reconnects, heartbeats, timers, or any lifecycle path where ordering can leave work hanging.

2026-07-156

contract-truth-writing

stevekinney/weft

Use this skill when writing or reviewing Weft comments, JSDoc, documentation, README examples, test prose, or operation descriptions that describe wire responses, server diagnostics, masked errors, public APIs, or runtime recovery.

2026-07-156

semantic-compatibility

stevekinney/weft

Use this skill when a Weft change renames, reshapes, normalizes, hashes, serializes, or replays persisted data such as effect-log records, checkpoints, tool calls, tool results, JSONValue content, storage payloads, or compatibility fixtures.

2026-07-156

verification-loop

stevekinney/weft

Run the full verification cycle before declaring work done: build, typecheck, lint, test, export review, diff review. Use when the user says "verify", "validate", "check everything passes", "run the full suite", "make sure it's ready", or before committing, opening a PR, or finishing a feature. Also use proactively after completing any non-trivial implementation work.

2026-07-066

security-review

stevekinney/weft

Security review checklist for weft covering server routes, MCP authentication, workflow trust boundaries, storage, activity isolation, and credential handling. Use when the user says "security review", "check for vulnerabilities", "audit security", "review trust boundaries", or when changes touch server routes, authentication, storage, or any code that handles untrusted input. Also use proactively when implementing features that cross trust boundaries.

2026-06-296

Documentation Refresh

When to use

A task asks to review recent pull requests and update documentation.

Public documentation, agent guidance, and mirrored skills must stay aligned.

A documentation-only pull request needs evidence grounded in merged code or review feedback.

Workflow

Start from the requested pull request window. If an earlier documentation refresh already covered part of the window, treat that refresh as the lower bound instead of documenting the same behavior twice.

Gather evidence before editing: pull request titles, bodies, changed files, review comments, and verification commands. Prefer merged pull requests; do not document open pull request behavior as shipped.

Map behavior changes to the right surface. User-facing runtime behavior belongs in README.md or documentation/**; agent workflow lessons belong in AGENTS.md, CLAUDE.md, .agents/skills/**, and .claude/skills/**.

If the window contains only a documentation-refresh pull request, use it as the new lower bound. Do not invent a public-doc edit; state in the pull request evidence that no post-refresh runtime, API, or workflow behavior landed.

Keep each update anchored to exact contracts, commands, and file paths. Avoid generic advice that could apply to any repository.

Mirror skill changes between .agents/skills and .claude/skills when the same workflow applies to both agent surfaces.

In the pull request body, include an evidence section that names the source pull requests and the contracts or workflows documented.

Verification

Run the documentation gates that match the edited surfaces:

bun run format bun run verify:documentation bun run verify:markdown-doctests bun run typecheck bun run validate

Run bun run verify:jsdoc:doctests when public JSDoc examples change. Run bun run scripts/check-type-ergonomics.ts when type-shape documentation or declaration examples change.