skills.rest
likec4
likec4OFFICIAL
Explore all skills by this author →
WebsiteGitHub

likec4-issue-repro

Reproduce and verify reported LikeC4 bugs with minimal fixtures and regression tests.

5.6k|377|Updated Mar 24, 2023
Search Tags:#pnpm#regression testing#triage#bug reproduction#Monorepo#LikeC4#gitHub issues
One-click install
npx skills add https://github.com/likec4/likec4 --skill likec4-issue-repro
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: likec4-issue-repro
Source: https://github.com/likec4/likec4/tree/main/.agents/skills/likec4-issue-repro
Command: npx skills add https://github.com/likec4/likec4 --skill likec4-issue-repro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When a bug is reported against LikeC4 on GitHub, maintainers need a fast, disciplined way to confirm whether the issue is real, isolate the failing code area, and turn the reproduction into a lasting regression test instead of ad-hoc debugging.

Core Features & Use Cases

  • Issue triage from GitHub: Pulls live issue data with gh issue view to capture the exact reported behavior before reproducing.
  • Symptom-based routing: Maps symptoms (codegen, project config, DSL parsing, computed views, diagram rendering) to the correct package such as packages/core or packages/language-server.
  • Minimal fixture construction: Builds the smallest likec4.config, specification, model, and views blocks needed to trigger the failure.
  • Use Case: A user reports that likec4 gen produces wrong output. The skill fetches the issue, builds a minimal fixture, runs the focused codegen test, confirms reproduction, and adds a regression test before any fix.

Quick Start

Ask the assistant to check whether GitHub issue 1234 in likec4/likec4 can be reproduced and to build a minimal failing fixture.

Frequently Asked Questions about likec4-issue-repro

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

FAQPage Schema
How do I reproduce a LikeC4 bug from a GitHub issue?▼

Fetch the report with `gh issue view ISSUE --repo likec4/likec4 --comments`, then build a minimal fixture with one config, specification, model, and views block. Run the narrowest pnpm test command for the affected package to confirm the failure.

How do I find which LikeC4 package a bug belongs to?▼

Route by symptom: codegen and exporters map to packages/likec4/src/cli/codegen, project discovery to packages/language-server/src/workspace, DSL parsing to packages/language-server, computed views to packages/core, and rendering to packages/diagram.

Does this workflow require the GitHub CLI?▼

Yes, live issue data is retrieved with `gh issue view` including comments. If reproduction is blocked, the workflow reports the exact blocker and the next command that would prove it.

What should I do after confirming a bug is reproducible?▼

Add or update a focused regression test before changing any implementation code. Then re-run the focused test, followed by package typecheck, dprint check on changed files, and git diff --check.

Why does pnpm fail unexpectedly during reproduction?▼

Check disk space before reinstalling dependencies, as unexpected pnpm failures are often caused by a full disk. The workflow explicitly avoids dependency churn to keep the reproduction environment stable.

Related Skills

Explore More Software Engineering Skills→
dotnetdotnet
14.8k

triage

Classify EF Core issues as bugs or feature requests and assign area labels.

Official
Advanced
summarybotngsummarybotng
2

debug-loop

Execute real commands to test hypotheses and fix software bugs.

Official
Advanced
kdlbskdlbs
562

verify

Run format, typecheck, tests, and lint across monorepo packages.

Official
Intermediate
SocketDevSocketDev
125

rendering-chromium-to-png

Render web pages, local HTML files, and MV3 extension popups to PNG screenshots.

Official
Intermediate