Agent Skills › likec4/likec4 › likec4-issue-repro

likec4-issue-repro

GitHub

用于复现、诊断和验证 LikeC4 项目 GitHub 问题或用户报告的 Bug。通过构建最小化测试用例并运行特定命令来确认问题，最终提供包含复现结果、失败命令及修复验证的标准化证据报告。

.agents/skills/likec4-issue-repro/SKILL.md likec4/likec4

Trigger Scenarios

用户询问某个 Issue 是否可以复现请求生成最小化复现代码 (minimal repro) 检查 Bug 报告细节将复现过程转化为回归测试

Install

npx skills add likec4/likec4 --skill likec4-issue-repro -g -y

More Options

Non-standard path

npx skills add https://github.com/likec4/likec4/tree/main/.agents/skills/likec4-issue-repro -g -y

Use without installing

npx skills use likec4/likec4@likec4-issue-repro

指定 Agent (Claude Code)

npx skills add likec4/likec4 --skill likec4-issue-repro -a claude-code -g -y

安装 repo 全部 skill

npx skills add likec4/likec4 --all -g -y

预览 repo 内 skill

npx skills add likec4/likec4 --list

SKILL.md

Frontmatter

{
    "name": "likec4-issue-repro",
    "description": "Use when reproducing, diagnosing, or verifying a reported LikeC4 bug from a GitHub issue or user report. Trigger for tasks asking whether an issue can be reproduced, requesting a minimal repro, checking bug reports, or turning a reproduction into a focused regression test."
}

LikeC4 Issue Reproduction

Reproduce with the smallest fixture that exercises the reported behavior, then give a direct yes/no with evidence.

Ground rules

Prefer live GitHub issue data from gh issue view ISSUE --repo likec4/likec4 --comments.
Keep fixtures outside unrelated source changes, usually in a temp directory or a focused test fixture.
Do not churn dependencies. If pnpm fails unexpectedly, check disk space before reinstalling.
If reproduction is blocked, report the exact blocker and the next command that would prove it.

Route the issue

Use the report symptoms to choose the likely code area:

Symptom	Start here
`likec4 gen`, exporters, `--outdir`, generated files	`packages/likec4/src/cli/codegen`
`likec4.config`, project discovery, include paths, excludes	`packages/language-server/src/workspace`
DSL parsing, validation, completions, imports	`packages/language-server`
computed views, predicates, relationships	`packages/core`
diagram rendering, browser behavior, embedded UI	`packages/diagram`, `packages/likec4-spa`, `packages/vite-plugin`

If the route is codegen or project config, also use the corresponding LikeC4 repo skill.

Reproduction workflow

Capture the exact report:

gh issue view ISSUE --repo likec4/likec4 --comments

Build a minimal fixture:

one likec4.config.* if project scope matters
one specification block with only required kinds
one model block with the smallest failing element or relationship shape
one views block only if rendering or codegen needs it

Run the narrowest command that exercises the failure.

Examples:

pnpm --filter @likec4/language-server test -- ProjectsManager.spec.ts
pnpm --filter likec4 test -- codegen
pnpm --filter @likec4/core test -- relationship
pnpm --filter @likec4/diagram test -- path/to/spec

If reproducible, add or update a focused regression test before changing implementation.
Re-run the focused test, then expand only as risk requires:

pnpm --filter PACKAGE test -- SPEC_OR_PATTERN
pnpm --filter PACKAGE typecheck
pnpm exec dprint check CHANGED_FILES
git diff --check

Evidence to report

Use this format:

Reproduced: yes/no.
Fixture: path or short description.
Failing command: exact command and relevant failure.
Fix verification: exact command that passed.
Remaining risk: anything not covered.