Where are the issues reported?

Issues are specifically created in the rnagrodzki/sdlc-marketplace repository to help improve the toolset for all users.

What information is included in the error report?

The report captures the failing skill, the specific step and operation that failed, full error details, and diagnostic hints for developers.

Is user consent required before posting?

Yes, the skill utilizes a strict two-gate consent flow to ensure you approve the report and its contents before anything is sent to GitHub.

Can I invoke this skill manually?

No, this is an internal utility designed to be triggered automatically by other skills when they encounter unrecoverable errors.

Does it require the GitHub CLI?

Yes, this skill requires the GitHub CLI (gh) to be installed and authenticated to create issues in the repository.

SDLC Error Reporter

Name: SDLC Error Reporter
Author: rnagrodzki

byrnagrodzki

0•

Developer Tools

Automates the reporting of technical failures and script crashes directly to GitHub issues with full diagnostic context.

The SDLC Error Reporter is a specialized internal utility designed to enhance the reliability of the SDLC marketplace ecosystem by providing a standardized error-tracking mechanism. When a compatible skill encounters an unrecoverable error—such as a build failure, API timeout, or CLI crash—this tool orchestrates the collection of critical metadata, verifies environment readiness, and facilitates a secure two-gate user consent process. By automating the assembly of detailed bug reports via the GitHub CLI, it ensures that developers receive the exact context needed to resolve issues without requiring the user to manually document technical logs.

Key Features

01Two-gate user consent flow for privacy and data security

020 GitHub stars

03Comprehensive diagnostic capture including exit codes and HTTP status

04Automated GitHub issue creation via gh CLI integration

05Pre-flight verification of GitHub authentication and environment

06Standardized reporting using the ToolingError template

Use Cases

01Standardizing bug reports for internal plugin development

02Reporting persistent API failures during automated SDLC tasks

03Documenting build failures after exhaustive retry attempts

Key Features

01Two-gate user consent flow for privacy and data security

020 GitHub stars

03Comprehensive diagnostic capture including exit codes and HTTP status

04Automated GitHub issue creation via gh CLI integration

05Pre-flight verification of GitHub authentication and environment

06Standardized reporting using the ToolingError template

Use Cases

01Standardizing bug reports for internal plugin development

02Reporting persistent API failures during automated SDLC tasks

03Documenting build failures after exhaustive retry attempts