How do I install the Wiki QA skill?

Run npx skillmds@latest add freightcognition/wiki-qa in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Wiki QA safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Wiki QA?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Wiki QA free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Wiki QA?

freightcognition (@freightcognition) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Wiki QA by freightcognition — Agent Skill

Name: Wiki QA
Author: freightcognition

Wiki QA

Answers questions about a code repository using source file analysis. Use when the user asks a question about how something works, wants to understand a component, or needs help navigating the codebase.

freightcognition 74aba51 2 files · 4.6 KB Updated Sep 17, 2026

File contents

Wiki Q&A

Answer repository questions grounded entirely in source code evidence.

When to Activate

User asks a question about the codebase
User wants to understand a specific file, function, or component
User asks "how does X work" or "where is Y defined"

Source Repository Resolution (MUST DO FIRST)

Before answering any question, you MUST determine the source repository context:

Check for git remote: Run git remote get-url origin to detect if a remote exists
Ask the user: "Is this a local-only repository, or do you have a source repository URL (e.g., GitHub, Azure DevOps)?"
- Remote URL provided → store as REPO_URL, use linked citations: [file:line](REPO_URL/blob/BRANCH/file#Lline)
- Local-only → use local citations: (file_path:line_number)
Determine default branch: Run git rev-parse --abbrev-ref HEAD
Do NOT proceed until source repo context is resolved

Procedure

Resolve source repo context (see above)
Detect the language of the question; respond in the same language
Search the codebase for relevant files
Read those files to gather evidence
Synthesize an answer with inline linked citations

Response Format

Use ## headings, code blocks with language tags, tables, bullet lists
Cite sources inline using resolved format:
- Remote: [src/path/file.ts:42](REPO_URL/blob/BRANCH/src/path/file.ts#L42)
- Local: (src/path/file.ts:42)
Include a "Key Files" table mapping files to their roles (with linked citations in the "File" column)
Include at least 1 Mermaid diagram when the answer involves architecture, data flow, or relationships — a diagram makes the answer 10x more useful
Use tables for any structured data in the answer (component lists, API endpoints, config options, comparisons)
If information is insufficient, say so and suggest files to examine

Rules

ONLY use information from actual source files
NEVER invent, guess, or use external knowledge
Think step by step before answering

---name: wiki-qadescription: Answers questions about a code repository using source file analysis. Use when the user asks a question about how something works, wants to understand a component, or needs help navigating the codebase.---# Wiki Q&AAnswer repository questions grounded entirely in source code evidence.## When to Activate- User asks a question about the codebase- User wants to understand a specific file, function, or component- User asks "how does X work" or "where is Y defined"## Source Repository Resolution (MUST DO FIRST)Before answering any question, you MUST determine the source repository context:1. **Check for git remote**: Run `git remote get-url origin` to detect if a remote exists2. **Ask the user**: _"Is this a local-only repository, or do you have a source repository URL (e.g., GitHub, Azure DevOps)?"_ - Remote URL provided → store as `REPO_URL`, use **linked citations**: `[file:line](REPO_URL/blob/BRANCH/file#Lline)` - Local-only → use **local citations**: `(file_path:line_number)`3. **Determine default branch**: Run `git rev-parse --abbrev-ref HEAD`4. **Do NOT proceed** until source repo context is resolved## Procedure1. Resolve source repo context (see above)2. Detect the language of the question; respond in the same language3. Search the codebase for relevant files4. Read those files to gather evidence5. Synthesize an answer with inline linked citations## Response Format- Use `##` headings, code blocks with language tags, tables, bullet lists- Cite sources inline using resolved format: - **Remote**: `[src/path/file.ts:42](REPO_URL/blob/BRANCH/src/path/file.ts#L42)` - **Local**: `(src/path/file.ts:42)`- Include a "Key Files" table mapping files to their roles (with linked citations in the "File" column)- **Include at least 1 Mermaid diagram** when the answer involves architecture, data flow, or relationships — a diagram makes the answer 10x more useful- **Use tables** for any structured data in the answer (component lists, API endpoints, config options, comparisons)- If information is insufficient, say so and suggest files to examine## Rules- ONLY use information from actual source files- NEVER invent, guess, or use external knowledge- Think step by step before answering

Frequently asked questions