Your task is to find documentation files relevant to the user's question within the current git repository and provide a list of GitHub URLs to view them.

CRITICAL FORMAT REQUIREMENTS:

MUST use the question tool for EVERY user interaction — never ask questions as plain text

Workflow:

Identify Repository Details:
- You may use shell commands like git or gh to get the remote URL of the repository.
- From the remote URL, parse and construct the base GitHub URL (e.g., https://github.com/user/repo). You must handle both HTTPS (https://github.com/user/repo.git) and SSH (git@github.com:user/repo.git) formats.
- Determine the default branch name. You can assume main for this purpose, as it is the most common.
Search for Documentation:
- First, perform a targeted search across the repository for documentation files (e.g., .md, .mdx) that seem directly related to the user's question.
- If this initial search yields no relevant results, and a docs/ directory exists, read the content of all files within the docs/ directory to find relevant information.
- If you still can't find a direct match, broaden your search to include related concepts and synonyms of the keywords in the user's question.
- For each file you identify as potentially relevant, read its content to confirm it addresses the user's query.
Construct and Output URLs:
- For each file you identify as relevant, construct the full GitHub URL by combining the base URL, branch, and file path. Do not use shell commands for this step.
- The URL format should be: {BASE_GITHUB_URL}/blob/{BRANCH_NAME}/{PATH_TO_FILE_FROM_REPO_ROOT}.
- Present the final list to the user as a markdown list. Each item in the list should be the URL to the document, followed by a short summary of its content.
- If, after all search attempts, you cannot find any relevant documentation, use the question tool with structured options to ask clarifying questions about what they need. Do not return any URLs in this case.

Más de este repositorio

mismo repositorio

conventional-commit

lalitmee/dotfiles

Use when the user asks to commit, write a commit message, generate a conventional commit, or invokes /conventional-commit. Also use when staged changes need a commitlint-compliant message, when the user asks to commit and push (or passes --push), when unstaged or untracked files exist and staging scope must be confirmed, or when agent-attribution trailers must be avoided on commits. Handles git commit and git push flags when the user passes them.

2026-07-1742

grill-pr

lalitmee/dotfiles

Use when the user asks to create, open, or raise a GitHub pull request, submit changes for review. Also when staged, committed, or unpushed work needs a PR via gh CLI and required PR metadata is missing (base branch, draft vs ready, reviewers, labels, linked issues, test plan).

2026-07-1742

structured-reasoning

lalitmee/dotfiles

Use when the task is multi-constraint, ambiguous, architectural, or needs a design/algorithm choice before answering. Skip for trivial lookups and one-line edits.

2026-07-1742

verifying-solutions

lalitmee/dotfiles

Use when the user explicitly asks to audit, critic, or verify a generated solution or answer (e.g. /verifying-solutions, "audit this", "critic this") — not for routine completion claims or pre-answer design.

2026-07-1742

commit

lalitmee/dotfiles

Use when staging, formatting, or creating git commits for code changes in a Git repository.

2026-07-0342

debug

lalitmee/dotfiles

Analyzes error logs, stack traces, and provides systematic debugging strategies and solutions

2026-07-0342

name	find-docs
description	Find relevant documentation and output GitHub URLs

Mission: Find Relevant Documentation

Your task is to find documentation files relevant to the user's question within the current git repository and provide a list of GitHub URLs to view them.

CRITICAL FORMAT REQUIREMENTS:

MUST use the question tool for EVERY user interaction — never ask questions as plain text

Workflow:

Identify Repository Details:
- You may use shell commands like git or gh to get the remote URL of the repository.
- From the remote URL, parse and construct the base GitHub URL (e.g., https://github.com/user/repo). You must handle both HTTPS (https://github.com/user/repo.git) and SSH (git@github.com:user/repo.git) formats.
- Determine the default branch name. You can assume main for this purpose, as it is the most common.
Search for Documentation:
- First, perform a targeted search across the repository for documentation files (e.g., .md, .mdx) that seem directly related to the user's question.
- If this initial search yields no relevant results, and a docs/ directory exists, read the content of all files within the docs/ directory to find relevant information.
- If you still can't find a direct match, broaden your search to include related concepts and synonyms of the keywords in the user's question.
- For each file you identify as potentially relevant, read its content to confirm it addresses the user's query.
Construct and Output URLs:
- For each file you identify as relevant, construct the full GitHub URL by combining the base URL, branch, and file path. Do not use shell commands for this step.
- The URL format should be: {BASE_GITHUB_URL}/blob/{BRANCH_NAME}/{PATH_TO_FILE_FROM_REPO_ROOT}.
- Present the final list to the user as a markdown list. Each item in the list should be the URL to the document, followed by a short summary of its content.
- If, after all search attempts, you cannot find any relevant documentation, use the question tool with structured options to ask clarifying questions about what they need. Do not return any URLs in this case.