Agent skill

Doc Maintenance

Workflow for maintaining changelogs, READMEs, and documentation files.

MITAuto-check passedDevelopment

Install Doc Maintenance

skills CLI

$ npx skills add macalbert/envilder --skill doc-maintenance -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install macalbert/envilder doc-maintenance --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/macalbert/envilder.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/doc-maintenance .claude/skills/doc-maintenance && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "doc-maintenance" agent skill from https://github.com/macalbert/envilder/tree/main/.github/skills/doc-maintenance into .claude/skills/doc-maintenance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc-maintenance", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/macalbert/envilder/tree/main/.github/skills/doc-maintenance

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add macalbert/envilder --skill doc-maintenance -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install macalbert/envilder doc-maintenance --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/macalbert/envilder.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/doc-maintenance .agents/skills/doc-maintenance && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "doc-maintenance" agent skill from https://github.com/macalbert/envilder/tree/main/.github/skills/doc-maintenance into .agents/skills/doc-maintenance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc-maintenance", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add macalbert/envilder --skill doc-maintenance -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install macalbert/envilder doc-maintenance --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/macalbert/envilder.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/doc-maintenance .cursor/skills/doc-maintenance && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "doc-maintenance" agent skill from https://github.com/macalbert/envilder/tree/main/.github/skills/doc-maintenance into .cursor/skills/doc-maintenance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc-maintenance", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/macalbert/envilder.git --path .github/skills/doc-maintenance

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add macalbert/envilder --skill doc-maintenance -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install macalbert/envilder doc-maintenance --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/macalbert/envilder.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/doc-maintenance .gemini/skills/doc-maintenance && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "doc-maintenance" agent skill from https://github.com/macalbert/envilder/tree/main/.github/skills/doc-maintenance into .gemini/skills/doc-maintenance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc-maintenance", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install macalbert/envilder doc-maintenance

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add macalbert/envilder --skill doc-maintenance -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/macalbert/envilder.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/doc-maintenance .github/skills/doc-maintenance && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "doc-maintenance" agent skill from https://github.com/macalbert/envilder/tree/main/.github/skills/doc-maintenance into .github/skills/doc-maintenance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc-maintenance", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add macalbert/envilder --skill doc-maintenance -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install macalbert/envilder doc-maintenance --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/macalbert/envilder.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/doc-maintenance .opencode/skills/doc-maintenance && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "doc-maintenance" agent skill from https://github.com/macalbert/envilder/tree/main/.github/skills/doc-maintenance into .opencode/skills/doc-maintenance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc-maintenance", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: doc-maintenance
GitHub stars: 138
Token cost: ~904 tokens
SKILL.md length: 326 words
Files: 1
Skills in repo: 30
Repo updated: Oct 5, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Workflow for maintaining changelogs, READMEs, and documentation files.

