brainstorm-agent-runs

Diagnose GitHub Actions workflow runs for a Pull Request and generate an Ishikawa diagram.

3|1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/Cogni-AI-OU/cogni-ai-agent-skills --skill brainstorm-agent-runs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: brainstorm-agent-runs
Source: https://github.com/Cogni-AI-OU/cogni-ai-agent-skills/tree/main/brainstorm-agent-runs
Command: npx skills add https://github.com/Cogni-AI-OU/cogni-ai-agent-skills --skill brainstorm-agent-runs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you determine what happened to agentic CI/CD runs triggered by a specific Pull Request, including success/failure signals and missing context, even when results are not visible through standard PR checks alone.

Core Features & Use Cases

  • Pull Request–scoped run discovery: Finds all relevant “Cogni AI Agent” workflow runs by matching the PR head branch name or PR title via the GitHub Actions API.
  • Failure insight extraction: Identifies likely causes such as missing facts and incomplete execution paths before diving into full logs.
  • Structured visualization: Produces an Ishikawa-style diagram to summarize status, challenges, and next steps for the PR.

Quick Start

Ask the AI to brainstorm and generate a structured analysis of the agentic CI/CD runs associated with Pull Request <pr_number> so you can see what succeeded, what failed, and what facts are missing.

Frequently Asked Questions about brainstorm-agent-runs

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

FAQPage Schema
How do I diagnose GitHub Actions agent runs that are missing from standard PR checks?▼

Diagnose CI agent runs by querying the GitHub Actions API filtered by your PR branch name or title to locate manual workflow triggers, then synthesizing the execution outcomes into a structured Ishikawa diagram for failure insight.

What is the best way to visualize CI/CD execution blockers for a Pull Request?▼

Visualize CI/CD blockers by generating an Ishikawa diagram that summarizes agentic workflow status, identifies likely failure causes like missing facts, and outlines next steps without prematurely downloading full execution logs.

How do I find GitHub Actions workflow runs tied to a specific PR branch?▼

Find workflow runs by querying the GitHub Actions API using the PR head branch name or PR title as the filter to discover all relevant triggered agent execution paths tied to that specific Pull Request.

Why are my manually triggered agent runs not showing up in standard PR checks?▼

Standard PR checks omit manually triggered agent workflows because they only track automated status checks, requiring a GitHub API query filtered by branch name or PR title to discover these hidden CI/CD runs and their execution results.

Can I extract failure insights from CI agent runs without downloading full GitHub Actions logs?▼

Extract failure insights by analyzing GitHub Actions workflow run metadata filtered by PR title or branch to identify missing facts and incomplete execution paths, producing a structured Ishikawa visualization before reviewing full logs.

Does this CI agent run analysis work with any GitHub Actions workflow?▼

This analysis applies to PR-driven agent workflows specifically targeting the Cogni AI Agent workflow runs, locating relevant GitHub Actions executions by matching the PR head branch name or PR title via the API.