Claude
Skill
goga-change-validator
Final end-to-end validation of the completed change
Virus-scanned
Reviewed automatically before listing.
Download
qarium-goga-goga_assets_skills_goga-change-validator-f1257db.zip · 1 KB
Install
skills CLI
npx skills add https://github.com/qarium/goga/tree/1.2.x/goga/assets/skills/goga-change-validator
Claude Code
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install qarium-goga@llmmart
Git
git clone https://github.com/qarium/goga.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole qarium/goga collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
goga-change-validator
Identity
You are responsible for final end-to-end validation of the completed change.
Algorithm
Execute only after: implementation stabilized, tests passing, reconciliation completed, drift analyzed.
- Load original task description
- Load approved Change Plan
- Verify implementation matches Change Plan — no unplanned modifications
- Run full test suite
- Run project validators and linters
- Execute:
goga lint— final CODEMANIFEST validation - Verify scope integrity — all changes within scope from scope-resolver
- Verify backward compatibility — compatibility-guard verdict was respected
- Apply goga-lang-disp — verify language conventions are followed in implementation and tests
- Apply goga-codemanifest-base — verify base usages and annotations are preserved in all affected CODEMANIFEST files
- Verify triple consistency per affected cell:
- CODEMANIFEST ↔ implementation
- implementation ↔ .usages
- CODEMANIFEST ↔ .usages
- Verify template completeness — all previous skills produced complete outputs
- Check for unresolved drift from drift-analyzer
- Produce Validation Report
STOP if:
- any test fails
- any validator/linter fails
- changes outside approved scope
- backward compatibility broken
- triple consistency violated
- any previous skill output has empty sections
- unresolved drift detected
Output Format
Fill every section. No empty sections.
# Validation Report
## Scope Resolution
[All modifications within scope? Excluded cells untouched?]
## Task Resolution
[Original task satisfied? Root cause eliminated?]
## Trace Consistency
[Behavioral traces valid? Data/call flows intact?]
## Change Plan Compliance
[Implementation matches plan? No unplanned changes?]
## Backward Compatibility
[API/semantic/algorithmic/usage compatibility preserved?]
## Implementation Quality
[Tests pass? Linters pass? No orphaned code?]
## Test Coverage
[Changed behavior covered? Algorithm stages covered? Regression scenarios?]
## Manifest Reconciliation
[Table: Cell | Algorithms | Operational Flow | Guarantees | Practices | Status]
## Usage Reconciliation
[Table: Usage | Classification | Validated | Status]
## Drift Resolution
[All drift resolved? List any remaining]
## Template Completeness
[Table: Skill | All Sections Filled? | Missing Sections]
## Blocking Issues
[List any blocking issues. Empty if none]
## Overall Status
[VERIFIED / PARTIAL / FAILED — with justification]
Files (goga)
-
SKILL.md 2.6 KB
--- name: goga-change-validator description: Final end-to-end validation of the completed change --- # goga-change-validator ## Identity You are responsible for final end-to-end validation of the completed change. ## Algorithm Execute only after: implementation stabilized, tests passing, reconciliation completed, drift analyzed. 1. Load original task description 2. Load approved Change Plan 3. Verify implementation matches Change Plan — no unplanned modifications 4. Run full test suite 5. Run project validators and linters 6. Execute: `goga lint` — final CODEMANIFEST validation 7. Verify scope integrity — all changes within scope from scope-resolver 8. Verify backward compatibility — compatibility-guard verdict was respected 9. Apply goga-lang-disp — verify language conventions are followed in implementation and tests 10. Apply goga-codemanifest-base — verify base usages and annotations are preserved in all affected CODEMANIFEST files 11. Verify triple consistency per affected cell: - CODEMANIFEST ↔ implementation - implementation ↔ .usages - CODEMANIFEST ↔ .usages 12. Verify template completeness — all previous skills produced complete outputs 13. Check for unresolved drift from drift-analyzer 14. Produce Validation Report STOP if: - any test fails - any validator/linter fails - changes outside approved scope - backward compatibility broken - triple consistency violated - any previous skill output has empty sections - unresolved drift detected ## Output Format Fill every section. No empty sections. ```md # Validation Report ## Scope Resolution [All modifications within scope? Excluded cells untouched?] ## Task Resolution [Original task satisfied? Root cause eliminated?] ## Trace Consistency [Behavioral traces valid? Data/call flows intact?] ## Change Plan Compliance [Implementation matches plan? No unplanned changes?] ## Backward Compatibility [API/semantic/algorithmic/usage compatibility preserved?] ## Implementation Quality [Tests pass? Linters pass? No orphaned code?] ## Test Coverage [Changed behavior covered? Algorithm stages covered? Regression scenarios?] ## Manifest Reconciliation [Table: Cell | Algorithms | Operational Flow | Guarantees | Practices | Status] ## Usage Reconciliation [Table: Usage | Classification | Validated | Status] ## Drift Resolution [All drift resolved? List any remaining] ## Template Completeness [Table: Skill | All Sections Filled? | Missing Sections] ## Blocking Issues [List any blocking issues. Empty if none] ## Overall Status [VERIFIED / PARTIAL / FAILED — with justification] ```
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.