Works in 6 steps: Identify what changed (feature / fix /… → Locate impacted documentation files → Update the smallest set of sections… → …
Adding changelog entries
SKILL.md covers When to Use, Scope, Changelog Format and Workflow, plus 3 more sections
Calls pnpm

What it does

Doc Maintenance is an agent skill from macalbert/envilder. Workflow for maintaining changelogs, READMEs, and documentation files. Use when adding changelog entries, updating docs after code changes, or synchronizing documentation with current behavior. Covers changelog categories, entry format, constraints, and validation.

Its SKILL.md is about 900 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Changelog and release notes and Technical documentation. The repository describes itself as: One secret mapping for local dev, CI/CD, and runtime. Envilder resolves cloud secrets from your own vaults without SaaS middlemen, duplicated config, or .env drift. The licence is MIT.

When your agent uses it

Adding changelog entries
Updating docs after code changes
Synchronizing documentation with current behavior

Example prompts

“/doc-maintenance”

Requirements

Node.js

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

Identify what changed (feature / fix / dependency / workflow / docs)
Locate impacted documentation files
Update the smallest set of sections needed for correctness
Cross-check consistency across related docs (use doc-sync skill
Validate: run pnpm lint to check formatting and consistency
Summarize: list updated files and what was synchronized

What it can do on your machine

Read from SKILL.md and the folder at commit b6a0327. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- pnpm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use pnpm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Doc Maintenance loads about 904 tokens when it runs. Until then it costs about 70 tokens; SKILL.md has 326 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~70
When it runs · the whole SKILL.md, loaded when a task matches: ~904

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from macalbert/envilder at commit b6a0327, republished under its MIT licence (© macalbert). 326 words, ~904 tokens.

Download SKILL.mdSave it as .claude/skills/doc-maintenance/SKILL.md (or your agent's skills folder).

name: doc-maintenance
description: Workflow for maintaining changelogs, READMEs, and documentation files. Use when adding changelog entries, updating docs after code changes, or synchronizing documentation with current behavior. Covers changelog categories, entry format, constraints, and validation.

Doc Maintenance

Active maintenance workflow for Envilder documentation: changelogs, READMEs, and docs/ files.

Distinction from doc-sync: This skill covers how to write and update documentation. The doc-sync skill covers how to detect drift across documentation surfaces.

When to Use

Adding a changelog entry after a feature, fix, or dependency update
Updating README or docs after code changes
Writing release notes
Verifying documentation accuracy after a change

Scope

Document type	Location
Changelogs (per-component)	`docs/changelogs/{cli,gha,sdk-dotnet,sdk-python,sdk-nodejs}.md`
Root README	`README.md`
CLI docs	`docs/pull-command.md`, `docs/push-command.md`
GHA docs	`docs/github-action.md`, `github-action/README.md`
SDK READMEs	`src/sdks/{runtime}/README.md`
Architecture docs	`docs/architecture/`
Security docs	`docs/SECURITY.md`

Changelog Format

Category	When to use
`Added`	New features or capabilities
`Changed`	Behavior changes to existing features
`Fixed`	Bug fixes
`Documentation`	Docs-only changes
`Dependencies`	Dependency updates
`Security`	Security-related changes

Entry format

Keep bullets concise and user-impact oriented
Start with action verb (Add, Fix, Update, Remove)
Reference issue/PR numbers when available
Group under the current release section or create a new one when requested

markdown

## [1.2.0]: 2026-05-01

### Added

- Add `--profile` flag for AWS named profile support (#45)

### Fixed

- Fix Azure Key Vault timeout on large secret batches (#52)

Workflow

Identify what changed (feature / fix / dependency / workflow / docs)
Locate impacted documentation files
Update the smallest set of sections needed for correctness
Cross-check consistency across related docs (use doc-sync skill for comprehensive audit)
Validate: run pnpm lint to check formatting and consistency
Summarize: list updated files and what was synchronized

Constraints

Never invent features: document only what exists in code
Verify claims against current source files before writing
Preserve existing structure and tone unless explicitly asked to refactor
Prefer documentation-only edits: don't modify source unless asked
Keep examples minimal and runnable: avoid hypothetical code
Don't modify ROADMAP.md without explicit request (it's strategic)

Validation

After documentation edits:

bash

# Check formatting and consistency
pnpm lint

# For website-related docs, verify build
cd src/website && pnpm build

Delegation

Trigger	Delegate to	Why
Website pages need updating	`website-design-system` + `website-i18n` skills	UI patterns and i18n workflow
Unsure if documented behavior matches code	Verify against source directly	Read the actual implementation
Cross-surface drift suspected	`doc-sync` skill	Systematic drift detection
SDK docs need updating after version bump	`sdk-release-checklist` skill	Full integration checklist

Files

Just SKILL.md in .github/skills/doc-maintenance of macalbert/envilder.

Open the folder on GitHubat commit b6a0327

Compare with similar skills

Doc Maintenance next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Doc Maintenance compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Doc Maintenance this skillmacalbert/envilder	138	—	~904	Automated safety check: Pass	MIT	3 days ago
Simple Englishmoeru-ai/airi	50k	2 repos	~4.6k	Automated safety check: Pass	MIT	today
Ccb GitHubSeemSeam/claude_codex_bridge	3.6k	—	~4.9k	Automated safety check: Pass	Custom licence	today
Golang Documentationunxed/f4	241	3 repos	~3.5k	Automated safety check: Pass	MIT	today
Simple Englishropensci/ckanr	104	3 repos	~2k	Automated safety check: Pass	MIT	16 days ago
Opik Documentation Patternscomet-ml/opik	22k	—	~1.3k	Automated safety check: Pass	Apache-2.0	today

Similar skills

Simple English
moeru-ai/airi
Write or rewrite technical text with the rules of ASD-STE100 Simplified Technical English so it is clear, unambiguous, and free of AI slop.
50k GitHub starsUsed in 2 repos~4.6k tokens
DevelopmentAuto-check passed
Ccb GitHub
SeemSeam/claude_codex_bridge
Maintain this CCB project's GitHub-facing release and npm publication surface.
3.6k GitHub stars~4.9k tokensUpdated today
DevelopmentAuto-check passed
Golang Documentation
unxed/f4
Comprehensive documentation guide for Golang projects, covering godoc comments, README, CONTRIBUTING, CHANGELOG, Go Playground, Example tests, API docs, and llms.txt.
241 GitHub starsUsed in 3 repos~3.5k tokens
DevelopmentAuto-check passed
Simple English
ropensci/ckanr
Write or rewrite text in plain, layman-readable English in the spirit of ASD-STE100 Simplified Technical English: short sentences, active voice, simple tenses, one word one meaning, condition before…
104 GitHub starsUsed in 3 repos~2k tokens
DevelopmentAuto-check passed
Opik Documentation Patterns
comet-ml/opik
Rules for writing PR descriptions, changelog entries and feature documentation in the Opik repository, including the exact headings that CI requires.
22k GitHub stars~1.3k tokensUpdated today
DevelopmentAuto-check passed
Release
jrswab/axe
Prepare code for release (version bumps, changelog, README updates) and create an annotated tag to trigger the GoReleaser workflow.
895 GitHub stars~1.4k tokensUpdated 2 days ago
DevelopmentAuto-check passed

Questions about Doc Maintenance

What does Doc Maintenance do?

Workflow for maintaining changelogs, READMEs, and documentation files. Doc Maintenance is an agent skill from macalbert/envilder. Workflow for maintaining changelogs, READMEs, and documentation files.

When should I use Doc Maintenance?

Doc Maintenance fits situations like: adding changelog entries; updating docs after code changes; synchronizing documentation with current behavior.

How do I install Doc Maintenance in Claude Code?

Run `npx skills add macalbert/envilder --skill doc-maintenance -a claude-code`. Or copy the skill folder (.github/skills/doc-maintenance in macalbert/envilder) into .claude/skills/doc-maintenance in your project. Claude Code loads it when a task matches its description.

How do I install Doc Maintenance in Codex?

Run `npx skills add macalbert/envilder --skill doc-maintenance -a codex`. Or copy the skill folder (.github/skills/doc-maintenance in macalbert/envilder) into .agents/skills/doc-maintenance in your project. Codex loads it when a task matches its description.

Can I use Doc Maintenance in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add macalbert/envilder --skill doc-maintenance -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/doc-maintenance, .gemini/skills/doc-maintenance, .github/skills/doc-maintenance and .opencode/skills/doc-maintenance in your project.

What does Doc Maintenance need to run?

Going by SKILL.md and its folder, Doc Maintenance needs the command-line tools its instructions call (pnpm). Our summary lists: Node.js.

Does Doc Maintenance access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Doc Maintenance safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Doc Maintenance use?

Doc Maintenance is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Doc Maintenance use?

About 904 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Doc Maintenance?

Skills that share tags, products or a category with Doc Maintenance: Simple English (moeru-ai/airi, 50k stars), Ccb GitHub (SeemSeam/claude_codex_bridge, 3.6k stars), Golang Documentation (unxed/f4, 241 stars) and Simple English (ropensci/ckanr, 104 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Doc Maintenance?

macalbert (a GitHub user) maintains it in macalbert/envilder, which has 138 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on October 5, 2026.

Source: macalbert/envilder on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Doc Maintenance

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Doc Maintenance

When to Use

Scope

Changelog Format

Categories

Entry format

Workflow

Constraints

Validation

Delegation

Files

Compare with similar skills

Similar skills

More from macalbert/envilder

Related

Questions about Doc Maintenance