update-docs

Use when code, config, prompt, schema, or task changes require updating Markdown files directly under docs/, such as architecture, structure, config-sync…

Skill by transparent-pegasus

IndexedMIT★ 12

Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/transparent-pegasus-update-docs

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

About

Use when code, config, prompt, schema, or task changes require updating Markdown files directly under docs/, such as architecture, structure, config-sync, theories, adopted-theories, or todo documents.

Use cases: documents, productivity, agent-building

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools: No tools found
Secrets: None asked for
Install scripts: None found

Network hosts it talks to 1

codeload.github.com · found in install command

Files it touches

~/.claude/skills/update-docs

What's inside

Skill name: update-docs
Description: Use when code, config, prompt, schema, or task changes require updating Markdown files directly under docs/, such as architecture, structure, config-sync, theories, adopted-theories, or todo documents.
License: MIT
Instructions: 25 lines in SKILL.md · view on GitHub

Files (2)

ROOT_DOCS.md
SKILL.md

SKILL.md (first lines)

# Update Docs

## Overview

Keep root-level Markdown docs under `docs/` aligned with the current codebase and config.

Use `ROOT_DOCS.md` in this directory as the contract for what each root doc should contain.

## Scope

- Edit only files matching `docs/*.md`
- Do not edit files inside `docs/*/`
- Leave generated or output directories alone, including planning directories, generated content directories, and other paths explicitly marked as outputs by the initialized repository.

## Workflow

1. Identify which root docs are affected by the change.
2. Check `ROOT_DOCS.md` to confirm each affected doc's role and boundaries.
3. Check the current source of truth in code, config, prompts, schemas, or git history.
4. Update only the sections that changed.
5. Keep terminology, tone, and structure consistent with the existing file.
6. Keep diffs minimal. Prefer surgical edits over rewrites.
7. If a doc conflicts with the source of truth, fix the doc.

From transparent-pegasus/herdrpowers, MIT.

Signals

Stars: 12
Forks: 0
Open issues: 1
Last commit (this folder): Jul 25, 2026 (3 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License: MIT
Repository: github.com/transparent-pegasus/herdrpowers
First seen: Oct 24, 2026
Last checked: Oct 24, 2026
Source: GitHub github-graphql

More from transparent-pegasus

Cite this page

update-docs skill. Agent Mart. https://agentmart.dev/skills/transparent-pegasus-update-docs (last updated 2026-10-24)