skills.rest
Open-Curiosity
Open-CuriosityOFFICIAL
Explore all skills by this author →
WebsiteGitHub

gini-bug-report

Submit consent-based Gini crash reports to GitHub issues.

1.7k|523|Updated May 5, 2026
Search Tags:#debugging#GitHub#bug reporting#crash reporting#consent-based
One-click install
npx skills add https://github.com/Open-Curiosity/gini-agent --skill gini-bug-report
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gini-bug-report
Source: https://github.com/Open-Curiosity/gini-agent/tree/main/skills/dev/gini-bug-report
Command: npx skills add https://github.com/Open-Curiosity/gini-agent --skill gini-bug-report

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, git, jq, and includes scripts (resource) components.

What problem does it solve?

This Skill simplifies the process of reporting locally-captured Gini crash reports to GitHub, with explicit user consent and automated handling of duplicates.

Core Features & Use Cases

  • Consent-Based Reporting: Only files crash reports after obtaining explicit user consent.
  • Automated Duplication Handling: Prevents duplicate issues by checking for existing open issues with the same fingerprint.
  • Integration with GitHub: Leverages the github-issues skill to create and manage GitHub issues.
  • Use Case: Upon a restart of the Gini instance, if a crash has occurred, this skill can automatically ask the user whether to report the crash, summarize the details, and upon consent, file it on GitHub.

Quick Start

On restart, when Gini prompts if you would like to report a crash, respond 'yes' and let it file the report on GitHub.

Frequently Asked Questions about gini-bug-report

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

FAQPage Schema
How do I report Gini crash reports as GitHub issues?▼

Report Gini crash reports as GitHub issues by using a consent-based skill that summarizes crash details and files them directly on GitHub upon explicit user approval. It integrates with the github-issues skill to manage the submission.

How does automated duplicate handling work for GitHub crash reports?▼

Automated duplicate handling for crash reports works by checking existing open GitHub issues for identical fingerprints before submission. If a matching issue is found, the skill prevents the creation of a duplicate report.

Do I need the GitHub CLI to submit Gini crash reports?▼

Yes, you need the GitHub CLI (gh) to submit Gini crash reports. The skill requires gh, git, and jq dependencies to authenticate, manage Git operations, and interface with GitHub for issue creation.

Can I automatically file crash reports on GitHub without user consent?▼

No, you cannot automatically file crash reports without user consent. The skill enforces consent-based reporting, meaning it only creates GitHub issues after explicitly asking the user and receiving a 'yes' response.

What is the best way to debug a Gini instance after a crash?▼

The best way to debug a Gini instance after a crash is to capture the local crash report and submit it to GitHub. Upon instance restart, the skill prompts you to report the crash details for tracking.

Related Skills

Explore More Software Engineering Skills→
Quill-AgentQuill-Agent
3

github-auth

Automate GitHub authentication setup using HTTPS tokens or SSH keys.

Community
Intermediate
11547613341154761334

source-command-dedupe

Detects duplicate GitHub issues by querying issue summaries and filtering false positives.

Community
Intermediate
gitkrakengitkraken
9.9k

create-issue

Create GitHub issues from uncommitted changes or commits and update CHANGELOG.

Official
Advanced
ThalfmanThalfman

qa

Create GitHub issues from conversation-based QA bug reports.

Community
Intermediate