Master backend architectures, REST API design, microservices, and server-side development across multiple languages. Use this as a central index to access specialized sub-skills.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyzes PHP codebase for SOLID principle violations. Detects God classes (SRP), type switches (OCP), broken contracts (LSP), fat interfaces (ISP), and concrete dependencies (DIP). Generates actionable reports with severity levels and remediation recommendations.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
This skill analyzes PHP codebases for SOLID principle violations and generates detailed reports with severity levels and remediation recommendations.
Determine analysis scope from user input or detect automatically:
# Detect project structure
ls -la src/
# Identify key directories
find . -type d -name "Domain" -o -name "Application" -o -name "Infrastructure"
Execute detection patterns for each SOLID principle.
# Find large classes (>500 lines)
find . -name "*.php" -path "*/src/*" -exec wc -l {} \; | awk '$1 > 500 {print "CRITICAL: " $0}'
# Find classes with many methods
for file in $(find . -name "*.php" -path "*/src/*"); do
count=$(grep -c "public function" "$file" 2>/dev/null || echo 0)
if [ "$count" -gt 15 ]; then
echo "WARNING: $file has $count public methods"
fi
done
# Classes with problematic names
grep -rn "class.*Manager\|class.*Handler\|class.*Helper\|class.*Util" --include="*.php" src/
# Count constructor dependencies
grep -rn "__construct" --include="*.php" -A 20 src/ | \
grep -E "private|readonly" | \
awk -F: '{files[$1]++} END {for(f in files) if(files[f]>7) print "WARNING: " f " has " files[f] " dependencies"}'
# Classes with "And" in name
grep -rn "class\s\+\w*And\w*" --include="*.php" src/
# Check for mixed concerns
grep -rn "class.*Service" --include="*.php" src/ -l | while read file; do
if grep -q "Repository\|Mailer\|Logger" "$file"; then
echo "INFO: $file may have mixed concerns"
fi
done
# Switch on type property
grep -rn "switch.*->type\|match.*->type\|match.*::class" --include="*.php" src/
# instanceof chains
grep -rn "if.*instanceof\|elseif.*instanceof" --include="*.php" src/
# Type-based conditionals
grep -rn "if.*getType\(\)\s*===\|if.*->type\s*===" --include="*.php" src/
# Hardcoded type maps
grep -rn "\[.*::class\s*=>" --include="*.php" src/
# Classes that need frequent modification (check git history if available)
git log --since="3 months ago" --name-only --pretty=format: -- "*.php" | \
sort | uniq -c | sort -rn | head -20
# NotImplementedException throws
grep -rn "throw.*NotImplemented\|throw.*NotSupported\|throw.*UnsupportedOperation" --include="*.php" src/
# Empty method overrides
grep -rn "public function.*\{[\s]*\}" --include="*.php" src/
# Parent type checks in child classes
grep -rn "if.*parent::\|parent::.*?:" --include="*.php" src/
# Additional validation in overrides
grep -rn "function.*override" --include="*.php" -A 10 src/ | grep "if.*throw"
# Return null where parent might not
grep -rn "return\s*null;" --include="*.php" src/
# Count methods in interfaces
for file in $(find . -name "*.php" -path "*/src/*" -exec grep -l "^interface" {} \;); do
count=$(grep -c "public function" "$file" 2>/dev/null || echo 0)
if [ "$count" -gt 5 ]; then
echo "WARNING: $file interface has $count methods"
fi
if [ "$count" -gt 8 ]; then
echo "CRITICAL: $file interface has $count methods - consider splitting"
fi
done
# Find "// TODO" or "// not implemented" in interface implementations
grep -rn "//\s*TODO\|//\s*not implemented\|//\s*unused" --include="*.php" src/
# Empty implementations
grep -rn "function.*\{[\s]*return;\s*\}" --include="*.php" src/
# Overly generic interface names
grep -rn "interface\s\+\(Service\|Manager\|Handler\)\s*$" --include="*.php" src/
# New in methods (excluding exceptions, DateTime, stdClass)
grep -rn "new\s\+[A-Z]" --include="*.php" src/ | \
grep -v "Exception\|DateTime\|stdClass\|DateTimeImmutable\|ArrayObject\|SplQueue"
# Static method calls to concrete classes
grep -rn "[A-Z][a-z]*::[a-z]" --include="*.php" src/ | \
grep -v "self::\|static::\|parent::\|Uuid::\|Money::"
# Constructor with concrete types (not interfaces)
grep -rn "__construct" --include="*.php" -A 15 src/ | \
grep -E "(private|readonly)\s+[A-Z][a-z]*[A-Z][a-z]*\s+\\\$" | \
grep -v "Interface\|Abstract\|Contract"
# Container/locator usage
grep -rn "container->get\|app()->make\|\\\$this->get(" --include="*.php" src/
# SOLID Violations Report
## Summary
| Principle | Critical | Warning | Info |
|-----------|----------|---------|------|
| SRP | X | X | X |
| OCP | X | X | X |
| LSP | X | X | X |
| ISP | X | X | X |
| DIP | X | X | X |
## Critical Violations
### SRP-001: God Class
- **File:** `src/Service/UserManager.php`
- **Lines:** 847
- **Issue:** Class exceeds 500 lines with 23 public methods
- **Recommendation:** Extract into focused classes
- **Skills:** `acc-create-use-case`, `acc-create-domain-service`
### OCP-001: Type Switch
- **File:** `src/Payment/PaymentProcessor.php:45`
- **Issue:** Switch on payment type requires modification for new types
- **Recommendation:** Apply Strategy pattern
- **Skills:** `acc-create-strategy`
## Warning Violations
### ISP-001: Fat Interface
- **File:** `src/Repository/UserRepository.php`
- **Methods:** 12
- **Issue:** Interface too large, clients forced to depend on unused methods
- **Recommendation:** Segregate into UserReader, UserWriter, UserStats
## Remediation Priority
1. **Immediate:** God classes blocking testing
2. **High:** Type switches preventing extension
3. **Medium:** Fat interfaces causing coupling
4. **Low:** Minor DIP violations
| Severity | Criteria | Action |
|---|---|---|
| CRITICAL | >500 LOC, >10 deps, NotImplementedException | Immediate refactoring |
| WARNING | 300-500 LOC, 7-10 deps, type switches | Plan refactoring |
| INFO | 200-300 LOC, minor issues | Monitor in next iteration |
| Violation | Recommended Skill |
|---|---|
| God Class | acc-create-use-case |
| Type Switch | acc-create-strategy |
| No Interface | acc-create-repository |
| Domain Logic | acc-create-domain-service |
| Value Extraction | acc-create-value-object |
| Factory Missing | acc-create-factory |
| Decorator Need | acc-create-decorator |
# Full analysis
echo "=== SRP ===" && \
find . -name "*.php" -path "*/src/*" -exec wc -l {} \; | awk '$1 > 400' && \
echo "=== OCP ===" && \
grep -rn "switch.*type\|match.*::class" --include="*.php" src/ && \
echo "=== LSP ===" && \
grep -rn "NotImplemented\|NotSupported" --include="*.php" src/ && \
echo "=== ISP ===" && \
for f in $(find . -name "*.php" -exec grep -l "^interface" {} \;); do \
c=$(grep -c "public function" "$f"); [ $c -gt 5 ] && echo "$f: $c methods"; \
done && \
echo "=== DIP ===" && \
grep -rn "new\s\+[A-Z]" --include="*.php" src/ | grep -v "Exception\|DateTime" | head -20
This analyzer uses detection patterns from acc-solid-knowledge. For detailed principle explanations and patterns, refer to:
acc-solid-knowledge/references/srp-patterns.mdacc-solid-knowledge/references/ocp-patterns.mdacc-solid-knowledge/references/lsp-patterns.mdacc-solid-knowledge/references/isp-patterns.mdacc-solid-knowledge/references/dip-patterns.mdacc-solid-knowledge/references/antipatterns.mdSee assets/report-template.md for the full report format.
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Master backend architectures, REST API design, microservices, and server-side development across multiple languages. Use this as a central index to access specialized sub-skills.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
在每次回复中使用固定前缀并列出本次实际参考的指令/文件,便于校验是否遵循上下文与规则。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Automate 21risk tasks via Rube MCP (Composio). Always search tools first for current schemas.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Automate 2chat tasks via Rube MCP (Composio). Always search tools first for current schemas.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Arquitecto de Soluciones Principal y Consultor Tecnológico de Andru.ia. Diagnostica y traza la hoja de ruta óptima para proyectos de IA en español.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
[00] META. Orchestrate skills into dynamic chains for complex tasks. Analyzes the task, discovers available skills, builds an optimal chain, explains why each skill is needed, and executes step-by-step with user confirmation. Use for any complex task requiring multiple thinking/research/analysis steps. Triggers on "plan this", "how to approach", "what's the strategy", "build a plan", or any multi-step problem requiring skill orchestration.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.