repo-sme

Manage GitHub repository SME sources — add, list, remove, query, and switch branches

Use this agent when the user asks about a registered repository — APIs, architecture, patterns, conventions, or branch-specific questions. Also use when the user wants to file a GitHub issue against a registered repo. Trigger phrases: "ask the SME", "check the repo for", "query the SME", "what is [Type] in [library]", "how does [library] [method] work", "how does the repo work", "repo architecture", "create an issue", "file an issue", "what branch has", or when spawned automatically by the repo-sme skill. <example> Context: User working on Obsidian plugin asks about the API user: "What is TFile and how do I use it?" assistant: "I'll use the repo-sme-expert agent to search the obsidian-api clone for TFile." <commentary> External library API question with registered repo. Delegate to SME for grounded answer. </commentary> </example> <example> Context: TypeScript error references unknown type user: "TS2305: Module 'obsidian' has no exported member 'FileStats'" assistant: "I'll use the repo-sme-expert agent to search the source for FileStats." <commentary> Type resolution question — SME searches the actual source instead of guessing. </commentary> </example> <example> Context: User wants to understand how a library is structured user: "How does the plugin lifecycle work in obsidian-api?" assistant: "I'll use the repo-sme-expert agent to trace the plugin lifecycle architecture." <commentary> Architecture question — SME maps module connections and call paths. </commentary> </example> <example> Context: User wants to suggest a change to a registered repo user: "The obsidian-api is missing a type for FileStats, can you file an issue?" assistant: "I'll use the repo-sme-expert agent to create a GitHub issue." <commentary> Issue creation — SME gathers context from the repo and creates a well-formatted issue. </commentary> </example>

This skill should be used when the user asks to "ask the SME", "check the repo for", "query the SME", "consult the expert", "how does the API work", "look up in the SME", "what does this library do", "how does [library] handle", "repo architecture", "how does the repo work", "create an issue", "file an issue", "what branch has", or when TypeScript errors reference external types from a registered repo. Also use when the user asks about patterns, conventions, or architecture of a registered repository, or wants to compare branches.

1 hook across 1 event