skills.rest
humblemuzzu
humblemuzzuCOMMUNITY
Explore all skills by this author →
Website𝕏@devmuzzammilGitHub

nexus-fix

Automate investigation-to-PR workflows for linear software issues with browser validation.

5|Updated Mar 10, 2026
Search Tags:#workflow#debugging#traceability#pull-request#browser-automation#counterfactual-proof
One-click install
npx skills add https://github.com/humblemuzzu/ghosttyyy --skill nexus-fix
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: nexus-fix
Source: https://github.com/humblemuzzu/ghosttyyy/tree/main/pi-setup/config-skills/nexus-fix
Command: npx skills add https://github.com/humblemuzzu/ghosttyyy --skill nexus-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Structured investigation-to-PR workflow for linear software issues, emphasizing hypothesis-driven debugging with browser validation and counterfactual proof to deliver verifiable fixes.

Core Features & Use Cases

  • Phase-driven workflow from bootstrap to PR with browser validation and evidence collection.
  • Counterfactual proof ensures the bug is reproducible before and after changes, supporting trustworthy releases.
  • Collaborative, auditable process that traces root cause to final PR with documented steps.

Quick Start

Begin with phase 0 to bootstrap the environment, then progress through phases 1–6 to complete an investigation and produce a verified PR.

Frequently Asked Questions about nexus-fix

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

FAQPage Schema
How do I debug a software issue from investigation through to a verified pull request?▼

Debug a software issue to a verified pull request by applying a structured, hypothesis-driven workflow that automates environment setup, code investigation, browser validation, and documented evidence collection to deliver reliable fixes.

What is counterfactual proof in the context of bug investigation and browser automation?▼

Counterfactual proof in bug investigation ensures a bug is reproducible before and after code changes. Using browser automation, it provides verifiable evidence that the fix directly resolves the issue.

Can I use a hypothesis-driven debugging workflow for linear software issues?▼

Yes, a hypothesis-driven debugging workflow applies to linear software issues. It progresses through phases from environment bootstrap to browser-validated fixes, ultimately producing an evidence-backed pull request.

What is the best way to trace a root cause to a final pull request with documented steps?▼

The best way to trace a root cause to a final pull request is using an auditable, phase-driven workflow. It documents each step from initial investigation to browser-validated fixes, ensuring traceability and reliable releases.

Does this debugging workflow support browser automation for validating fixes?▼

Yes, this debugging workflow supports browser automation for validating fixes. It uses browser validation alongside counterfactual proof to ensure the software bug is resolved before submitting the pull request.

Related Skills

Explore More Software Engineering Skills→
sQVesQVe

debug-issue

Diagnose bugs by tracing evidence and generating a BR issue template.

Community
Advanced
GenEducationGenEducation

land-and-deploy

Merge a pull request, wait for CI and deployment, and verify production health with canary checks.

Official
Advanced
burgebjburgebj

ship

Automate testing, code review, pull request creation, and deployment workflows.

Community
Advanced
winsorllcwinsorllc

code-review

Execute linters, static analysis, and security scanners on code.

Community
Intermediate