Detects installed developer plugins (python-developer, frontend-developer, php-developer) and project stack, then provides a list of relevant skills to load for code review and fix workflows. Supports Python (FastAPI, SQLAlchemy, Pydantic, Django, Celery, asyncio, uv), Frontend (React, Tailwind, Zustand, TanStack, pnpm), and PHP (Symfony, Doctrine, DDD).
Instalação
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Detects installed developer plugins (python-developer, frontend-developer, php-developer) and project stack, then provides a list of relevant skills to load for code review and fix workflows. Supports Python (FastAPI, SQLAlchemy, Pydantic, Django, Celery, asyncio, uv), Frontend (React, Tailwind, Zustand, TanStack, pnpm), and PHP (Symfony, Doctrine, DDD).
Detects installed developer plugins and project stack, then provides a list of relevant skills to load for code review and fix workflows. Acts as the bridge between the code-review plugin and specialized developer plugins (python-developer, frontend-developer, php-developer).
Overview
This skill is the detection and integration layer between the code-review plugin and developer plugins. It performs three tasks:
Stack Detection - Identifies which technology stacks are present in the project (Python, Frontend/React, PHP)
Plugin Detection - Checks which developer plugins are installed and available in the current session
Skill Resolution - Produces a list of skills to load, based on detected stack and available plugins
The output is consumed by the review command, auditors, and fix workflows to ensure framework-specific patterns are enforced during code review.
Stack Detection
Step 1: Detect Python Stack
ALWAYS check these files in project root and first-level subdirectories:
If ANY of these files exist, Python stack is detected.
Step 2: Detect Python Frameworks
Only run if Python stack is detected. Grep dependencies in every pyproject.toml and requirements.txt that triggered detection (root and first-level subdirectories):
echo"=== Python Framework Detection ==="# Collect all Python dependency files (root + subdirectories)
PYTHON_DEP_FILES=""for f in pyproject.toml requirements.txt; do
[ -f "$f" ] && PYTHON_DEP_FILES="$PYTHON_DEP_FILES$f"donefordirin */; dofor f in pyproject.toml requirements.txt; do
[ -f "$dir$f" ] && PYTHON_DEP_FILES="$PYTHON_DEP_FILES $dir$f"donedone# FastAPI
FASTAPI=falsefor f in$PYTHON_DEP_FILES; do
grep -qi "fastapi""$f" 2>/dev/null && FASTAPI=truedoneecho"FastAPI: $FASTAPI"# SQLAlchemy
SQLALCHEMY=falsefor f in$PYTHON_DEP_FILES; do
grep -qi "sqlalchemy""$f" 2>/dev/null && SQLALCHEMY=truedoneecho"SQLAlchemy: $SQLALCHEMY"# Pydantic
PYDANTIC=falsefor f in$PYTHON_DEP_FILES; do
grep -qi "pydantic""$f" 2>/dev/null && PYDANTIC=truedoneecho"Pydantic: $PYDANTIC"# asyncio (check source files for async def or asyncio import)
ASYNCIO=false
grep -rqE "import asyncio|from asyncio|async def" --include="*.py" . 2>/dev/null && ASYNCIO=trueecho"asyncio: $ASYNCIO"# uv (check for uv.lock in root and subdirectories)
UV=false
[ -f "uv.lock" ] && UV=truefordirin */; do
[ -f "$dir/uv.lock" ] && UV=truedoneecho"uv: $UV"# Django
DJANGO=falsefor f in$PYTHON_DEP_FILES; do
grep -qi "django""$f" 2>/dev/null && DJANGO=truedoneecho"Django: $DJANGO"# Celery
CELERY=falsefor f in$PYTHON_DEP_FILES; do
grep -qi "celery""$f" 2>/dev/null && CELERY=truedoneecho"Celery: $CELERY"
Step 3: Detect PHP Stack
ALWAYS check these files in project root and first-level subdirectories:
If package.json contains "react" in dependencies, Frontend stack is detected.
Step 6: Detect Frontend Frameworks
Only run if Frontend stack is detected. Grep every package.json that triggered detection (root and first-level subdirectories) for dependencies and devDependencies:
echo"=== Frontend Framework Detection ==="# Collect all package.json files that contain react (root + subdirectories)
PKG_FILES=""if [ -f "package.json" ]; then
grep -q '"react"' package.json 2>/dev/null && PKG_FILES="$PKG_FILES package.json"fifordirin */; doif [ -f "$dir/package.json" ]; then
grep -q '"react"'"$dir/package.json" 2>/dev/null && PKG_FILES="$PKG_FILES$dir/package.json"fidone# Tailwind
TAILWIND=falsefor f in$PKG_FILES; do
grep -qE '"tailwindcss"|"@tailwindcss/core"'"$f" 2>/dev/null && TAILWIND=truedoneecho"Tailwind: $TAILWIND"# Zustand
ZUSTAND=falsefor f in$PKG_FILES; do
grep -q '"zustand"'"$f" 2>/dev/null && ZUSTAND=truedoneecho"Zustand: $ZUSTAND"# TanStack Query
TANSTACK_QUERY=falsefor f in$PKG_FILES; do
grep -q '"@tanstack/react-query"'"$f" 2>/dev/null && TANSTACK_QUERY=truedoneecho"TanStack Query: $TANSTACK_QUERY"# TanStack Router
TANSTACK_ROUTER=falsefor f in$PKG_FILES; do
grep -q '"@tanstack/react-router"'"$f" 2>/dev/null && TANSTACK_ROUTER=truedoneecho"TanStack Router: $TANSTACK_ROUTER"# React Hook Form
REACT_HOOK_FORM=falsefor f in$PKG_FILES; do
grep -q '"react-hook-form"'"$f" 2>/dev/null && REACT_HOOK_FORM=truedoneecho"React Hook Form: $REACT_HOOK_FORM"# pnpm (check root and subdirectories)
PNPM=false
[ -f "pnpm-lock.yaml" ] && PNPM=truefordirin */; do
[ -f "$dir/pnpm-lock.yaml" ] && PNPM=truedoneecho"pnpm: $PNPM"
Plugin Detection
Check if developer plugins are installed by verifying their skills are available in the current session's skill list.
How to check: Look for these skills in the available skills list:
python-developer:coding-standards - Indicates the python-developer plugin is installed
frontend-developer:coding-standards - Indicates the frontend-developer plugin is installed
php-developer:coding-standards - Indicates the php-developer plugin is installed
If a skill is present in the session's skill list, the corresponding plugin is installed and its skills can be loaded.
Detection approach:
Check the available skills/commands in the current Claude Code session
If python-developer:coding-standards is available, mark python-developer as INSTALLED
If frontend-developer:coding-standards is available, mark frontend-developer as INSTALLED
If php-developer:coding-standards is available, mark php-developer as INSTALLED
Only attempt to load skills from plugins that are confirmed INSTALLED
Output Format
After running detection, produce the following structured report:
Python Skills (load if python-developer INSTALLED AND Python stack detected):
Skill
Condition
python-developer:coding-standards
Always (base skill)
python-developer:tdd-workflow
Always (base skill)
python-developer:fastapi-patterns
FastAPI detected
python-developer:sqlalchemy-patterns
SQLAlchemy detected
python-developer:pydantic-patterns
Pydantic detected
python-developer:async-python-patterns
asyncio detected
python-developer:uv-package-manager
uv detected
python-developer:django-orm-patterns
Django detected
python-developer:django-web-patterns
Django detected
python-developer:celery-patterns
Celery detected
Frontend Skills (load if frontend-developer INSTALLED AND Frontend stack detected):
Skill
Condition
frontend-developer:coding-standards
Always (base skill)
frontend-developer:tdd-workflow
Always (base skill)
frontend-developer:tailwind-patterns
Tailwind detected
frontend-developer:zustand-patterns
Zustand detected
frontend-developer:tanstack-query-patterns
TanStack Query detected
frontend-developer:tanstack-router-patterns
TanStack Router detected
frontend-developer:form-patterns
React Hook Form detected
frontend-developer:pnpm-package-manager
pnpm detected
PHP Skills (load if php-developer INSTALLED AND PHP stack detected):
Skill
Condition
php-developer:coding-standards
Always (base skill)
php-developer:tdd-workflow
Always (base skill)
php-developer:symfony-patterns
Symfony detected
php-developer:doctrine-orm-patterns
Doctrine detected
php-developer:ddd-patterns
DDD structure detected
php-developer:composer
Always (base skill)
Usage in Code Review
Review Command
Load this skill at the START of the review workflow, BEFORE launching auditors. Pass the resolved skill list to all auditor agents so they can apply framework-specific patterns.
1. Run developer-plugins-integration (this skill)
2. Collect skills_to_load list
3. Pass list to auditors when spawning them
4. Auditors load relevant skills alongside their standard skills
Code Quality Auditor
Load developer plugin skills AFTER standard code quality skills. Apply them as additional review criteria:
Check code against framework-specific coding standards
Validate patterns match framework best practices (e.g., FastAPI route patterns, React component patterns)
Flag anti-patterns specific to the detected frameworks
Security Auditor
Load developer plugin skills AFTER standard security scans. Check framework-specific security patterns:
FastAPI: authentication middleware, CORS configuration, input validation
Load during the "Analyze Context" phase. Apply framework patterns when implementing fixes:
Use framework-idiomatic solutions (e.g., Pydantic validators instead of manual validation)
Follow framework conventions for file structure and naming
Apply TDD patterns from the developer plugin's tdd-workflow skill
Graceful Degradation
This skill is designed to fail safely at every level:
No Developer Plugins Installed
Standard code review behavior applies
Zero changes to existing workflow
No errors, no warnings - simply nothing additional to load
The skills_to_load list is empty
Plugin Installed but Stack Does Not Match
If python-developer is installed but no Python stack detected: python skills are NOT loaded
If frontend-developer is installed but no Frontend stack detected: frontend skills are NOT loaded
If php-developer is installed but no PHP stack detected: php skills are NOT loaded
Only the matching plugin + stack combination activates skills
Skill Invocation Fails
If a specific skill fails to load (e.g., python-developer:fastapi-patterns is unavailable): log as unavailable, continue without it
Never block the review workflow due to a missing optional skill
Report unavailable skills in the output for visibility
{"skills_to_load":["python-developer:coding-standards","python-developer:tdd-workflow"],"skills_unavailable":[{"skill":"python-developer:fastapi-patterns","reason":"Skill not found in plugin"}]}
Red Flags - STOP if you
Skip stack detection and assume which plugins to load
Load developer plugin skills without verifying the plugin is installed
Load framework-specific skills without detecting the framework in the project
Block the review workflow because a developer plugin is missing
Ignore the graceful degradation rules
When these occur: Go back and run the full detection workflow.
Final Checklist
Before completing developer plugins integration, verify:
Checked for Python stack indicators (pyproject.toml, setup.py, requirements.txt, etc.)
Checked for Frontend stack indicators (package.json with react)
Checked for PHP stack indicators (composer.json, composer.lock, symfony.lock)