discipline-refactor-phase-4-validation
Sub-skill of discipline-refactor: Phase 4: Validation.
Best use case
discipline-refactor-phase-4-validation is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Sub-skill of discipline-refactor: Phase 4: Validation.
Teams using discipline-refactor-phase-4-validation should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/phase-4-validation/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How discipline-refactor-phase-4-validation Compares
| Feature / Agent | discipline-refactor-phase-4-validation | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Sub-skill of discipline-refactor: Phase 4: Validation.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# Phase 4: Validation
## Phase 4: Validation
**Spawn**: `Task` with `subagent_type=Bash`
**Prompt**:
```
Validate module-based refactoring:
1. Structure validation:
- [ ] src/<package>/modules/ exists with disciplines
- [ ] tests/modules/ mirrors src structure
- [ ] docs/modules/ exists
- [ ] specs/modules/ exists
- [ ] Each module has __init__.py (Python) or index (JS)
- [ ] Each module has README.md
2. Import validation:
- [ ] No old import paths remain
- [ ] All imports resolve
- [ ] Circular imports checked
3. Test validation:
- [ ] pytest / npm test passes
- [ ] Coverage maintained
4. Documentation validation:
- [ ] Internal links work
- [ ] Module READMEs complete
Generate report. On failure, suggest:
git checkout pre-module-refactor-{date}
```
---Related Skills
data-validation-reporter
Generate interactive validation reports with quality scoring, missing data analysis, and type checking. Combines Pandas validation, Plotly visualization, and YAML configuration for comprehensive data quality reporting.
gtm-demo-validation-cache-regression-repair
Diagnose and repair GTM demo validation failures caused by legacy cache files missing intermediate chart data, especially in nested digitalmodel demo scripts using --from-cache.
plan-gated-issue-validation-workflow
Systematic validation pattern for plan-approved GitHub issues with pre-existing deliverables
blocker-reporting-outcome-validation
Pattern for closing issues where the deliverable is documented blockers rather than feature completion
gtm-prospect-pipeline-phased-execution
Phased execution pattern for
gtm-demo-validation-and-preview-gif-workflow
Validate digitalmodel GTM demos end-to-end, recover from legacy Demo 2 cache regressions, regenerate fresh artifacts, and produce lightweight preview GIFs for issue
github-actions-cross-platform-validation-gotchas
Execution-time GitHub Actions pitfalls discovered while fixing cross-platform CI workflows — path-filter non-triggers, Windows shell parsing mismatches, and job-scoped validation.
data-validation
QA an analysis before sharing with stakeholders -- methodology checks, accuracy verification, and bias detection
plan-rerun-state-revalidation
Revalidate live plan state before rerunning adversarial review or resuming from a handoff so review prompts do not encode stale approval/artifact assumptions.
module-based-refactor
Reorganize a repository from flat structure to a module-based 5-layer architecture (src/tests/specs/docs/examples) while preserving git history. Use when restructuring a codebase into modules, migrating import paths, cleaning up hidden folders, consolidating duplicate directories, removing root-level artifacts, or archiving completed plan files. Capabilities: parallel agent spawn strategy, hidden-folder consolidation patterns, benchmark fixture separation, 4-phase atomic commit workflow.
discipline-refactor-verification-checklist
Sub-skill of discipline-refactor: Verification Checklist.
discipline-refactor-target-repository-structure
Sub-skill of discipline-refactor: Target Repository Structure.