skills.rest
PequiProject
PequiProjectOFFICIAL
Explore all skills by this author →
GitHub

bug-investigation

Diagnose and repair bugs in the Pequi codebase with structured evidence-driven analysis.

2|Updated Apr 12, 2026
Search Tags:#testing#debugging#investigation#reproduction#bug#arq#pequi
One-click install
npx skills add https://github.com/PequiProject/pequi --skill bug-investigation-pequiproject
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bug-investigation
Source: https://github.com/PequiProject/pequi/tree/main/.agents/skills/bug-investigation
Command: npx skills add https://github.com/PequiProject/pequi --skill bug-investigation-pequiproject

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bug investigation in the Pequi codebase is a structured, evidence-driven process that guides teams from symptom collection through root-cause analysis to a verified fix, ensuring reproducibility and safe handling of sensitive data.

Core Features & Use Cases

  • Systematic symptom collection and reproduction steps to isolate failures.
  • Layered analysis guiding from routers to repositories to infrastructure, with explicit decision points.
  • Verification, documentation, and governance to prevent regression and maintain audit trails.

Quick Start

Trace a full bug investigation workflow: map symptoms, reproduce, isolate layers, analyze root cause, implement a fix, verify, and document.

Frequently Asked Questions about bug-investigation

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

FAQPage Schema
What is the best way to systematically investigate bugs in the Pequi codebase?▼

Systematic bug investigation for Pequi follows an evidence-driven process that maps symptoms, reproduces failures, isolates layers from routers to infrastructure, analyzes root cause, implements a fix, verifies, and documents.

How do I structure bug reproduction steps for dockerized deployments?▼

Structure bug reproduction by collecting symptoms and defining reproducible tests that validate failures across local, staging, and production-like environments for consistent incident reproducibility.

Does Pequi bug investigation work with ARQ workers and dockerized infrastructure?▼

Yes, Pequi bug investigation provides explicit decision points and guidance aligned with ARQ workers and dockerized deployments to safely isolate layers and verify fixes.

Why does root-cause analysis require layered isolation from routers to repositories?▼

Layered isolation is required for root-cause analysis because it guides teams systematically from routers to repositories to infrastructure, establishing explicit decision points to pinpoint exact failure locations.

What are the limitations when handling sensitive data during bug investigation?▼

Investigation limitations are mitigated by enforcing safe handling of sensitive data, requiring verification, documentation, and clear escalation to maintain audit trails and prevent regression.

When do I need to escalate a bug investigation to prevent regression?▼

You need to escalate a bug investigation when verification fails or sensitive data is at risk, using clear escalation paths to maintain audit trails, apply regression checks, and ensure safe handling.

Related Skills

Explore More Software Engineering Skills→
OpenAEC-FoundationOpenAEC-Foundation
7

crosstech-impl-docker-aec-stack

Containerize multi-service AEC stacks with Docker and docker-compose.

Official
Advanced
virajpvirajp
1

verify

Verify deployed environments against product blueprints by checking service health and acceptance criteria.

Community
Advanced
m16khbm16khb

root-cause-tracing

Trace errors backward through the call stack to identify the original trigger.

Community
Advanced
UlanxxUlanxx

canary

Monitor live URLs for console errors, performance regressions, and page failures.

Community
Advanced