triage-recent-bugs

Cluster Linear bug tickets by shared chat URL and orchestrate parallel investigations.

43|2|Updated Jan 25, 2024
One-click install
npx skills add https://github.com/glowingkitty/OpenMates --skill triage-recent-bugs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage-recent-bugs
Source: https://github.com/glowingkitty/OpenMates/tree/main/.agents/skills/triage-recent-bugs
Command: npx skills add https://github.com/glowingkitty/OpenMates --skill triage-recent-bugs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triage-recent-bugs eliminates the time sink of manually sorting and debugging multiple user-reported issues by coordinating discovery, root-cause forensics, fixes, and deployment verification across related tickets.

Core Features & Use Cases

  • Recent bug discovery in Linear: Finds bug-labeled issues within a lookback window and guides you to select what to work on.
  • Duplicate clustering by shared chat URL: Detects multiple reports pointing to the same OpenMates share/chat ID so teams investigate together instead of repeating work.
  • Parallel specialist forensics and optional encryption tracing: Runs issue forensics for each selected bug and adds encryption-flow tracing when decryption/key/sync symptoms appear.
  • Test-first fix loop with CI confirmation: Ensures each fix is validated via the existing tests (or prompts you to confirm a minimal repro test), then verifies CI actually ran your tests before closing out.
  • Deploy gate and Linear handoff: Prepares deployment, verifies Vercel readiness for the correct commit, re-verifies on the deployed SHA, and updates Linear with root cause, fix summary, files, SHA, and test evidence.

Quick Start

Ask: triage recent user bugs from the last 2 hours.

Frequently Asked Questions about triage-recent-bugs

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

FAQPage Schema
How do I triage recent user bugs reported in Linear automatically?

To triage recent user bugs reported in Linear, this Skill queries bug-labeled issues within a configurable lookback window in hours, clusters duplicate reports by shared chat URL, and orchestrates parallel investigations to produce fix and verification plans.

What is the best way to group duplicate bug reports pointing to the same chat URL?

The best way to group duplicate bug reports pointing to the same chat URL is to use duplicate clustering, which detects multiple reports pointing to the same OpenMates share/chat ID so teams can investigate together instead of repeating work.

How do I verify CI ran my tests before closing out a bug fix?

To verify CI ran your tests before closing out a bug fix, this Skill enforces a test-first execution loop via run_tests.py and confirms CI actually ran your tests before updating Linear with the closure details.

How does bug triage handle encryption or decryption symptom clusters?

Bug triage handles encryption or decryption symptom clusters by running specialist agent forensics for each selected bug and adding optional encryption-flow tracing when decryption, key, or sync symptoms appear in the reports.

Do I need Vercel to verify deployment readiness for bug fixes?

You do not strictly need Vercel, but this Skill uses a Vercel readiness gate to prepare deployment, verifies the correct commit, re-verifies on the deployed SHA, and updates Linear with root cause and test evidence.

Can I use this for multi-issue daily standups and recurring regressions?

Yes, you can use this for multi-issue daily standups and recurring regressions, as it orchestrates parallel investigations across selected tickets discovered in Linear and tracks session pickup comments for continuous triage.