diagnose-forge

Diagnose forge container gaps from E2E diagnostics and file improvement proposals.

5|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/8007342/tillandsias --skill diagnose-forge-8007342
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: diagnose-forge
Source: https://github.com/8007342/tillandsias/tree/main/skills/diagnose-forge
Command: npx skills add https://github.com/8007342/tillandsias --skill diagnose-forge-8007342

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Development containers often lack the tools, SDKs, and environment variables needed to build arbitrary projects, forcing users to manually investigate and install missing dependencies. This Skill closes that gap by analyzing E2E diagnostics logs, identifying missing capabilities, and driving a structured proposal-to-implementation workflow for improving the forge container image. ## Core Features & Use Cases - Diagnostics Analysis: Reads raw diagnostics logs and distilled summaries to detect missing env vars, runtimes, SDKs, caches, network access, and shell tools. - Proposal State Machine: Files one proposal per gap and tracks it through proposed, reviewed, approved, implemented, rejected, or stale states. - Guided Implementation: Applies approved changes to the Containerfile and entrypoint script with per-proposal commits and evidence tracking. - Use Case: After an E2E run reveals that Flutter and Rust are missing from the forge image, run this Skill to file proposals for each gap, wait for orchestrator approval, then implement the Containerfile and entrypoint changes with cited diagnostics evidence. ## Quick Start Run the diagnose-forge command to analyze the latest forge diagnostics and file improvement proposals for any detected gaps.

Frequently Asked Questions about diagnose-forge

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

FAQPage Schema
How do I diagnose missing tools in a development container?▼

Run the diagnose-forge command, which reads E2E diagnostics logs and distilled summaries to detect missing env vars, runtimes, SDKs, caches, network access, and shell tools. Each detected gap becomes a separate proposal file for review.

How does the forge improvement proposal workflow work?▼

Each gap is filed as a proposal with status proposed, then moves through reviewed, approved, and implemented states, or is marked rejected or stale. The Skill never self-approves; an orchestrator must approve proposals before implementation begins.

Can diagnose-forge run unattended in an automated loop?▼

Yes, it supports unattended execution via opencode run --command diagnose-forge as well as interactive TUI sessions with /diagnose-forge. In unattended mode it files proposals and waits for orchestrator approval before making changes.

What safety constraints apply to forge container changes?▼

Changes must only add capabilities, never remove them, and every change must cite diagnostics evidence. Proposals cannot request broader host mounts, host credentials, privileged containers, new network egress, or reduced container isolation.

What files does diagnose-forge modify when implementing proposals?▼

It modifies the forge image definition in images/default/Containerfile and the runtime environment setup in images/default/entrypoint-forge-opencode.sh. Each implementation is committed separately with evidence recorded in the proposal frontmatter.