Architecture Skill - Debugging & Feature Addition Procedures

Diagnose compiler pipeline failures and coordinate end-to-end feature additions.

Updated May 27, 2026
One-click install
npx skills add https://github.com/ormastes/Spipe --skill architecture-skill-debugging-feature-addition-procedures
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Architecture Skill - Debugging & Feature Addition Procedures
Source: https://github.com/ormastes/Spipe/tree/main/doc/00_llm_process/skill_command/skills/claude/lib/architecture
Command: npx skills add https://github.com/ormastes/Spipe --skill architecture-skill-debugging-feature-addition-procedures

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It provides a structured method to diagnose pipeline issues and safely add new language/compiler features without missing critical integration steps.

Core Features & Use Cases

  • Feature addition checklist across pipeline stages: Guides changes through lexer/parser, desugaring, block parsing, type system, HIR/MIR lowering, backend extensions, and standard library impacts.
  • Debugging workflow for compiler and workspace issues: Covers parse error triage, workspace diagnostics, symbol lookup, and reference tracing.
  • Lean verification alignment: Ensures type inference changes remain consistent by updating corresponding Lean theorems and running verification builds and comparisons.
  • Design checklist with before/after actions: Helps prevent regressions by pairing spec review and dependency impact analysis with test and verification steps.

Quick Start

Ask it to help you add a new DSL feature end-to-end by mapping the required source changes to the lexer/parser, lowering stages, backend, and any Lean verification updates, then validate the result using the specified test and comparison workflow.

Frequently Asked Questions about Architecture Skill - Debugging & Feature Addition Procedures

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

FAQPage Schema
How do I add a new feature to a compiler pipeline end-to-end?

Diagnosing compiler pipeline failures involves structured parse error triage, workspace diagnostics, symbol lookup, and reference tracing to isolate issues across frontend parsing and backend integration. This debugging workflow provides deterministic stage coverage and concrete commands for accurate triage.

How do I update Lean verification theorems for type inference changes?

Updating Lean verification for type inference changes requires modifying corresponding Lean theorems, then running lake build and simple gen-lean compare diffs. This workflow ensures type-system modifications remain consistent and mathematically verified across the compiler pipeline.

What is the best way to prevent regressions when modifying HIR/MIR lowering?

The best way to prevent regressions during HIR/MIR lowering modifications is applying a design checklist that pairs spec review and dependency impact analysis with test and verification steps. This before/after action framework safely guides complex compiler maintenance tasks.

Why does my compiler fail during symbol lookup and reference tracing?

Compiler failures during symbol lookup and reference tracing often stem from misaligned frontend parsing or unresolved dependencies in the workspace. Use targeted debugging workflows for symbol investigation to accurately diagnose and resolve these pipeline reference issues.