gh-issue-bug

Draft a GitHub bug report from the current conversation, save it under tmp/gh-issues/, and follow the repository's canonical bug-report workflow.

Jump to install

Repository: blockscout/blockscout-rs
Last source activity: April 13, 2026 at 20:05
Detected SKILL.md language: English
Stars: 231
Forks: 205

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

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.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/blockscout/blockscout-rs --skill gh-issue-bug

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

2 files

SKILL.md

Source instructions · Read-only preview

name: gh-issue-bug
description: Draft a GitHub bug report from the current conversation, save it under tmp/gh-issues/, and follow the repository's canonical bug-report workflow.

# GitHub Bug Issue Skill Use this skill when the user wants a GitHub issue drafted for a bug, failure, regression, or other broken behavior. ## Workflow Follow the canonical workflow in `../../../.memory-bank/workflows/gh-issue-bug.md`. ## Required Guardrails - Use this skill only for bugs and incorrect behavior, not feature requests or improvements. - Draft the issue from the conversation and any verified local context needed to make it accurate. - If the conversation does not contain enough information for reproduction steps, expected behavior, actual behavior, root cause, and suggested fix, ask for the missing details before writing the file. - Keep the suggested fix high-level. Do not include code snippets, file lists, or implementation plans. - Save the issue to `tmp/gh-issues/YYMMDD-<short-issue-name>.md` and report the full path after creation. ## Minimal Starting Reads Start with: - `../../../.memory-bank/workflows/gh-issue-bug.md` Then read only the relevant code, tests, `.memory-bank/` context, and conversation details needed to draft an accurate bug report.

View on GitHub

Back to search Back to installation

research-scope

Investigate the intended scope of a codebase topic through discussion with a human, propose a research-note outline, and only create a .memory-bank/research file after explicit human confirmation.

2026-08-25

implementation-plan

Turn an approved task analysis and selected solution into a technical design and coding-ready handoff under `tmp/tasks/<task-name>/`, with explicit human confirmation before the coding task is written.

2026-08-10

pr-description

Draft or refresh a reviewer-facing Markdown PR description from `tmp/tasks/<task-name>/` and the current implementation snapshot, covering functional scope, API/config, migration, testing, and follow-ups.

2026-08-10

View all from this repository

gh-issue-bug

Source facts

Install options

Review the source files

More from this repository

More from this repository