repo-knowledge-lookup

knowledgeca がプロジェクト内一次情報と外部公式ドキュメントに当たって回答する手順。

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 2, 2026⬇️1downloads

When & Why to Use This Skill

The repo-knowledge-lookup skill is designed to provide evidence-based answers by systematically searching through internal project documentation and external official sources. It prioritizes primary information such as implementation plans, ADRs, and source code to eliminate guesswork and ensure technical accuracy. By following a structured retrieval process, it helps development teams maintain consistency and reduce rework caused by misinformation.

Use Cases

  • Technical Onboarding: Helping new developers quickly grasp project architecture and implementation details by querying internal docs and READMEs.
  • Architecture Alignment: Verifying if current code implementations align with documented Architecture Decision Records (ADRs) and design notes.
  • API Reference Integration: Cross-referencing internal logic with external official documentation like Microsoft Learn or library-specific APIs to ensure correct implementation.
  • Root Cause Analysis: Tracing the rationale behind specific code structures by retrieving historical context from task logs and review notes.
namerepo-knowledge-lookup
description|

目的

「推測」ではなく「根拠」に基づく回答を短く返し、作業の手戻りを減らす。

プロジェクト内の当たり方(順序)

  1. docs/<work_item>/implementedplan.md / tasks.md / review.md / notes.md
  2. README / docs/index / docs/architecture / ADR(存在する場合)
  3. 該当コード(呼び出し元→定義の順で追う)

外部の当たり方(MCPが利用可能な場合)

  • Microsoft系: Microsoft Learn MCP を優先
  • ライブラリAPI: Context7
  • 公開リポ構造: DeepWiki

回答フォーマット(必須)

  1. 結論(1行)
  2. 根拠(プロジェクト内ファイル/外部公式)
  3. 注意点(不確実なら不確実)
  4. oca判断が必要か(Yes/No)