원클릭으로 Manus에서 모든 스킬 실행

시작하기

skill-repro

스타5

포크0

업데이트2026년 4월 19일 11:10

Reproduce reported bugs or symptoms by creating minimal, verifiable scripts in the DAX Lab.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

ShaileshRawat1403

ShaileshRawat1403/dax

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Bug Reproduction Skill

Use this skill when a user reports a bug, unexpected behavior, or failing symptom that needs to be isolated and verified before a fix is implemented.

When to Use

User reports a bug or regression
User provides a failing code snippet
You need to confirm a failure state before drafting a fix
You need to verify that a fix actually resolves the reported issue

The DAX Lab

Experimental reproduction scripts should ALWAYS be placed in the .dax/lab/ directory. DAX has Implicit Approval to write and execute any code within this directory. This keeps the main src/ tree clean and avoids unnecessary approval prompts.

Workflow

Analyze: Map the reported symptom to the likely codebase modules. Identify relevant dependencies and configurations.
Draft: Write a standalone reproduction script in .dax/lab/ (e.g., .dax/lab/repro_issue_123.ts).
- Use absolute imports or relative paths correctly.
- Ensure the script is self-contained or explicitly imports the required local modules.
Verify Failure: Execute the script using bun run or the appropriate runtime and confirm it fails as expected with the reported symptom.
Minimize: Strip away unrelated logic until the script is the smallest possible "proof of bug".
Link to Fix:
- Once a fix is drafted, run the repro script again.
- Confirm the script now passes (or the failure is resolved).
Cleanup (Optional): If the repro is no longer needed, delete the script from .dax/lab/.

Output Contract

When the reproduction is complete, report:

Reproduction Script: Path to the script in .dax/lab/.
Failure Symptom: The exact error or output that confirms the bug.
Isolation Level: Confirmation that the bug is reproduced in isolation from unrelated logic.
Verification Plan: How you will use this script to verify the upcoming fix.

Tooling

Use write_file to create the script in .dax/lab/.
Use run_shell_command (e.g., bun run .dax/lab/repro.ts) to execute it.
Use enforceRuntimeGuard logic which implicitly allows these actions in the Lab.

이 저장소의 다른 Skills

같은 저장소

agent-config-audit

ShaileshRawat1403/dax

Audit agent configuration surfaces (AGENTS.md, CLAUDE.md, MCP servers, tool registrations, settings, hooks) for consistency, contradictions, and silent overrides. Returns impact-ordered findings tables.

2026-05-165

agentic-loop-audit

ShaileshRawat1403/dax

Audit an agent's main loop for halting conditions, mutation budgets, loop breakers, sensitive-path guards, error recovery, and replayability. Returns impact-ordered findings tables.

2026-05-165

db-migration-review

ShaileshRawat1403/dax

Review a database schema migration for production safety: lock contention, backfill strategy, online vs offline, rollback path, foreign-key timing, replication lag. Returns impact-ordered findings tables.

2026-05-165

deploy-readiness

ShaileshRawat1403/dax

Production readiness audit for a service: health checks, rollback strategy, runbook presence, observability wiring, capacity, dependencies. Returns impact-ordered findings tables.

2026-05-165

eval-suite-audit

ShaileshRawat1403/dax

Audit an AI eval suite for coverage, leakage between datasets, deterministic vs stochastic measurement, ladder correctness, and signal quality. Returns impact-ordered findings tables.

2026-05-165

incident-runbook

ShaileshRawat1403/dax

Generate or audit an incident runbook for an alert/service from code, dashboards, and alert rules. Output is a runbook plus a findings table of gaps. Findings follow the shared output contract.

2026-05-165

Bug Reproduction Skill

Use this skill when a user reports a bug, unexpected behavior, or failing symptom that needs to be isolated and verified before a fix is implemented.

When to Use

User reports a bug or regression

User provides a failing code snippet

You need to confirm a failure state before drafting a fix

You need to verify that a fix actually resolves the reported issue

The DAX Lab

Workflow

Analyze: Map the reported symptom to the likely codebase modules. Identify relevant dependencies and configurations.

Draft: Write a standalone reproduction script in .dax/lab/ (e.g., .dax/lab/repro_issue_123.ts).

Use absolute imports or relative paths correctly.
Ensure the script is self-contained or explicitly imports the required local modules.

Verify Failure: Execute the script using bun run or the appropriate runtime and confirm it fails as expected with the reported symptom.

Minimize: Strip away unrelated logic until the script is the smallest possible "proof of bug".

Link to Fix:

Once a fix is drafted, run the repro script again.
Confirm the script now passes (or the failure is resolved).

Cleanup (Optional): If the repro is no longer needed, delete the script from .dax/lab/.

Output Contract

When the reproduction is complete, report:

Reproduction Script: Path to the script in .dax/lab/.

Failure Symptom: The exact error or output that confirms the bug.

Isolation Level: Confirmation that the bug is reproduced in isolation from unrelated logic.

Verification Plan: How you will use this script to verify the upcoming fix.

Tooling

Use write_file to create the script in .dax/lab/.

Use run_shell_command (e.g., bun run .dax/lab/repro.ts) to execute it.

Use enforceRuntimeGuard logic which implicitly allows these actions in the Lab.

name	skill-repro
description	Reproduce reported bugs or symptoms by creating minimal, verifiable scripts in the DAX Lab.