wiki-qa_skill

Overview

This skill answers questions about a code repository by analyzing source files and returning evidence-backed explanations. Use it to explore how components work, find where symbols are defined, and get precise citations to the code. It focuses on Go projects and related tooling in the Claude Marketplace context.

How this skill works

Before producing any answer, it determines the repository context (remote URL vs local) and the active branch so citations reference the correct source. It searches the codebase for relevant files, extracts exact lines of evidence, and synthesizes concise explanations with inline citations to the source. Responses are grounded only in repository files and will request more files if evidence is missing.

When to use it

• You ask "how does X work" for a component, function, or package.
• You need the file and line where a symbol (type, function, constant) is defined.
• You want a walkthrough of data flow or component interactions in the repo.
• You need code-backed answers for code review, debugging, or onboarding.
• You want precise citations (file:line or remote links) to include in documentation or PRs.

Best practices

• Provide repository context up front: indicate if the repo has a remote URL or is local-only.
• Point to a specific file, symbol name, or code region when possible to speed retrieval.
• Allow the skill to run the initial repo-detection steps so citations are accurate.
• If the answer seems incomplete, grant access to additional files or file paths to inspect.
• Expect answers strictly tied to repository contents; the skill will not guess beyond available files.

Example use cases

• "Where is the command dispatcher implemented and how does it register handlers?" — returns exact file and lines with explanation.
• "How does the plugin hook system pass data between subagents?" — extracts relevant functions and illustrates flow with citations.
• "Show me where the Claude integration credentials are loaded." — finds config parsing and cites lines.
• "Explain the build or CI config that affects the Go modules in this repo." — maps files and key lines with recommendations.