---
name: blockscout-gh-issue-publish
description: "Publish a drafted GitHub issue from tmp/gh-issues/ by running the repository's gh CLI publish script and relaying the resulting URL or remediation."
license: "NOASSERTION"
disable-model-invocation: true
metadata:
  decimalai-skill-id: "169246af-319a-42e4-b33c-d821f17dc3d4"
  decimalai-version-id: "20d306cc-e4e0-43c5-9921-266d32493a78"
  decimalai-version: "2"
  decimalai-body-sha256: "3859187a82d40f77dc296ed69dc2b41b7f47a70794e7748ab5b5dd2993d935fe"
  decimalai-name: "blockscout/gh-issue-publish"
  decimalai-format: "1"
  decimalai-invocation: "user"
  decimalai-category: "productivity"
  decimalai-source: "https://app.decimal.ai/s/blockscout-gh-issue-publish@2/SKILL.md"
---
# GitHub Issue Publish Skill

Use this skill when the user wants to publish a previously drafted GitHub issue markdown file with the `gh` CLI.

## Workflow

Follow the canonical workflow in `../../../.memory-bank/workflows/gh-issue-publish.md`.

## Required Guardrails

- Determine the issue file path from the user input or the most recent `tmp/gh-issues/*.md` path in the conversation. If no path can be determined, ask for one.
- Use the checked-in script at `../../../.memory-bank/workflows/scripts/gh-issue-publish.sh` rather than recreating its logic inline.
- Relay the script result exactly at the semantic level:
  - On success, report the issue URL and applied label.
  - On failure, report the error and the documented remediation.
- Do not edit the issue markdown unless the user asks for content changes.

## Minimal Starting Reads

Start with:

- `../../../.memory-bank/workflows/gh-issue-publish.md`
- `../../../.memory-bank/workflows/scripts/gh-issue-publish.sh`

Then run the script with the resolved issue path and report the outcome.