skills.rest
pipecrew-ai
pipecrew-aiCOMMUNITY
Explore all skills by this author →
GitHub

troubleshoot

Investigates cross-repo incidents via workspace logs and recent diffs, generating structured reports with enforced read-only operation.

16|2|Updated Jun 17, 2026
Search Tags:#system troubleshooting#incident triage#read-only enforcement#cross-repo investigation#hypothesis-driven analysis
One-click install
npx skills add https://github.com/pipecrew-ai/pipecrew --skill troubleshoot-pipecrew-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: troubleshoot
Source: https://github.com/pipecrew-ai/pipecrew/tree/main/skills/troubleshoot
Command: npx skills add https://github.com/pipecrew-ai/pipecrew --skill troubleshoot-pipecrew-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The troubleshoot Skill addresses the challenge of identifying and diagnosing cross-repo incidents, simplifying the triage and resolution process.

Core Features & Use Cases

  • Cross-Repo Incident Triage: Conducts investigations based on symptoms and optional flags, using workspace logs and recent diffs.
  • Structured Reporting: Generates detailed reports detailing root causes and next steps.
  • Read-Only Enforcement: Ensures agents operate strictly in a read-only manner, enforcing no system changes during the troubleshoot process.
  • Hypothesis-Driven Approach: Uses an OBSERVABILITY routing table for log queries and a hypothesis-approval gate for investigating potential causes.
  • Use Case: If you experience a 500 error on a bulk upload feature, this Skill can analyze the workspace's logs and recent diffs to determine the root cause.

Quick Start

/troubleshoot "bulk upload returns 500" --since=1h

Frequently Asked Questions about troubleshoot

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

FAQPage Schema
How do I investigate cross-repo incidents using workspace logs?▼

To investigate cross-repo incidents, you run hypothesis-driven investigations against workspace logs and recent diffs. This process analyzes symptoms and optional flags to determine the root cause and generate a structured report.

What is hypothesis-driven incident triage and how does it work?▼

Hypothesis-driven incident triage uses an OBSERVABILITY routing table for log queries and a hypothesis-approval gate. It systematically investigates potential causes across repositories to identify the root cause of system issues.

How do I troubleshoot a 500 error using recent diffs and logs?▼

You can troubleshoot a 500 error by running a targeted investigation with a symptom description and time flag. The system analyzes workspace logs and recent diffs to pinpoint the root cause and suggest next steps.

Does read-only enforcement prevent system changes during incident investigation?▼

Yes, read-only enforcement prevents system changes during incident investigation. This ensures agents operate strictly in a non-mutation state, keeping the system stable while troubleshooting workspace issues.

What do I need to set up before running a cross-repo incident investigation?▼

You need an OBSERVABILITY routing table for log queries and the system must be in a non-mutation state. This read-only environment is required to enforce safe operations during the troubleshooting process.

What is the best way to generate structured reports for incident triage?▼

The best way to generate structured incident triage reports is through hypothesis-driven analysis of workspace logs and recent diffs. This approach details root causes and outlines actionable next steps.

Related Skills

Explore More Software Engineering Skills→
rezosndrezosnd

database

Validate PostgreSQL database provisioning and execute environment-aware SQL queries.

Community
Advanced
pcaokhaipcaokhai

investigate

Trace software bugs to root causes through a structured multi-phase investigation workflow.

Community
Advanced
HerxinsasaHerxinsasa
1

log-analysis

Parse and analyze multi-format application and system logs to identify errors and root causes.

Community
Intermediate
tubone24tubone24
1

operations

Implement reliability practices for production systems with CI/CD pipelines and monitoring.

Community
Advanced