원클릭으로
find-docs
Find relevant documentation and output GitHub URLs
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Find relevant documentation and output GitHub URLs
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
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.
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).
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.
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.
Use when staging, formatting, or creating git commits for code changes in a Git repository.
Analyzes error logs, stack traces, and provides systematic debugging strategies and solutions
| name | find-docs |
| description | Find relevant documentation and output GitHub URLs |
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.
question tool for EVERY user interaction — never ask questions as plain textIdentify Repository Details:
git or gh to get the remote URL of the repository.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.main for this purpose, as it is the most common.Search for Documentation:
.md, .mdx) that seem directly related to the user's question.docs/ directory exists, read the content of all files within the docs/ directory to find relevant information.Construct and Output URLs:
{BASE_GITHUB_URL}/blob/{BRANCH_NAME}/{PATH_TO_FILE_FROM_REPO_ROOT}.question tool with structured options to ask clarifying questions about what they need. Do not return any URLs in this case.