What problem does it solve? When the weegloo-server API changes (endpoints, MCP tools, error codes, script statement types), the agent-facing skills and rules in this repository silently drift out of date. Manually tracking what changed across a git range and deciding which documentation files to update is error-prone and tedious. ## Core Features & Use Cases - Mechanical change detection: Diffs operationIds, MCP tool groups, error codes, and schema-internal enums (e.g., Script statement types) between two git refs of the server repo, with dynamic module discovery instead of hardcoded paths. - Deployment gating: Cross-checks detected changes against dev-stack Swagger URLs per plane so only actually deployed features get documented, with MCP exposure triage for hidden [-Tag] tools. - Approval-gated editing: Produces a structured impact report (detected changes, affected files with rationale, items needing human judgment) and edits skill/rule files only after explicit approval. - Use Case: After a server release, run the skill with the server repo path, a git range, and Swagger URLs to get a reviewed list of exactly which skill and rule files need updating and why. ## Quick Start Ask the agent to sync the latest weegloo-server spec changes into the plugin skills, providing the server repo path, the base and head git refs, and the dev Swagger URLs.
