القائمة
Use for iterative cosim implementation, debugging, or validation after cosim-gpu-flow-plan. Runs bounded rounds until frozen acceptance criteria and independent review gates pass.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use as the main entry for cosim debugging: gem5 crashes, assertions, hangs, timeouts, address translation faults, non-PASS test results, guest-side waits, and QEMU exits that may be secondary to gem5. Collect logs, preserve live state when needed, route to gem5 model references, and decide the first failing component.
Use when building gem5 or QEMU, checking build provenance, or preserving gem5 incremental builds across worktrees. Delegates to scripts/cosim_build.sh; never hand-roll Docker, scons, or QEMU make commands.
Use when delegating independent code review, design review, or focused bug investigation to an AI reviewer. Provides delegation templates and records reviewer evidence; higher-level review flow remains in cosim-gpu-review or cosim-gpu-rlcr-loop.
Use when the guest disk image needs modification without a full rebuild. Mount with guestmount, add files, systemd services, kernel module config.
Use as the first step for non-trivial cosim testing, debugging, review, or iterative implementation tasks. Do not use for ordinary repository maintenance such as commit splitting, submodule pointer updates, author config, or documentation-only cleanup.
Use when you need to send commands to a running cosim guest. Console pipe interaction, 9p share mount, GPU status check, manual driver load.
| name | cosim-gpu-rlcr-loop |
| description | Use for iterative cosim implementation, debugging, or validation after cosim-gpu-flow-plan. Runs bounded rounds until frozen acceptance criteria and independent review gates pass. |
Run iterative implementation or debugging after cosim-gpu-flow-plan. This
skill owns round state, acceptance criteria, interruption recovery, and the
order of build, test, and review gates. Independent reviewer rules live in
../cosim-gpu-review/references/review/independent-review-contract.md; read
that file before each review gate.
artifacts/<task-slug>/plan.mdcosim-gpu-buildHEAD recorded as the source-edit baseIf there is no plan, run cosim-gpu-flow-plan first.
artifacts/<task-slug>/rlcr/
├── goal-tracker.md
├── round-001-summary.md
├── round-001-review.md
└── final-summary.md
Logs, review briefs, verdicts, and provenance stay in the task workspace under
logs/, reviews/, tests/, or existing artifact paths.
Maintain rlcr/goal-tracker.md:
# Goal Tracker
## Immutable
- Goal:
- Acceptance Criteria:
## Mutable
- Active round:
- Completed:
- Remaining:
- Deferred with reason:
- Decision log:
Do not change the immutable section without explicit human approval.
Repeat until all acceptance criteria pass and the independent review stop rule is satisfied.
Stop rules apply in this order:
plan.md or goal-tracker.mdBLOCKER or MAJOR findingsEach round:
scratch/hypotheses.md before source edits.rlcr/round-NNN-summary.md with commands, artifacts, verdicts,
source base, and remaining work.cosim-gpu-review or
cosim-gpu-codex-review, following the shared review contract.Ask only when the next action would alter the immutable goal, widen source or test scope, use a nonstandard binary, perform a full or cold rebuild, edit a disk image, access external services, or create public artifacts.
After interruption or context compaction, reconstruct state from artifacts:
plan.mdrlcr/goal-tracker.mdevidence.md, commands.md, matrix rows, verdicts, and provenanceIf no live process remains and the artifact lacks a valid verdict or review result, classify the interrupted step as incomplete and resume the next missing step inside the frozen scope. Do not ask whether to continue when the remaining step is already authorized by the plan.
If HEAD moved, record the new value and reclassify pending findings against
current source before editing.
Use the narrowest relevant gate first:
cosim-gpu-buildThe final row must have verdict.json or a [COSIM_VERDICT] line. Do not
override verdict artifacts by interpreting logs manually.
Write rlcr/final-summary.md with: