grimoire-improve

Installation
SKILL.md

Improve ownership, dependency direction, and how directly a reader can explain behavior—not merely file size.

Under orchestration, the caller's execution contract takes precedence over this skill's standalone defaults.

Scope and discovery

Default to audit mode. Implement only when authorized; comprehensive implementation already authorizes in-scope internal restructuring without per-finding approval. Preserve observable behavior and public contracts. Ask for material scope expansion, contract changes, or irreversible actions.

When no scope is specified, start discovery with recent Git change hotspots; otherwise keep history analysis within the requested scope. Combine user-reported pain points with scoped Git history before deep inspection: look for repeated edits, fixes, and modules changed together over a stated revision/time window. Inspect representative diffs; discount generated, formatting-only, and bulk-migration churn. Use hotspots to order investigation, not as proof of defects or a substitute for requested coverage. If history is absent or shallow, state the limitation and prioritize user pain and source-level coupling.

Read hotspot code and relevant callers, configuration, state ownership, and tests, then expand through affected dependencies and remaining requested scope. Record scope, source revision/dirty state, contracts, and baseline checks when implementing. Optional map data accelerates navigation, not proof; verify source claims.

Own structural findings, recommendations, and analysis coverage; map owns reusable source evidence and navigation. For broad work, account for every in-scope first-party module, but reference the map inventory and source relationships rather than copying them into an improvement ledger. Search hits are not inspection; expose unread, excluded, and blocked regions.

For structured handoffs or resumable persistence, read the shared coordination contract v1. Publish owner analysis and check records; refactor references them rather than taking ownership. Standalone work may supply source evidence inline in the same format without requiring another skill. Small tasks need no ledger; persistence remains permission-gated.

Use dimensions.md to examine within- and cross-module relationships. Capture root cause, affected contract, impact, confidence, cost, and consumers with source evidence; use the shared finding shape when exchanging records. Names, size, or implementation counts alone are not findings.

Design and execution

Installs
15
GitHub Stars
3
First Seen
Jul 27, 2026