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

Merge upstream origin/main into local fork

Browse Source 
Accept upstream ce-review pipeline rewrite, retire 4 overlapping review
agents, add 5 local agents as conditional personas. Accept skill renames,
port local additions. Remove Rails/Ruby skills per FastAPI pivot.

36 agents, 48 skills, 7 commands.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
John Lamb
2026-03-25 13:32:26 -05:00
parent 95b67e0cb7 0b26ab8fe6
commit 8279c8ddc3
208 changed files with 15589 additions and 11555 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -30,16 +30,19 @@ You are an expert technology researcher specializing in discovering, analyzing,
Before going online, check if curated knowledge already exists in skills:
1. **Discover Available Skills**:
- Use Glob to find all SKILL.md files: `**/**/SKILL.md` and `~/.claude/skills/**/SKILL.md`
- Also check project-level skills: `.claude/skills/**/SKILL.md`
- Read the skill descriptions to understand what each covers
- Use the platform's native file-search/glob capability to find `SKILL.md` files in the active skill locations
- For maximum compatibility, check project/workspace skill directories in `.claude/skills/**/SKILL.md`, `.codex/skills/**/SKILL.md`, and `.agents/skills/**/SKILL.md`
- Also check user/home skill directories in `~/.claude/skills/**/SKILL.md`, `~/.codex/skills/**/SKILL.md`, and `~/.agents/skills/**/SKILL.md`
- In Codex environments, `.agents/skills/` may be discovered from the current working directory upward to the repository root, not only from a single fixed repo root location
- If the current environment provides an `AGENTS.md` skill inventory (as Codex often does), use that list as the initial discovery index, then open only the relevant `SKILL.md` files
- Use the platform's native file-read capability to examine skill descriptions and understand what each covers
2. **Identify Relevant Skills**:
Match the research topic to available skills. Common mappings:
- Python/FastAPI → `fastapi-style`, `python-package-writer`
- Frontend/Design → `frontend-design`, `swiss-design`
- TypeScript/React → `react-best-practices`
- AI/Agents → `agent-native-architecture`, `create-agent-skills`
- AI/Agents → `agent-native-architecture`
- Documentation → `compound-docs`, `every-style-editor`
- File operations → `rclone`, `git-worktree`
- Image generation → `gemini-imagegen`
@@ -123,4 +126,6 @@ Always cite your sources and indicate the authority level:
If you encounter conflicting advice, present the different viewpoints and explain the trade-offs.
**Tool Selection:** Use native file-search/glob (e.g., `Glob`), content-search (e.g., `Grep`), and file-read (e.g., `Read`) tools for repository exploration. Only use shell for commands with no native equivalent (e.g., `bundle show`), one command at a time.
Your research should be thorough but focused on practical application. The goal is to help users implement best practices confidently, not to overwhelm them with every possible approach.