feat: enhancement workflow preset system with multi-target CLI
- Add YAML-based enhancement workflow presets shipped inside the package (default, minimal, security-focus, architecture-comprehensive, api-documentation) - Add `skill-seekers workflows` subcommand: list, show, copy, add, remove, validate - copy/add/remove all accept multiple names/files in one invocation with partial-failure behaviour - `add --name` override restricted to single-file operations - Add 5 MCP tools: list_workflows, get_workflow, create_workflow, update_workflow, delete_workflow - Fix: create command _add_common_args() now correctly forwards each --enhance-workflow as a separate flag instead of passing the whole list as a single argument - Update README: reposition as "data layer for AI systems" with AI Skills front and centre - Update CHANGELOG, QUICK_REFERENCE, CLAUDE.md with workflow preset details - 1,880+ tests passing Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
This commit is contained in:
72
src/skill_seekers/workflows/architecture-comprehensive.yaml
Normal file
72
src/skill_seekers/workflows/architecture-comprehensive.yaml
Normal file
@@ -0,0 +1,72 @@
|
||||
name: architecture-comprehensive
|
||||
description: Deep architectural analysis including patterns, dependencies, and design quality
|
||||
version: "1.0"
|
||||
applies_to:
|
||||
- codebase_analysis
|
||||
- github_analysis
|
||||
variables:
|
||||
depth: comprehensive
|
||||
stages:
|
||||
- name: base_patterns
|
||||
type: builtin
|
||||
target: patterns
|
||||
enabled: true
|
||||
uses_history: false
|
||||
- name: architecture_overview
|
||||
type: custom
|
||||
target: architecture
|
||||
uses_history: false
|
||||
enabled: true
|
||||
prompt: >
|
||||
Analyse the architectural patterns and design decisions in this codebase.
|
||||
|
||||
Identify:
|
||||
1. Overall architectural style (MVC, microservices, layered, hexagonal, etc.)
|
||||
2. Key design patterns used and their purpose
|
||||
3. Component boundaries and responsibilities
|
||||
4. Data flow between components
|
||||
5. External dependencies and integration points
|
||||
|
||||
Output JSON with an "architecture" object containing:
|
||||
- "style": primary architectural style
|
||||
- "patterns": list of design patterns detected
|
||||
- "components": list of key components with descriptions
|
||||
- "data_flow": description of data flow
|
||||
- "quality_score": 1-10 rating with justification
|
||||
- name: dependency_analysis
|
||||
type: custom
|
||||
target: dependencies
|
||||
uses_history: true
|
||||
enabled: true
|
||||
prompt: >
|
||||
Based on the architectural overview, analyse the dependency structure.
|
||||
|
||||
Identify:
|
||||
1. Circular dependencies (red flags)
|
||||
2. High coupling between modules
|
||||
3. Opportunities for dependency injection
|
||||
4. Third-party dependency risks (outdated, unmaintained)
|
||||
5. Suggested refactoring priorities
|
||||
|
||||
Output JSON with a "dependency_analysis" object.
|
||||
- name: improvement_roadmap
|
||||
type: custom
|
||||
target: roadmap
|
||||
uses_history: true
|
||||
enabled: true
|
||||
prompt: >
|
||||
Based on the full architectural analysis, create an improvement roadmap.
|
||||
|
||||
Provide:
|
||||
1. Top 3 quick wins (low effort, high impact)
|
||||
2. Medium-term improvements (1-3 months)
|
||||
3. Long-term architectural goals
|
||||
4. Technical debt prioritisation
|
||||
|
||||
Output JSON with a "roadmap" object containing "quick_wins", "medium_term", and "long_term" arrays.
|
||||
post_process:
|
||||
reorder_sections: []
|
||||
add_metadata:
|
||||
enhanced: true
|
||||
workflow: architecture-comprehensive
|
||||
deep_analysis: true
|
||||
Reference in New Issue
Block a user