error-report-sdlc

Draft GitHub issues for SDLC errors using the ToolingError.md template.

6|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/rnagrodzki/sdlc-marketplace --skill error-report-sdlc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: error-report-sdlc
Source: https://github.com/rnagrodzki/sdlc-marketplace/tree/main/plugins/sdlc-utilities/skills/error-report-sdlc
Command: npx skills add https://github.com/rnagrodzki/sdlc-marketplace --skill error-report-sdlc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This procedure standardizes how actionable SDLC errors are captured and transformed into GitHub issues, ensuring full context is preserved for efficient triage and remediation.

Core Features & Use Cases

  • Internal error-handling flow: invoked by other SDLC skills after an error to draft a GitHub issue with complete context.
  • Template-based reporting: uses the ToolingError.md template to ensure consistent fields (skill, step, operation, timestamp, error details, environment).
  • Automated creation: leverages the gh CLI to create the issue with appropriate labels and returns control to the calling skill.

Quick Start

Trigger this skill from an error handler to draft and file a GitHub issue in rnagrodzki/sdlc-marketplace with full context.

Frequently Asked Questions about error-report-sdlc

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

FAQPage Schema
How do I automate GitHub issue creation for SDLC errors like build failures or CLI crashes?

To automate GitHub issue creation for SDLC errors, this skill captures full context from script crashes, persistent API errors, or build failures after retries and drafts a reproducible issue using the gh CLI. It applies appropriate labels and files the issue automatically.

What is the best way to standardize error reporting for internal tooling and software development lifecycle failures?

Standardizing error reporting for internal tooling involves using a structured template like ToolingError.md to capture consistent fields such as skill, step, operation, timestamp, error details, and environment. This ensures full context is preserved for efficient triage and remediation.

Do I need the GitHub CLI installed to automatically file issues for build failures?

Yes, you need the GitHub CLI installed. The skill verifies that the gh CLI is available before assembling metadata, applying labels, and creating the issue in the designated GitHub repository to ensure automated error reporting succeeds.

How does template-based error triage work for actionable SDLC errors?

Template-based error triage for actionable SDLC errors works by assembling captured context into a standardized ToolingError.md template. This ensures consistent fields like operation, timestamp, and environment are recorded, enabling efficient and reproducible issue remediation.

Can I use this automated error reporting skill with my existing SDLC automation workflow?

You can integrate this automated error reporting skill into existing SDLC automation workflows by invoking it from an error handler. After an actionable error occurs, it drafts and files the GitHub issue, then returns control directly to the calling skill.

What types of SDLC errors are considered actionable for automated GitHub issue creation?

Actionable SDLC errors for automated GitHub issue creation include script crashes, CLI failures, persistent API errors, and build failures that persist after retries. These errors trigger the skill to capture full context and generate a reproducible issue.