agentsclimarketplace
Sign in

Bug evidence to issue

Skill StaryMoon/bug-evidence-to-issue-skill/skills/bug-evidence-to-issue

Package reproduction steps, expected and actual behavior, sanitized logs, screenshots, system details, and optional Git state into a reviewer-ready GitHub issue and evidence manifest. Use when Codex needs to report a bug without leaking tokens, passwords, private paths, authorization headers, or unrelated environment data.From its SKILL.md

Install
npx -y skills add StaryMoon/bug-evidence-to-issue-skill --skill bug-evidence-to-issue

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.8 KB, 317 tokens by cl100k_base, as published. Nobody here has run it

Bug Evidence to Issue

Create a minimal reproducible report, not a data dump. Collect only evidence needed to reproduce the defect, sanitize it before review, and let the user inspect the final issue before posting.

Workflow

  1. Reproduce the bug once with the smallest known steps.
  2. Save relevant logs and screenshots in a task directory.
  3. Build the issue pack:
python3 scripts/build_bug_issue.py \
  --title "CLI exits after loading an empty config" \
  --steps steps.md \
  --expected "The default configuration is created." \
  --actual "The process exits with code 1." \
  --log app.log \
  --screenshot error.png \
  --output output/bug-issue
  1. Review sanitized/ and issue.md line by line. Search for private usernames, hostnames, paths, IDs, and business data that generic redaction cannot identify.
  2. Add repository-specific version and reproduction details.
  3. Ask the user before posting the issue to an external repository.

Quality rules

  • Never collect the full environment or home directory.
  • Redact secrets before copying logs into the output pack.
  • Include exact commands only when they are safe to publish.
  • Distinguish observed behavior from suspected cause.
  • Do not attach screenshots that contain private tabs, notifications, or account data.
  • Preserve original log files outside the public pack when forensic fidelity matters.

See references/redaction-policy.md for covered and uncovered data classes.

What ships with it: 3 files

6.5 KB alongside SKILL.md, 1 of them executable

agents/

references/

scripts/

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.