skills.rest
AndersonsRepo
AndersonsRepoCOMMUNITY
Explore all skills by this author →
GitHub

doc-on-success

Automates updating README, ARCHITECTURE and CONTEXT files after confirmed success.

Updated Aug 23, 2026
Search Tags:#automation#developer tools#documentation#knowledge management#code changes#context.md
One-click install
npx skills add https://github.com/AndersonsRepo/AI-Harness --skill doc-on-success
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: doc-on-success
Source: https://github.com/AndersonsRepo/AI-Harness/tree/main/.claude/skills/doc-on-success
Command: npx skills add https://github.com/AndersonsRepo/AI-Harness --skill doc-on-success

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the crucial but often overlooked task of updating project documentation after code changes are confirmed to be successful, ensuring that documentation remains accurate and up-to-date.

Core Features & Use Cases

  • Post-Implementation Documentation: Automatically updates README.md, ARCHITECTURE.md, and CONTEXT.md after a feature or bug fix is verified.
  • User Confirmation Loop: Ensures documentation is only updated after explicit or implicit user confirmation of success.
  • Use Case: After a developer implements a new feature and the user confirms it works, this skill will automatically update the project's README and architecture diagrams to reflect the change.

Quick Start

Use the doc-on-success skill to update project documentation after a successful code deployment.

Frequently Asked Questions about doc-on-success

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically update README and architecture documentation after code changes?▼

Automate project documentation updates by confirming successful feature implementation or bug resolution, categorizing the change, and updating markdown files like README.md and ARCHITECTURE.md. This ensures documentation remains accurate and up-to-date after code changes.

What is the best way to maintain AI-optimized documentation for code changes?▼

Maintain AI-optimized documentation by automatically updating CONTEXT.md with specific formatting rules after successful code deployment. This approach ensures documentation remains accurate and up-to-date for AI processing and knowledge management.

How does a user confirmation loop work for post-implementation documentation?▼

A user confirmation loop ensures documentation is only updated after explicit or implicit user confirmation of a successful feature implementation or bug fix, preventing inaccurate updates from failed code changes.

Can I update ARCHITECTURE.md and CONTEXT.md automatically after a bug fix?▼

Yes, you can automatically update ARCHITECTURE.md and CONTEXT.md after a bug fix. The process confirms the resolution with the user, categorizes the change, and applies the updates to the relevant project markdown files.

When should I trigger automated documentation updates for developer tools?▼

Trigger automated documentation updates immediately after a user confirms a successful code deployment or feature implementation. This prevents documentation drift by ensuring markdown files are updated only when code changes are verified.

Related Skills

Explore More Software Engineering Skills→
uuau99999uuau99999

git-commit

Generate Chinese conventional commit messages from current git status.

Community
Basic
t6adevt6adev
3

doc-sync

Detect documentation drift from git history and propose edits to project docs.

Community
Intermediate
trevorfoxtrevorfox
18

spandrel-builder

Provide expert heuristics for building and evolving the Spandrel framework.

Community
Advanced
VektaVekta
2

generate-doc

Generate and update CLAUDE.md, CONTEXT.md, and scoped rules from project analysis.

Official
Advanced