Run any Skill in Manus with one click

logs-repro-harness

Stars502

Forks63

UpdatedFebruary 19, 2026 at 07:58

Reduce flaky or environment-dependent failures to a minimal, reproducible script and capture the exact logs and error lines.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

pilinux

pilinux/gorest

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

SKILL.md

readonly

name	logs-repro-harness
description	Reduce flaky or environment-dependent failures to a minimal, reproducible script and capture the exact logs and error lines.
license	MIT
metadata	{"mode":"diagnostics","purpose":"repro"}

Logs Repro Harness

When to Use

An issue is flaky, hard to reproduce locally, or depends on environment configuration.

Responsibilities

Produce the smallest reproducible commands that trigger the failure.
Capture key log lines, stack traces, and environment differences needed to reproduce.
Provide targeted probes to distinguish root-cause hypotheses.

Rules

Never request or reveal secrets.
Use source setTestEnv.sh when environment variables are required.
Prefer go test -run <TestName> <pkg> for focused reproduction.

Output

Minimal repro: 1-3 commands.
Observed output: first actionable error or stack lines.
Hypotheses: 1-3 candidates with next probe commands.

Examples

"Test X passes locally but fails in CI" - compare env vars, capture output diff.
"Intermittent timeout in Redis test" - isolate with CONNTTL tuning and retry logic.

Related Skills

test-runner, fix-suggester, config-loader-helper

References

logs/ directory, setTestEnv.sh, AGENTS.md

More from this repository

same repository

ci-orchestrator

pilinux/gorest

Run a CI-like pipeline locally (format, lint, vet, static-analysis, tests) and summarize per-step results with remediation guidance.

2026-06-24502

linter-runner

pilinux/gorest

Execute repository linters and surface highest-priority issues with minimal, targeted fixes.

2026-06-24502

ast-introspection

pilinux/gorest

Use Go AST-aware analysis to enumerate symbols, extract signatures, and propose mechanically safe refactors (read-only by default).

2026-02-19502

build-run

pilinux/gorest

Build and run the project locally to reproduce compile/runtime issues in a safe, non-production way.

2026-02-19502

code-formatter

pilinux/gorest

Apply repository-standard formatting to minimize diff noise and meet linter expectations.

2026-02-19502

code-navigation

pilinux/gorest

Rapid, focused navigation to locate definitions/usages and map the impact of proposed changes.

2026-02-19502

name	logs-repro-harness
description	Reduce flaky or environment-dependent failures to a minimal, reproducible script and capture the exact logs and error lines.
license	MIT
metadata	{"mode":"diagnostics","purpose":"repro"}

Logs Repro Harness

When to Use

An issue is flaky, hard to reproduce locally, or depends on environment configuration.

Responsibilities

Produce the smallest reproducible commands that trigger the failure.
Capture key log lines, stack traces, and environment differences needed to reproduce.
Provide targeted probes to distinguish root-cause hypotheses.

Rules

Never request or reveal secrets.
Use source setTestEnv.sh when environment variables are required.
Prefer go test -run <TestName> <pkg> for focused reproduction.

Output

Minimal repro: 1-3 commands.
Observed output: first actionable error or stack lines.
Hypotheses: 1-3 candidates with next probe commands.

Examples

"Test X passes locally but fails in CI" - compare env vars, capture output diff.
"Intermittent timeout in Redis test" - isolate with CONNTTL tuning and retry logic.

Related Skills

test-runner, fix-suggester, config-loader-helper

References

logs/ directory, setTestEnv.sh, AGENTS.md