skills.rest
ai-pivot
ai-pivotOFFICIAL
Explore all skills by this author →
GitHub

post-dev

Update AGENTS.md and docs/agent/ files after code changes.

12|5|Updated Apr 26, 2026
Search Tags:#git workflow#knowledge management#docs maintenance#documentation accuracy#agent index#code change hygiene
One-click install
npx skills add https://github.com/ai-pivot/xbot --skill post-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: post-dev
Source: https://github.com/ai-pivot/xbot/tree/main/tools/embed_skills/post-dev
Command: npx skills add https://github.com/ai-pivot/xbot --skill post-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures your AI Agent’s knowledge base stays consistent with the latest codebase by updating the AGENTS.md index and the corresponding docs/agent/ knowledge files after development changes.

Core Features & Use Cases

  • Prevents stale or broken knowledge references: Ensures every file referenced in AGENTS.md actually exists and removes references when files are deleted.
  • Maintains a living, self-contained knowledge base: Updates the real content in docs/agent/ files (not just the index), writing what future sessions need to know.
  • Supports continuous documentation hygiene: Activated before commits/pushes and after changes that add/remove files, alter architecture, or modify core behavior.

Quick Start

Ask the agent to run the post-dev cleanup after your latest code changes to update AGENTS.md and the docs/agent/ knowledge files.

Frequently Asked Questions about post-dev

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

FAQPage Schema
How do I update AGENTS.md and docs automatically after code changes?▼

Maintain documentation accuracy by running a post-dev cleanup to update your AGENTS.md index and docs/agent/ knowledge files. This prevents stale references by ensuring all referenced files exist and content reflects the latest architecture.

When should I update my agent knowledge base index during a git workflow?▼

Update your agent knowledge base index before committing or pushing code, specifically after development that adds or removes files, changes architecture, or modifies core behavior, ensuring your AGENTS.md index points to existing docs/agent/ topics.

How do I prevent stale or broken knowledge references in my documentation?▼

Prevent stale or broken knowledge references by enforcing read-before-write accuracy during documentation maintenance. This guarantees every file referenced in AGENTS.md actually exists and removes references when files are deleted.

What is the best way to maintain a living knowledge base for an AI agent?▼

Maintain a living knowledge base for an AI agent by keeping AGENTS.md as a concise index pointing to self-contained docs/agent/ topics. Update the real content in these files after development changes to inform future sessions.

Does post-dev cleanup work without external dependencies for docs maintenance?▼

Yes, post-dev cleanup operates without external dependencies to maintain documentation accuracy. It directly manages your AGENTS.md and docs/agent/ files to ensure code change hygiene and a consistent knowledge index.

Related Skills

Explore More Software Engineering Skills→
Desko77Desko77
40

1c-cf-edit

Edit 1C Configuration.xml properties and objects via cf-edit scripts.

Community
Advanced
tobihagemanntobihagemann
399

stage-commit-push

Stage all changes, commit with a user message, and push to the remote branch.

Community
Basic
ragnarokhaaragnarokhaa
4

requesting-code-review

Automate pre-commit code review with static security and quality scans.

Community
Advanced
emcconnellemcconnell

story-done

Verifies completed stories' acceptance criteria, design consistency, and prepares completion reports.

Community
Advanced