Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

codex-test-review

Sterne175

Forks23

Aktualisiert4. April 2026 um 07:35

Review test case sufficiency using Codex MCP, suggest additional edge cases. Supports review loop with context preservation.

Installation

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.

In Manus ausführen

Quelle

sd0xdev

sd0xdev/sd0x-dev-flow

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

Softwarequalitätssicherungsanalysten und -testerInformatik- und Mathematikberufe·SOC 15-1253

SKILL.md

readonly

name	codex-test-review
description	Review test case sufficiency using Codex MCP, suggest additional edge cases. Supports review loop with context preservation.
allowed-tools	mcp__codex__codex, mcp__codex__codex-reply, Bash(git:*), Read, Grep, Glob

Codex Test Review

Thin entry-point skill — routes to the parent skill for full workflow.

Parent Skill

This skill delegates to test-review for the full test coverage review workflow, prompt templates, and sufficiency assessment.

See @skills/test-review/SKILL.md

Variant

This is the Review variant — evaluates existing test coverage and suggests gaps.

Trigger

Keywords: test review, review tests, test coverage, test sufficiency, codex-test-review

When NOT to Use

Generating new tests (use /codex-test-gen)
Code review (use /codex-review-fast)
Security audit (use /codex-security)

Mehr aus diesem Repository

gleiches Repository

ui-first-principles

sd0xdev/sd0x-dev-flow

First-principles UI/IA reasoning: turns a `<scenario>` + API field set into JTBD analysis, principle-anchored field-priority decisions, anti-pattern findings, and a bidirectional UI↔API gap report. Trigger: UI、UX、資訊架構、IA、scenario-driven UI、欄位優先級、information hierarchy. Not for: visual/CSS work (use `/frontend-design`), post-build critique (use `/critique`), or simplifying existing layouts (use `/distill`).

2026-04-27175

necessity-audit

sd0xdev/sd0x-dev-flow

Necessity audit for over-designed spec elements. Use when: auditing lifecycle spec (1-requirements / 2-tech-spec / 3-architecture) for YAGNI/KISS violations, challenging necessity of FRs/NFRs/abstractions/configs via Codex adversarial debate. Not for: FP reasoning validity (use /codex-review-spec), completeness check (use /feature-completeness), detail review (use /codex-review-doc), or code-level simplification (use /simplify).

2026-04-21175

epic-merge

sd0xdev/sd0x-dev-flow

Sequential squash-merge of stacked PR chains into an epic branch. Handles dependency-ordered rebase, collision-safe backup tags, CI monitoring (delegates to /watch-ci), and post-merge verification. Use when: merging a chain of stacked PRs into an epic branch, collapsing a linear PR stack into per-PR squash commits, preparing an epic branch for final review. Triggers on: 'merge PRs into epic', 'squash chain', 'collapse PR stack', 'epic merge', or when user has a linear PR dependency chain (PR A -> B -> C) targeting an epic branch. Not for: single PR merge (use /create-pr + GitHub UI), simple rebase (use /smart-rebase), pre-merge analysis (use /merge-prep). Output: chain analysis table + backup tag manifest + per-iteration AskUserQuestion gate + verification log.

2026-04-20175

push-ci

sd0xdev/sd0x-dev-flow

Push to remote and monitor CI. Validates branch safety, executes git push WITH explicit user approval, then monitors CI run status via gh CLI. Use when: user says 'push', 'push and watch CI', 'ship it', 'push-ci'. Not for: committing (use /smart-commit), creating PRs (use /create-pr), merging (use /merge-prep).

2026-04-20175

post-dev-recap

sd0xdev/sd0x-dev-flow

Post-development recap wrapper. Use when: AI/Codex just finished implementing a feature and the user wants a guided walkthrough with scope detection + doc generation + follow-up Q&A. Not for: generating only a doc (use /recap-doc), Q&A over an existing recap (use /recap-ask), technical share-out (use /tech-brief), first-principles reasoning of an existing doc (use /fp-brief), general code tracing (use /code-explore). Output: ScopeReport → briefing-recap-<date>.md → interactive Q&A session.

2026-04-17175

recap-ask

sd0xdev/sd0x-dev-flow

Interactive Q&A over an existing recap document. Use when: user wants to ask follow-up questions about a briefing-recap-<date>.md produced by /recap-doc, with recap-bounded context + out-of-scope redirect + optional promote-to-request. Not for: generating a new recap (use /recap-doc), general project Q&A (use /ask), code tracing (use /code-explore). Output: per-turn answer referencing file:line + end-of-session promote prompt.

2026-04-17175

name	codex-test-review
description	Review test case sufficiency using Codex MCP, suggest additional edge cases. Supports review loop with context preservation.
allowed-tools	mcp__codex__codex, mcp__codex__codex-reply, Bash(git:*), Read, Grep, Glob

Codex Test Review

Thin entry-point skill — routes to the parent skill for full workflow.

Parent Skill

This skill delegates to test-review for the full test coverage review workflow, prompt templates, and sufficiency assessment.

See @skills/test-review/SKILL.md

Variant

This is the Review variant — evaluates existing test coverage and suggests gaps.

Trigger

Keywords: test review, review tests, test coverage, test sufficiency, codex-test-review

When NOT to Use

Generating new tests (use /codex-test-gen)
Code review (use /codex-review-fast)
Security audit (use /codex-security)