{"id":77024,"plugin_id":"plugins_6ab41ed5b8c4819199eb5bbf91ce25f5","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-03T00:12:19.328Z","digest":"3d828a7e08e65dbddb489ce7cd13abf1d383e246d80065788d0a0fc8950ad938","against":null,"payload":{"description":"Explain an existing repository, trace code paths, map contracts and dependencies before proposing changes.","included_files":[],"name":"understand-repository","skill_md_contents":"---\nname: understand-repository\ndescription: Explain an existing repository, trace code paths, map contracts and dependencies before proposing changes.\n---\n\n# Understand Repository\n\nUse this skill only for its stated purpose. Follow the shared source-of-truth, permission and evidence rules in `../../references/workflow-contract.md`. Read `../../references/repository-discovery.md` for detailed method when necessary.\n\n## Procedure\n1. Read scoped repository rules, manifest and just enough entrypoints/source/tests for the user question.\n2. Trace one representative path across handlers/services/persistence or client/integration boundaries; identify public contracts and invariants.\n3. Mark facts by observed file paths and known versions. Separate uncertain assumptions from direct observations.\n4. Summarize the structure and likely change points; do not refactor unless asked.\nDeliver a focused codebase map, flow diagram in text when useful, contract inventory and questions only for true blockers.\n\n## Handoff rule\nState actual artifacts or grounded code findings and validation status. Never invent file paths, executed tests, tool access, or completed subagent work. Keep output proportionate to the user request.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}