skill-updater

Detects durable coding rules from agent work and updates SKILL.md and documentation files.

Updated Feb 25, 2026
One-click install
npx skills add https://github.com/werlang/event-hub --skill skill-updater-werlang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: skill-updater
Source: https://github.com/werlang/event-hub/tree/main/.agents/skills/skill-updater
Command: npx skills add https://github.com/werlang/event-hub --skill skill-updater-werlang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Recurring implementation patterns and durable coding decisions often get lost after a task completes, forcing future work to rediscover the same rules. This Skill captures those lessons and writes them into the correct repository documentation so future agent and human work inherits them by default. ## Core Features & Use Cases - Durable Rule Detection: Auto-invokes on trigger phrases like "update docs", "create new skill", or "document recurring pattern", and when agent output reveals reusable patterns across multiple files. - Ownership-Based Updates: Routes each rule to the narrowest correct guide, such as api-development, web-frontend, css-standards, or .github/copilot-instructions.md, preferring updates over new skills. - Documentation Audits: Reconciles stale README, prompt, and skill content against current routes, scripts, and tests. - Use Case: After refactoring event moderation logic into a reusable service pattern, invoke this Skill to record the new architectural boundary in the appropriate SKILL.md so future tasks follow it automatically. ## Quick Start Ask the agent to update the skill documentation to capture the reusable workflow or convention established in the current task.

Frequently Asked Questions about skill-updater

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

FAQPage Schema
How do I document a recurring coding pattern in a repository?▼

Identify the durable rule, confirm it applies beyond the current diff, then update the narrowest existing skill guide that owns that domain. Only create a new SKILL.md when no existing guide is the right long-term owner.

When should I create a new skill versus update an existing one?▼

Prefer updating an existing skill whenever a clear owner exists, such as api-development for API routes or web-frontend for SSR patterns. Create a new skill only for cross-cutting workflows or uncovered domains with recurring decisions.

What triggers automatic invocation of the skill-updater?▼

Auto-invocation occurs when prompts contain exact phrases like "update docs", "create new skill", or "this should be a skill", or when agent output introduces reusable patterns across multiple files or modifies .github guidance.

What changes should not be documented as durable rules?▼

Avoid documenting one-off bug fixes, temporary workarounds, local variable renames, unverified assumptions, and task-specific decisions. Only record rules that will remain true and influence future work beyond the current diff.

How do I keep README and Copilot instructions in sync with the codebase?▼

Run a documentation audit that checks README.md, .github skills, and prompt files against current routes, pages, scripts, and tests. Update every location that repeats a stale claim, not just the first occurrence.