pos-debug

OK, I've got it. I'll do that.

8|Updated Mar 17, 2026

Search Tags:#testing #debugging #verification #reproduce #hypothesize #bug-pattern-memory

Ready to run

npx skills add https://github.com/ShaheerKhawaja/ProductionOS --skill pos-debug

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pos-debug
Source: https://github.com/ShaheerKhawaja/ProductionOS/tree/main/skills/pos-debug
Command: npx skills add https://github.com/ShaheerKhawaja/ProductionOS --skill pos-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debugging complex failures often requires capturing context, patterns, and outcomes to avoid repeating mistakes. This Skill automates reproducing bugs, forming hypotheses, running tests, and applying fixes while accumulating a memory of recurring patterns.

Core Features & Use Cases

Reproduce failures across environments to establish a reliable baseline.
Hypothesize root causes using historical bug-pattern memory.
Apply minimal fixes and verify regressions using stored evaluation data.
Use Case: When a recurring bug in a component surfaces, pos-debug guides you from reproduction to verification with learning from past incidents.

Quick Start

Run the pos-debug skill with an action and a target to start diagnosing, fixing, or verifying a bug.

Frequently Asked Questions about pos-debug

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

FAQPage Schema

How do I debug recurring software bugs by reproducing failures and hypothesizing root causes?▼

Debug recurring bugs by reproducing failures to establish a baseline, hypothesizing root causes using historical bug-pattern memory, and validating minimal fixes against regressions. This approach automates the diagnosis cycle while accumulating memory of recurring patterns to accelerate future resolution.

What is bug-pattern memory and how does it help fix recurring component failures?▼

Bug-pattern memory is a local domain store that captures debugging context, patterns, and outcomes from past incidents. It helps fix recurring component failures by leveraging historical data to form root cause hypotheses faster, avoiding repeated mistakes during the debugging workflow.

How do I verify bug fixes and prevent regressions using stored evaluation data?▼

Verify bug fixes and prevent regressions by applying minimal fixes and validating them against stored evaluation data. The process uses rubric-driven evaluation for each debugging action, ensuring fixes are confirmed through automated testing before resolution.

Do I need a local domain memory store to use memory-driven debugging workflows?▼

Yes, memory-driven debugging workflows require a local domain memory store at ~/.productionos/domains/pos-debug/. This store accumulates context and patterns from recurring bugs, enabling the system to hypothesize root causes based on past incidents and accelerate resolution.

What's the best way to diagnose complex failures across different environments?▼

The best way to diagnose complex failures is to reproduce them across environments to establish a reliable baseline, then hypothesize root causes using historical bug-pattern memory. This structured approach guides you from reproduction to verification with learning from past incidents.

Why does my debugging workflow keep repeating the same mistakes when fixing recurring bugs?▼

Debugging workflows repeat mistakes when they fail to capture context, patterns, and outcomes from past incidents. Using bug-pattern memory automates the accumulation of this debugging history, allowing you to hypothesize root causes based on recurring patterns rather than starting fresh each time.