skills.rest
anantham
ananthamCOMMUNITY
Explore all skills by this author →
Website𝕏@adityaarpithaGitHub

investigation-pipeline

Integrate static analysis, reproduction, classification, and archaeology tools for bug investigation workflows.

15|2|Updated Aug 12, 2025
Search Tags:#classification#regression testing#traceability#conflict resolution#bug investigation
One-click install
npx skills add https://github.com/anantham/LexiconForge --skill investigation-pipeline
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: investigation-pipeline
Source: https://github.com/anantham/LexiconForge/tree/main/issues/_meta/proposed-skill
Command: npx skills add https://github.com/anantham/LexiconForge --skill investigation-pipeline

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill streamlines the process of investigating, classifying, and documenting software bugs, reducing debugging time and preventing misdiagnoses.

Core Features & Use Cases

  • Verbatim Claim Recording: Preserves the user's original bug report for accurate reference.
  • Reproduction Verification: Guides users to reproduce bugs reliably with environment setup and evidence collection.
  • Verdict and Classification: Automates determination of bug validity, scope, and location, including ADR consistency.
  • Thematic Analysis: Identifies cross-cutting failure patterns and ties issues to known themes.
  • Regression Test Planning: Tracks and ensures test coverage before closing bugs.
  • Archaeology Tooling: Maps code changes back to user sessions and commits to trace the origin of bugs.
  • Closure Gatekeeping: Enforces rigorous criteria before marking bugs as fixed.

Quick Start

Investigate your bug queue, verify reproductions, classify issues, and plan regression tests from start to finish.

Frequently Asked Questions about investigation-pipeline

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

FAQPage Schema
How do I systematically investigate a software bug from reproduction to closure?▼

Systematic bug investigation integrates static analysis, live reproduction, classification, and archaeology tools to trace origins and improve software reliability. You record verbatim claims, verify reproduction environments, classify issues, and enforce closure gatekeeping criteria.

What is the best way to classify bugs and track failure patterns across a codebase?▼

Classifying bugs and tracking failure patterns involves thematic analysis to identify cross-cutting issues and tie them to known themes. This approach maps code changes back to commits, ensuring ADR consistency and reducing regression risks.

How do I trace the origin of a bug back to a specific commit or code change?▼

Tracing the origin of a bug utilizes archaeology tooling to map code changes back to user sessions and commits. This establishes traceability by comparing historical code states against the reported failure environment.

Can I enforce regression test coverage before closing a fixed bug?▼

Yes, you can enforce regression test coverage through closure gatekeeping. This process tracks and ensures test coverage planning is completed and validated before allowing any bug to be marked as fixed.

Does bug investigation workflow support verifying environment setup and evidence collection?▼

Bug investigation workflow supports reproduction verification by guiding users to reliably reproduce bugs. This includes specific environment setup procedures and systematic evidence collection to validate the verbatim original bug report.

Why does bug misdiagnosis happen and how can classification prevent it?▼

Bug misdiagnosis happens due to incomplete reproduction verification and lack of evidence tracking. Automated verdict and classification prevents this by determining bug validity, scope, and location while checking ADR consistency.

Related Skills

Explore More Software Engineering Skills→
arozumenkoarozumenko
18

reproducing-issues

Convert vague bug reports into repeatable reproduction steps with evidence and a verdict.

Community
Intermediate
Sheldon-92Sheldon-92
3

Testing

Execute test suites and report failures with coverage metrics.

Community
Intermediate
rtfpessoartfpessoa

atcommit

Analyze file dependencies to organize staged changes into atomic Git commits.

Community
Advanced
Luis-ERPLuis-ERP

bug-phase-classification

Classify bugs by detected and injected phases in bug logs.

Community
Basic