Skip to content
Agentmart
Submit a tool

ci-investigation

Investigate CI/CD failures on PRs using subagents for parallel log analysis.

Skill by agent-rails

IndexedApache-2.0
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/agent-rails-ci-investigation

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Investigate CI/CD failures on PRs using subagents for parallel log analysis. Use when CI fails, build breaks, tests fail in pipeline, or user asks about failing checks. Trigger phrases include "CI failed", "build failed", "pipeline error", "failing checks", "why did CI fail".

Use cases: devops, data

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/ci-investigation

What's inside

Skill name
ci-investigation
Description
Investigate CI/CD failures on PRs using subagents for parallel log analysis. Use when CI fails, build breaks, tests fail in pipeline, or user asks about failing checks. Trigger phrases include "CI failed", "build failed", "pipeline error", "failing checks", "why did CI fail".
License
Apache-2.0
Instructions
30 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

## When to Use

When a user asks about CI failures on a PR or branch.

## Pattern

1. Spawn an `explore` agent for failure analysis:
   ```
   "Investigate CI failures for PR #<number>. Get all failing check logs, 
   identify root causes, and summarize: failing jobs, error messages, root cause."
   ```

2. In parallel, gather PR metadata yourself (title, commits, changed files)

3. Synthesize agent findings with context to determine fix

## When NOT to Use

- Local test failures (use tester agent directly)
- Simple type errors visible in editor
- When CI is passing
- Single-job failures with obvious errors

## Why

- CI logs are verbose and require parsing multiple sources
- Agent investigates all failures in parallel
- Main context stays focused on decision-making, not log parsing

From agent-rails/agentic-fabric, Apache-2.0.

More from agent-rails/agentic-fabric

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Jul 17, 2026 (3 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
Apache-2.0
Repository
github.com/agent-rails/agentic-fabric
First seen
Oct 24, 2026
Last checked
Oct 24, 2026
Source
GitHubgithub-graphql

More from agent-rails

Cite this page

ci-investigation skill. Agent Mart. https://agentmart.dev/skills/agent-rails-ci-investigation (last updated 2026-10-24)