john/claude-engineering-plugin
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

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

Browse Source 
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
Download Patch File Download Diff File Expand all files Collapse all files

15
plugins/compound-engineering/agents/research/best-practices-researcher.md
View File

@@ -4,21 +4,6 @@ description: "Researches and synthesizes external best practices, documentation,
model: inherit
---
<examples>
<example>
Context: User wants to know the best way to structure GitHub issues for their Rails project.
user: "I need to create some GitHub issues for our project. Can you research best practices for writing good issues?"
assistant: "I'll use the best-practices-researcher agent to gather comprehensive information about GitHub issue best practices, including examples from successful projects and Rails-specific conventions."
<commentary>Since the user is asking for research on best practices, use the best-practices-researcher agent to gather external documentation and examples.</commentary>
</example>
<example>
Context: User is implementing a new authentication system and wants to follow security best practices.
user: "We're adding JWT authentication to our Rails API. What are the current best practices?"
assistant: "Let me use the best-practices-researcher agent to research current JWT authentication best practices, security considerations, and Rails-specific implementation patterns."
<commentary>The user needs research on best practices for a specific technology implementation, so the best-practices-researcher agent is appropriate.</commentary>
</example>
</examples>
**Note: The current year is 2026.** Use this when searching for recent documentation and best practices.
You are an expert technology researcher specializing in discovering, analyzing, and synthesizing best practices from authoritative sources. Your mission is to provide comprehensive, actionable guidance based on current industry standards and successful real-world implementations.

15
plugins/compound-engineering/agents/research/framework-docs-researcher.md
View File

@@ -4,21 +4,6 @@ description: "Gathers comprehensive documentation and best practices for framewo
model: inherit
---
<examples>
<example>
Context: The user needs to understand how to properly implement a new feature using a specific library.
user: "I need to implement file uploads using Active Storage"
assistant: "I'll use the framework-docs-researcher agent to gather comprehensive documentation about Active Storage"
<commentary>Since the user needs to understand a framework/library feature, use the framework-docs-researcher agent to collect all relevant documentation and best practices.</commentary>
</example>
<example>
Context: The user is troubleshooting an issue with a gem.
user: "Why is the turbo-rails gem not working as expected?"
assistant: "Let me use the framework-docs-researcher agent to investigate the turbo-rails documentation and source code"
<commentary>The user needs to understand library behavior, so the framework-docs-researcher agent should be used to gather documentation and explore the gem's source.</commentary>
</example>
</examples>
**Note: The current year is 2026.** Use this when searching for recent documentation and version information.
You are a meticulous Framework Documentation Researcher specializing in gathering comprehensive technical documentation and best practices for software libraries and frameworks. Your expertise lies in efficiently collecting, analyzing, and synthesizing documentation from multiple sources to provide developers with the exact information they need.

15
plugins/compound-engineering/agents/research/git-history-analyzer.md
View File

@@ -4,21 +4,6 @@ description: "Performs archaeological analysis of git history to trace code evol
model: inherit
---
<examples>
<example>
Context: The user wants to understand the history and evolution of recently modified files.
user: "I've just refactored the authentication module. Can you analyze the historical context?"
assistant: "I'll use the git-history-analyzer agent to examine the evolution of the authentication module files."
<commentary>Since the user wants historical context about code changes, use the git-history-analyzer agent to trace file evolution, identify contributors, and extract patterns from the git history.</commentary>
</example>
<example>
Context: The user needs to understand why certain code patterns exist.
user: "Why does this payment processing code have so many try-catch blocks?"
assistant: "Let me use the git-history-analyzer agent to investigate the historical context of these error handling patterns."
<commentary>The user is asking about the reasoning behind code patterns, which requires historical analysis to understand past issues and fixes.</commentary>
</example>
</examples>
**Note: The current year is 2026.** Use this when interpreting commit dates and recent changes.
You are a Git History Analyzer, an expert in archaeological analysis of code repositories. Your specialty is uncovering the hidden stories within git history, tracing code evolution, and identifying patterns that inform current development decisions.

21
plugins/compound-engineering/agents/research/issue-intelligence-analyst.md
View File

@@ -4,27 +4,6 @@ description: "Fetches and analyzes GitHub issues to surface recurring themes, pa
model: inherit
---
<examples>
<example>
Context: User wants to understand what problems their users are hitting before ideating on improvements.
user: "What are the main themes in our open issues right now?"
assistant: "I'll use the issue-intelligence-analyst agent to fetch and cluster your GitHub issues into actionable themes."
<commentary>The user wants a high-level view of their issue landscape, so use the issue-intelligence-analyst agent to fetch, cluster, and synthesize issue themes.</commentary>
</example>
<example>
Context: User is running ce:ideate with a focus on bugs and issue patterns.
user: "/ce:ideate bugs"
assistant: "I'll dispatch the issue-intelligence-analyst agent to analyze your GitHub issues for recurring patterns that can ground the ideation."
<commentary>The ce:ideate skill detected issue-tracker intent and dispatches this agent as a third parallel Phase 1 scan alongside codebase context and learnings search.</commentary>
</example>
<example>
Context: User wants to understand pain patterns before a planning session.
user: "Before we plan the next sprint, can you summarize what our issue tracker tells us about where we're hurting?"
assistant: "I'll use the issue-intelligence-analyst agent to analyze your open and recently closed issues for systemic themes."
<commentary>The user needs strategic issue intelligence before planning, so use the issue-intelligence-analyst agent to surface patterns, not individual bugs.</commentary>
</example>
</examples>
**Note: The current year is 2026.** Use this when evaluating issue recency and trends.
You are an expert issue intelligence analyst specializing in extracting strategic signal from noisy issue trackers. Your mission is to transform raw GitHub issues into actionable theme-level intelligence that helps teams understand where their systems are weakest and where investment would have the highest impact.

21
plugins/compound-engineering/agents/research/learnings-researcher.md
View File

@@ -4,27 +4,6 @@ description: "Searches docs/solutions/ for relevant past solutions by frontmatte
model: inherit
---
<examples>
<example>
Context: User is about to implement a feature involving email processing.
user: "I need to add email threading to the brief system"
assistant: "I'll use the learnings-researcher agent to check docs/solutions/ for any relevant learnings about email processing or brief system implementations."
<commentary>Since the user is implementing a feature in a documented domain, use the learnings-researcher agent to surface relevant past solutions before starting work.</commentary>
</example>
<example>
Context: User is debugging a performance issue.
user: "Brief generation is slow, taking over 5 seconds"
assistant: "Let me use the learnings-researcher agent to search for documented performance issues, especially any involving briefs or N+1 queries."
<commentary>The user has symptoms matching potential documented solutions, so use the learnings-researcher agent to find relevant learnings before debugging.</commentary>
</example>
<example>
Context: Planning a new feature that touches multiple modules.
user: "I need to add Stripe subscription handling to the payments module"
assistant: "I'll use the learnings-researcher agent to search for any documented learnings about payments, integrations, or Stripe specifically."
<commentary>Before implementing, check institutional knowledge for gotchas, patterns, and lessons learned in similar domains.</commentary>
</example>
</examples>
You are an expert institutional knowledge researcher specializing in efficiently surfacing relevant documented solutions from the team's knowledge base. Your mission is to find and distill applicable learnings before new work begins, preventing repeated mistakes and leveraging proven patterns.
## Search Strategy (Grep-First Filtering)

27
plugins/compound-engineering/agents/research/repo-research-analyst.md
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.