بنقرة واحدة
reviews-pragmatic
Run pragmatic code review to detect over-engineering and ensure code matches project scale
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Run pragmatic code review to detect over-engineering and ensure code matches project scale
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Unified orchestrator for all development tasks. ALWAYS execute when invoked — never skip for 'straightforward' tasks. Phases adapt based on detected task characteristics rather than predetermined types. Use for any development work that modifies code.
Internal engine for managing project documentation and technical standards in .agyflow/docs/. Handles file operations, INDEX.md generation, and AGENTS.md integration. Invoked by flow-init, standards-update, and standards-discover skills.
Initialize AI SDLC framework with intelligent project analysis and documentation generation
Orchestrates the complete migration workflow from current state analysis through implementation to compatibility verification. Handles technology migrations, platform changes, and architecture pattern transitions with adaptive risk assessment, incremental execution, and rollback planning. Use when migrating technologies, platforms, or architecture patterns.
Orchestrates performance optimization workflows using static code analysis to identify bottlenecks (N+1 queries, missing indexes, O(n^2) algorithms, blocking I/O, memory leaks). Accepts optional user-provided profiling data. Reuses standard specification, planning, implementation, and verification phases.
Interactive product/feature design orchestrator. Transforms fuzzy ideas into structured product briefs through collaborative exploration, iterative refinement, and visual prototyping. Adaptive phases detect design complexity and adjust depth.
| name | reviews-pragmatic |
| description | Run pragmatic code review to detect over-engineering and ensure code matches project scale |
ACTION REQUIRED: This command delegates to a different skill. The <command-name> tag refers to THIS command, not the target. Call the Task tool with subagent_type="code-quality-pragmatist" NOW. Pass the path to analyze in the prompt. Do not read files, explore code, or execute workflow steps yourself.
You are running a pragmatic code review using the code-quality-pragmatist agent.
You are performing pragmatic analysis to identify over-engineering, unnecessary complexity, and developer experience issues.
Determine the following from the user's request:
Invoke the code-quality-pragmatist agent NOW using the Task tool:
Task Tool:
- subagent_type: code-quality-pragmatist
- description: Pragmatic code review
- prompt: |
You are the code-quality-pragmatist agent. Review the code at: [path]
Your task:
1. Assess overall complexity relative to project scale (check .agyflow/docs/project/ for scale)
2. Detect over-engineering patterns (infrastructure overkill, excessive abstraction, enterprise patterns in simple code)
3. Assess developer experience (setup complexity, feedback loops, error messages, consistency)
4. Verify requirements alignment (if spec.md available, compare implementation to requirements)
5. Recommend specific simplifications with before/after examples
6. Prioritize top 3 changes with highest impact
Generate comprehensive pragmatic review report.
Save to: verification/pragmatic-review.md
Focus on: Simple solutions for simple problems. Code should match project needs, not theoretical best practices.
Wait for the agent to complete before proceeding.
The code-quality-pragmatist agent will:
Example 1: Review specific feature
User: /agyflow:reviews-pragmatic .agyflow/tasks/development/2025-11-17-user-management/
Example 2: Review source directory
User: /agyflow:reviews-pragmatic src/features/payments/
Example 3: Review specific file
User: /agyflow:reviews-pragmatic src/services/cache-service.ts
The code-quality-pragmatist will provide: