Menü
Run the full quality gate for GedPi — type-check then test suite. Use before committing or after significant changes.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
| name | verify |
| description | Run the full quality gate for GedPi — type-check then test suite. Use before committing or after significant changes. |
Run the full quality gate:
npm run check && npm run lint && npm test
Report any type errors, lint errors, or test failures. If all pass, the codebase is ready to commit.
Discover external skills during GedPi's skill-fit checkpoint. When the current bundled, project, and user skills don't cover a task's needs, search the open ecosystem via npx skills, evaluate candidates, and install through GedPi's project-skill mechanism. Triggers include "how do I do X", "find a skill for X", "is there a skill for X", "skill for", "need a skill", "search for skills", "skill-fit", "ecosystem"
Implements the next task from .ged/work/<work-id>/TASKS.md with narrow scope and concise handoff notes. Triggers include "do the next task", "implement", "execute", or when a task is ready for implementation.
Produces or refines implementation plans in .ged/work/<work-id>/SPEC.md, task breakdowns in .ged/work/<work-id>/TASKS.md, and verification criteria in .ged/work/<work-id>/TESTS.md. Triggers include "plan", "break down", "what tasks", "how to implement", or when starting a new feature.
Runs checks from .ged/work/<work-id>/TESTS.md after task implementation, summarizes pass/fail, and prepares retry briefs. Triggers include "verify", "test", "check", "did it work", or after completing an implementation task.
Use before planning or implementing a non-trivial change when the request is not fully clear. Clarifies goals, desired behavior, constraints, edge cases, non-goals, tests, rollout, and success criteria by asking one concise question at a time with a recommended answer/default.
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions. Triggers include "domain", "glossary", "terminology", "ubiquitous language", "CONTEXT.md", "ADR", "architecture decision", "decision record", "context map", "domain model".