Skill guide

Repository debugging

Find the cause of a concrete failure or unexpected behavior, then make a repair when requested.

Start from a reproducible symptom, inspect the relevant execution path, and test supported explanations. The result separates the observed failure, its demonstrated cause, and the evidence for any authorized fix.

Package version 0.1.0-beta.7

Included with Faye Coding Assistant

See an example View package

When to use

Use this for a failing command, incorrect runtime result, regression, or unexpectedly slow operation.

What to provide

The expected and actual behavior, error output, and steps to reproduce.
The affected repository or environment and whether you want diagnosis only or diagnosis with repair.

Expected results

A supported root-cause explanation or a clearly bounded remaining uncertainty.
When repair is authorized, a targeted fix and verification of the failure path.

Example requests

Try this request

Codex

$repository-debugging Diagnose and fix why the site build rejects a valid related-skill link. Reproduce the failure, identify the resolution error, and verify the correction.

Grok

/repository-debugging Diagnose and fix why the site build rejects a valid related-skill link. Reproduce the failure, identify the resolution error, and verify the correction.

Antigravity

/repository-debugging Diagnose and fix why the site build rejects a valid related-skill link. Reproduce the failure, identify the resolution error, and verify the correction.

Requirements and limits

Before you start

A concrete symptom and enough access or evidence to investigate it.
Explicit repair authorization before changing source.

Scope and limitations

Diagnosis alone stays read-only.
A suite-wide assessment of cost or flakiness is a different task from diagnosing one observed failure.
Unconfirmed hypotheses must not be presented as established causes.

Technical source

The hosted file belongs to the package version shown on this page.

plugins/faye-coding-assistant/skills/repository-debugging

Open source file

Supporting material

Supporting files

Implementation assistantDefines a write-capable role for explicitly authorized, bounded implementation or repair.Read-only coding analystDefines a bounded analysis role for exploration, diagnosis, review, planning, suite assessment, and handoff.