report-omnigrid-bug

Files structured GitHub issues about OMNIGRID framework bugs to MohamedSayedK/omnigrid.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/MohamedSayedK/omnigrid --skill report-omnigrid-bug-mohamedsayedk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: report-omnigrid-bug
Source: https://github.com/MohamedSayedK/omnigrid/tree/main/assets/core/skills/report-omnigrid-bug
Command: npx skills add https://github.com/MohamedSayedK/omnigrid --skill report-omnigrid-bug-mohamedsayedk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When an OMNIGRID hook misfires, a skill breaks, or a rule produces a wrong result, there is no structured channel to report it. This Skill turns ad-hoc complaints into well-formed GitHub issues filed to the framework's public repository, with privacy scrubbing built in. ## Core Features & Use Cases - Structured intake: Gathers affected component, Given/When/Then behavior, reproduction steps, and severity through one-question-at-a-time conversation. - Privacy scrubbing: Ensures private project names and repo slugs never leak into the public issue body before filing. - Confirmation gate: Renders the full issue from the shipped bug-report template and requires explicit approval before creating it via the GitHub CLI. - Use Case: A hook like stack-gate blocks a correctly exempted skill; you invoke the Skill, answer the guided questions, confirm the draft, and it files a labeled [Bug] issue to MohamedSayedK/omnigrid and returns the URL. ## Quick Start Ask the assistant to report an OMNIGRID framework bug, for example by saying the stack-gate hook blocks a correctly exempted skill, then answer the follow-up questions and confirm the drafted issue.

Frequently Asked Questions about report-omnigrid-bug

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I report a bug in the OMNIGRID framework?▼

Invoke /report-omnigrid-bug with a short description of the framework bug. The Skill asks guided questions about the affected component, reproduction steps, and severity, then files a structured issue to MohamedSayedK/omnigrid after your confirmation.

What is the difference between /bug and /report-omnigrid-bug?▼

/bug files issues into your own project's GitHub repository, while /report-omnigrid-bug targets the OMNIGRID framework itself and files to MohamedSayedK/omnigrid. Use the latter for hook misfires, broken skills, wrong rules, or bad docs.

Does reporting a framework bug expose my private project name?▼

No. The Skill explicitly scrubs private project names, repo slugs, and internal paths before filing, since the target repository is public. Context is described generically, and the rendered body is re-scanned before you confirm.

What information is needed to file a framework bug report?▼

You provide the affected hook, skill, rule, agent, or doc; a Given/When/Then description; minimal reproduction steps; and a severity of blocker, major, or minor. Optional extras include error output and related issue numbers.

What happens if the bug label does not exist on the repository?▼

The Skill drops the --label flag and files the issue without it, noting the omission rather than failing. The issue is still created with the [Bug] title prefix.