Drives the GME Test Agent from inside Harness: three tools list interface catalogs, start and repair autonomous test generation in a local Python backend, poll the task until review, and keep PR, skip and cleanup actions behind explicit user consent.
Author: nuaaweixinye · Workflow & Automation · Catalog snapshot: 2026-09-19Canonical semantic path
Drives the GME Test Agent from inside Harness: three tools list interface catalogs, start and repair autonomous test generation in a local Python backend, poll the task until review, and keep PR, skip and cleanup actions behind explicit user consent.
Imported third-party catalog description; not a Registry verification conclusion.— stars · — downloads
Signals were provided by the source catalog and do not imply quality or safety. 2026-09-19Active analysis coverage 1/5. Historical chains are retained but do not count toward current coverage.
Source structure has not been analyzed.
Repository metadata has not been analyzed.
npm release metadata has not been analyzed.
Conclusion: Compatibility verification did not pass: the bounded compatibility check did not pass. Test environment: DSH 0.1.6-alpha.2, web profile.
Conclusion: The dependency audit did not produce a complete report.
The plugin’s advertised feature has not been automatically verified. Passing installation and startup does not prove that feature works.
Conclusion: The bounded static scan found none of its predefined risk signals. This is not proof of safety.
Conclusion: Package structure or integrity validation did not pass.
Automated evidence is scoped to the named artifact, DSH target and profile. It is not a blanket safety or feature-completeness claim.
Describe your task in a DSH conversation and mention dsh-gme-workflow. After installing or updating the manager from npm latest, it can find this candidate through Registry, then inspect its actual source and version locally.
github:nuaaweixinye/dsh-gme-workflowExact version not resolved