pipeline-summary

Pipeline Summary

Create a GitHub issue documenting bugs encountered during a pipeline run and a PR from the feature branch into the target branch.

Arguments

/autoskillit:pipeline-summary {bug_report_path} {feature_branch} {target_branch} {workspace} [{closing_issue}]

• bug_report_path — Path to the JSON file containing bug metadata
• feature_branch — Name of the branch containing all accumulated fixes
• target_branch — Branch to create the PR against (e.g., "main")
• workspace — Path to the git repository workspace
• closing_issue — (Optional) GitHub issue number whose ## Requirements section should be extracted and embedded in the PR body. When absent or empty, requirements extraction is skipped.

When to Use

• End of a pipeline run with collect_on_branch enabled
• Any pipeline that accumulates fixes on a feature branch and needs a summary

Critical Constraints

NEVER:

• Fail the pipeline if gh is not available or not authenticated — write a local summary instead
• Create empty issues or PRs (skip if no bugs to report)
• Modify any source code — this skill only creates GitHub artifacts and a summary file

ALWAYS:

• Check gh auth status before attempting GitHub operations
• Push the feature branch before creating the PR
• Write a local summary markdown file regardless of GitHub availability
• Output summary_path=<path> for capture by the orchestrator
• If GitHub operations succeed, also output issue_url=<url> and pr_url=<url>

Workflow

Step 1: Parse Arguments

Parse up to five positional arguments from the prompt. The fifth (closing_issue) is optional.

Step 2: Read Bug Report

Read the JSON file at {bug_report_path}. Expected structure:

[
  {
    "step": "string — pipeline step where failure occurred",
    "error": "string — error description",
    "fix": "string — what was done to fix it",
    "iteration": "number — which bugfix iteration"
  }
]

If the file is empty, contains [], or doesn't exist, write a clean-run summary and exit successfully.