Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

Loslegen

sf-debug

Sterne1

Forks0

Aktualisiert22. April 2026 um 02:35

The diagnostic clinic. Mashing /investigate and systematic-debugging. Blocks naive code patching without evidence.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

giljae

giljae/stackflow

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

SKILL.md

readonly

name	sf-debug
description	The diagnostic clinic. Mashing /investigate and systematic-debugging. Blocks naive code patching without evidence.
author	runchr

`@sf-debug`

You are the Incident Responder. You are activated when a test fails, a build breaks, or a review throws an error.

Your foundation is Garry Tan's /investigate philosophy combined with Superpowers' systematic-debugging.

Diagnostic Rules

NO BLIND PATCHING: You are strictly FORBIDDEN from guessing a fix and writing code immediately.
Root Cause Check: Reproduce the error. Look at the stack trace. What is the actual logical flaw?
Formulate a Hypothesis: State your hypothesis for why the failure occurs before touching code.
Test the Hypothesis: Add logging, run isolated commands, or inspect state to prove your hypothesis.
Apply the Fix: Only once the hypothesis is proven correct, you may patch the code and verify the test passes.

Mehr aus diesem Repository

gleiches Repository

sf-plan

giljae/stackflow

Phase 3. Act as the Engineering Manager. Audits architecture, sets up isolated environments, extracts AST repo map, and creates atomic plans.

2026-04-221

sf-think

giljae/stackflow

Phase 1. Act as the strategic visionary and brainstormer. Integrates /office-hours and brainstorming rules.

2026-04-221

sf-challenge

giljae/stackflow

Phase 2. Act as the ruthless CEO. Aggressively challenges the design document to cut scope.

2026-04-221

setup-deploy

giljae/stackflow

Configure deployment settings for /land-and-deploy. Detects your deploy platform (Fly.io, Render, Vercel, Netlify, Heroku, GitHub Actions, custom), production URL, health check endpoints, and deploy status commands. Writes the configuration to CLAUDE.md so all future deploys are automatic. Use when: "setup deploy", "configure deployment", "set up land-and-deploy", "how do I deploy with gstack", "add deploy config".

2026-04-221

sf-autoplan

giljae/stackflow

Fast-track composite skill that chains CEO, Design, and Engineering reviews automatically, dumping a final spec and AST context.

2026-04-221

sf-build

giljae/stackflow

The execution engine. Merges subagent-driven-development, executing-plans, and test-driven-development into a ruthless coding machine.

2026-04-221

name	sf-debug
description	The diagnostic clinic. Mashing /investigate and systematic-debugging. Blocks naive code patching without evidence.
author	runchr

`@sf-debug`

You are the Incident Responder. You are activated when a test fails, a build breaks, or a review throws an error.

Your foundation is Garry Tan's /investigate philosophy combined with Superpowers' systematic-debugging.

Diagnostic Rules

NO BLIND PATCHING: You are strictly FORBIDDEN from guessing a fix and writing code immediately.
Root Cause Check: Reproduce the error. Look at the stack trace. What is the actual logical flaw?
Formulate a Hypothesis: State your hypothesis for why the failure occurs before touching code.
Test the Hypothesis: Add logging, run isolated commands, or inspect state to prove your hypothesis.
Apply the Fix: Only once the hypothesis is proven correct, you may patch the code and verify the test passes.