Run the full end-to-end compiler test suite for the swpp202601-team03 project inside the pre-baked CI Docker image (`ghcr.io/dennis0405/swpp202601-team03-ci:latest`). Invoke when the user runs `/E2E-TEST` or asks to "run E2E tests / 전체 테스트 / 컨테이너에서 빌드+테스트". The skill checks for the image (pulls it if missing), bind-mounts the local repo into a clean container, and runs `ci/scripts/1-build-compiler.sh` through `5-interpreter.sh` in order.
Add LLVM-IR unit tests for a transform pass in this team compiler under `test/unit/<PassName>/`. Triggers on `/add-unit-test` or any request to "add unit tests / 유닛 테스트 추가 / 테스트 작성" for a pass in this repo. Enforces the team's mandatory rule: **at least 3 tests, and at least one must be a real-IR snippet from `swpp202601-benchmarks/<bench>/src/<bench>.ll` where the pass actually fires**, with a comment showing the approximate TM cost delta (before/after) so both correctness and effectiveness are visible at the unit-test layer. Also drafts the matching cost analysis line for the PR description.
Run a SWPP benchmark through the log-enabled interpreter and analyze cost breakdown. Use when asked to profile cost, debug performance, or understand where execution cost accumulates in a benchmark. Invoke as `/bench-cost [bench_name] [input_number]` — e.g. `/bench-cost matmul2 3`. With no args, runs all benchmarks without log analysis.
Rules, conventions, and grading criteria for the SWPP 2026 Spring team compiler project. Use this skill whenever the user is working inside the `swpp202601-teamNN` team repository — writing code, opening or reviewing a pull request, preparing a sprint document, planning an optimization, or asking "what's the rule for X?". Triggers on any mention of the SWPP project, sprints (Sprint 0/1/2/3), the team compiler, PR grading, the target machine / imaginary ISA, the interpreter, benchmarks, the CI image, LLVM passes for this project, Alive2 for this project, or any file under `.clang-format`, `compile.sh`, or CMakeLists.txt in the context of this project. Use it even if the user does not explicitly ask — these rules govern grading, so aligning with them matters on every change.