fix(agents): remove self-referencing example blocks that cause recursive self-invocation (#496)

Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Trevin Chow
2026-04-03 01:40:34 -07:00
committed by GitHub
parent 6dcb4a3c55
commit 2c90aebe3b
24 changed files with 0 additions and 447 deletions

View File

@@ -4,33 +4,6 @@ description: "Conducts thorough research on repository structure, documentation,
model: inherit
---
<examples>
<example>
Context: User wants to understand a new repository's structure and conventions before contributing.
user: "I need to understand how this project is organized and what patterns they use"
assistant: "I'll use the repo-research-analyst agent to conduct a thorough analysis of the repository structure and patterns."
<commentary>Since the user needs comprehensive repository research, use the repo-research-analyst agent to examine all aspects of the project. No scope is specified, so the agent runs all phases.</commentary>
</example>
<example>
Context: User is preparing to create a GitHub issue and wants to follow project conventions.
user: "Before I create this issue, can you check what format and labels this project uses?"
assistant: "Let me use the repo-research-analyst agent to examine the repository's issue patterns and guidelines."
<commentary>The user needs to understand issue formatting conventions, so use the repo-research-analyst agent to analyze existing issues and templates.</commentary>
</example>
<example>
Context: User is implementing a new feature and wants to follow existing patterns.
user: "I want to add a new service object - what patterns does this codebase use?"
assistant: "I'll use the repo-research-analyst agent to search for existing implementation patterns in the codebase."
<commentary>Since the user needs to understand implementation patterns, use the repo-research-analyst agent to search and analyze the codebase.</commentary>
</example>
<example>
Context: A planning skill needs technology context and architecture patterns but not issue conventions or templates.
user: "Scope: technology, architecture, patterns. We are building a new background job processor for the billing service."
assistant: "I'll run a scoped analysis covering technology detection, architecture, and implementation patterns for the billing service."
<commentary>The consumer specified a scope, so the agent skips issue conventions, documentation review, and template discovery -- running only the requested phases.</commentary>
</example>
</examples>
**Note: The current year is 2026.** Use this when searching for recent documentation and patterns.
You are an expert repository research analyst specializing in understanding codebases, documentation structures, and project conventions. Your mission is to conduct thorough, systematic research to uncover patterns, guidelines, and best practices within repositories.