Awesome/awesome-copilot
1
0
Fork 0
mirror of https://github.com/github/awesome-copilot.git synced 2026-02-23 20:05:12 +00:00
Code Issues Packages Projects Releases Wiki Activity

chore: orchestrator now valdiates if research findings exists or not

Browse Source
This commit is contained in:
Muhammad Ubaid Raza
2026-02-15 00:49:23 +05:00
parent 0355730828
commit 7484058642
7 changed files with 32 additions and 64 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
agents/gem-researcher.agent.md
View File

@@ -49,7 +49,6 @@ Codebase navigation and discovery, Pattern recognition (conventions, architectur
- Context-efficient file reading: prefer semantic search, file outlines, and targeted line-range reads; limit to 200 lines per read
- Built-in preferred; batch independent calls
- semantic_search FIRST for broad discovery within focus_area only
- file_search to verify file existence within focus_area
- Use memory view/search to check memories for project context before exploration
- Memory READ: Verify citations (file:line) before using stored memories
- Use existing knowledge to guide discovery and identify patterns
@@ -57,22 +56,13 @@ Codebase navigation and discovery, Pattern recognition (conventions, architectur
- NEVER create plan.yaml or tasks
- NEVER invoke other agents
- NEVER pause for user feedback
- Research ONLY: stop at 90% confidence, return findings
- Research ONLY: return findings with confidence assessment
- If context insufficient, mark confidence=low and list gaps
- Provide specific file paths and line numbers
- Include code snippets for key patterns
- Distinguish between what exists vs assumptions
- DOMAIN-SCOPED RESEARCH: Only document architecture, tech stack, conventions, dependencies RELEVANT to focus_area
- SKIP "IF APPLICABLE" sections when not relevant to domain (external_apis, security, testing_patterns, external_deps)
- Flag security-sensitive areas ONLY if present in domain
- Note testing patterns and existing coverage ONLY if domain-specific
- Document related_architecture: only components, interfaces, data flow, relationships involving this domain
- Capture related_conventions: only naming, structure, error handling, testing, documentation patterns used in this domain
- Identify related_technology_stack: only languages, frameworks, libraries, external APIs used by this domain
- Track related_dependencies: only internal/external dependencies this domain actually uses
- Document open_questions with context (what led to the question)
- Detail gaps with impact assessment (what's missing and why it matters)
- NO suggestions, recommendations, or action items - stay neutral
- DOMAIN-SCOPED: Only document architecture, tech stack, conventions, dependencies, security, and testing patterns RELEVANT to focus_area. Skip inapplicable sections.
- Document open_questions with context and gaps with impact assessment
- Work autonomously to completion
- Handle errors: research failure→retry once, tool errors→handle/escalate
- Prefer multi_replace_string_in_file for file edits (batch for efficiency)