Skip to content

amazon-science/ammo / ai_cli_session/.codex/skills/ammo

Profile and optimize GPU kernels for vLLM inference on NVIDIA GPUs. Use when targeting a specific model, hardware, dtype, parallelism, and workload to improve latency.

FileKindSize
RUNTIME.mdmarkdown4.9 KB
SKILL.mdskill md18.5 KB
agents/ammo-auditor.mdmarkdown9.1 KB
agents/ammo-champion.mdmarkdown9.6 KB
agents/ammo-delegate.mdmarkdown3.2 KB
agents/ammo-implementer.mdmarkdown13.8 KB
agents/ammo-investigator.mdmarkdown4.0 KB
agents/ammo-report.mdmarkdown2.9 KB
agents/ammo-researcher.mdmarkdown10.3 KB
agents/ammo-resolver.mdmarkdown4.4 KB
agents/ammo-transcript-monitor.mdmarkdown7.8 KB
agents/openai.yamlexecutablescript313 B
data/ATTRIBUTION.mdmarkdown1.4 KB
data/gsm8k_full.jsonexecutablescript735.5 KB
data/gsm8k_subset.jsonexecutablescript116.8 KB
eval/EVAL-SKILL.mdexecutablescript21.8 KB
eval/agents/transcript_grader.mdexecutablescript18.0 KB
eval/causal/__init__.pyexecutablescript137 B
eval/causal/agents/causal_analyzer.mdexecutablescript10.5 KB
eval/causal/build_dag.pyexecutablescript21.6 KB
eval/causal/diff_versions.pyexecutablescript38.5 KB
eval/causal/extract_events.pyexecutablescript36.3 KB
eval/causal/generate_postmortem.pyexecutablescript17.0 KB
eval/causal/score_nodes.pyexecutablescript21.5 KB
eval/causal/templates/narrative_template.mdexecutablescript472 B
eval/causal/templates/viz_template.htmlexecutablescript9.5 KB
eval/causal/tests/__init__.pyexecutablescript151 B
eval/causal/tests/conftest.pyexecutablescript448 B
eval/causal/tests/fixtures/sample_session.jsonlexecutablescript10.4 KB
eval/causal/tests/fixtures/sample_session_data.jsonexecutablescript3.4 KB
eval/causal/tests/fixtures/sample_snapshot.jsonexecutablescript2.5 KB
eval/causal/tests/test_build_dag.pyexecutablescript2.7 KB
eval/causal/tests/test_diff_versions.pyexecutablescript13.5 KB
eval/causal/tests/test_extract_events.pyexecutablescript3.7 KB
eval/causal/tests/test_generate_postmortem.pyexecutablescript3.1 KB
eval/causal/tests/test_score_nodes.pyexecutablescript3.3 KB
eval/scripts/aggregate_versions.pyexecutablescript15.2 KB
eval/scripts/archive_run.pyexecutablescript9.1 KB
eval/scripts/codex_session.pyexecutablescript10.6 KB
eval/scripts/generate_dashboard.pyexecutablescript5.3 KB
eval/scripts/parse_artifacts.pyexecutablescript48.1 KB
eval/scripts/parse_session_logs.pyexecutablescript51.3 KB
eval/scripts/rescore_archived.pyexecutablescript5.5 KB
eval/scripts/score_campaign.pyexecutablescript43.8 KB
eval/scripts/snapshot_changes.pyexecutablescript11.1 KB
eval/scripts/verify_citations.pyexecutablescript8.8 KB
eval/tests/test_dashboard_bugs.pyexecutablescript8.8 KB
eval/tests/test_parse_session_logs.pyexecutablescript3.9 KB
eval/tests/test_parse_session_logs_round_inference.pyexecutablescript11.0 KB
eval/tests/test_score_campaign_diluted.pyexecutablescript9.4 KB
eval/viewer/dashboard_template.htmlexecutablescript15.1 KB
instrumentation/sitecustomize.pyexecutablescript3.6 KB
orchestration/audit-protocol.mdmarkdown9.3 KB
orchestration/debate-protocol.mdmarkdown11.2 KB
orchestration/integration-logic.mdmarkdown10.3 KB
orchestration/parallel-tracks.mdmarkdown8.9 KB
references/artifact-layout.mdexecutablescript22.4 KB
references/audit-invariants.mdmarkdown10.6 KB
references/champion-common-patterns.mdmarkdown3.4 KB
references/crossover-probing.mdexecutablescript4.7 KB
references/cudagraph-safety.mdmarkdown2.7 KB
references/debate-rules.mdmarkdown4.7 KB
references/debate-scoring-rubric.mdexecutablescript16.7 KB
references/e2e-delta-math.mdexecutablescript17.9 KB
references/e2e-latency-guide.mdexecutablescript9.6 KB
references/fusion-feasibility-heuristics.mdmarkdown5.6 KB
references/gpu-pool.mdexecutablescript5.4 KB
references/impl-track-rules.mdexecutablescript13.8 KB
references/nsys-profiling-guide.mdmarkdown9.8 KB
references/optimization-categories.mdexecutablescript11.0 KB
references/shutdown-protocol.mdexecutablescript3.1 KB
references/technology-selection.mdmarkdown5.0 KB
references/torch-compile-contract.mdmarkdown13.8 KB
references/validation-defaults.mdexecutablescript34.2 KB
references/workload-invocation.mdexecutablescript4.9 KB
references/writing-style.mdexecutablescript6.9 KB
scripts/ammo_state.pyexecutablescript142.0 KB
scripts/artifact_layout.jsonconfig16.3 KB
scripts/check_projection_accuracy.pyexecutablescript11.7 KB
scripts/create_evidence_template.pyexecutablescript9.7 KB
scripts/create_worktree_with_build.shexecutablescript10.2 KB
scripts/generate_validation_report.pyexecutablescript35.7 KB
scripts/gpu_reservation.pyexecutablescript27.1 KB
scripts/hook_cmd_classify.pyscript13.3 KB
scripts/mine_trace.pyscript29.4 KB
scripts/monitor_queue_ack.pyexecutablescript6.1 KB
scripts/ncu_sanity.shexecutablescript5.2 KB
scripts/ncu_sanity_driver.pyexecutablescript8.5 KB
scripts/new_target.pyexecutablescript22.0 KB
scripts/preflight_vllm_api.pyexecutablescript12.3 KB
scripts/reconcile_track_state.pyexecutablescript15.8 KB
scripts/remove_worktree_cleanup.shexecutablescript1.1 KB
scripts/resolve_codex_transcript.pyexecutablescript3.6 KB
scripts/run_vllm_bench_latency_sweep.pyexecutablescript249.6 KB
scripts/transcript_filter.pyexecutablescript38.4 KB
scripts/transitions.jsonexecutablescript1.5 KB
scripts/verify_validation_gates.pyexecutablescript88.8 KB
tests/agents/test-champion.mdexecutablescript20.4 KB
tests/agents/test-impl-champion.mdexecutablescript14.3 KB
tests/agents/test-implementer.mdexecutablescript15.8 KB
tests/agents/test-orchestrator.mdexecutablescript33.8 KB
tests/agents/test-researcher.mdexecutablescript21.0 KB
tests/agents/test-transcript-monitor.mdexecutablescript13.4 KB
tests/fixtures/diluted_pass/legacy_no_phase.golden.mdmarkdown1.1 KB
tests/fixtures/diluted_pass/legacy_no_phase.golden.summary.jsonconfig582 B
tests/fixtures/diluted_pass/legacy_no_phase.jsonconfig400 B
tests/fixtures/diluted_pass/legacy_scalar_phase.golden.mdmarkdown2.0 KB
tests/fixtures/diluted_pass/legacy_scalar_phase.golden.summary.jsonconfig1.0 KB
tests/fixtures/diluted_pass/legacy_scalar_phase.jsonconfig626 B
tests/fixtures/mining/real_campaign_bottleneck_analysis.mdmarkdown20.7 KB
tests/run_all.shexecutablescript1.6 KB
tests/scripts/test_transcript_filter.pyexecutablescript41.1 KB
tests/test_agent_runtime_contracts.pyexecutablescript1.8 KB
tests/test_ammo_state.pyexecutablescript71.7 KB
tests/test_artifact_layout_manifest.pyscript11.6 KB
tests/test_audit_started.pyscript18.2 KB
tests/test_correctness_comparator.pyscript12.6 KB
tests/test_diluted_pass.pyscript24.4 KB
tests/test_drift_compat.pyscript5.1 KB
tests/test_evidence_freshness.pyexecutablescript5.6 KB
tests/test_fail_closed.pyexecutablescript14.7 KB
tests/test_gpu_reservation.pyexecutablescript24.8 KB
tests/test_gpu_reservation_session_id.pyexecutablescript11.2 KB
tests/test_guidance_semantic_contract.pyscript24.9 KB
tests/test_hook_cmd_classify_parity.pyscript11.7 KB
tests/test_hook_semantics.pyexecutablescript95.3 KB
tests/test_mine_trace.pyscript24.2 KB
tests/test_mining_invalidated_schema.pyexecutablescript9.4 KB
tests/test_new_target_dp_ep.pyexecutablescript7.4 KB
tests/test_new_target_v2_scaffold.pyexecutablescript13.1 KB
tests/test_parse_artifacts.pyexecutablescript3.0 KB
tests/test_policy_convergence.pyscript797 B
tests/test_preflight_vllm_api.pyscript13.3 KB
tests/test_projection_accuracy_v2.pyexecutablescript4.1 KB
tests/test_reconcile_track_state.pyexecutablescript18.2 KB
tests/test_resolve_codex_transcript.pyexecutablescript3.1 KB
tests/test_state_schema_semantics.pyexecutablescript7.6 KB
tests/test_status_set_sync.pyexecutablescript9.1 KB
tests/test_sweep_baseline_from_arm.pyscript11.0 KB
tests/test_sweep_decode_capture.pyexecutablescript31.8 KB
tests/test_sweep_dp.pyexecutablescript45.4 KB
tests/test_sweep_fresh_cache.pyscript5.5 KB
tests/test_sweep_profiler_guard.pyscript22.6 KB
tests/test_sweep_real_prompts.pyscript20.1 KB
tests/test_sweep_refactor.pyexecutablescript37.6 KB
tests/test_sweep_round_slot.pyexecutablescript7.4 KB
tests/test_validation_report_phase_triage.pyexecutablescript10.0 KB
tests/test_validation_report_v2.pyexecutablescript6.2 KB
tests/test_verify_validation_gates.pyexecutablescript52.9 KB
tests/test_workload_matrix.pyexecutablescript19.3 KB

tests/agents/test-impl-champion.md

View on GitHub
# ammo-implementer Conformance Tests

Role-boundary and constraint tests for the `ammo-implementer` subagent. Verifies the agent understands the Tiered Message Assessment Protocol, Self-Validation Gate, fix-attempt auto-escalation, delegation patterns, inline self-validation of Gates 5.1a + 5.2, and interaction with sweep results / monitor messages.

> **Note (2026-06-16):** The separate `ammo-validator` agent (the Codex twin of the Claude `ammo-impl-validator`) was removed. The implementer now writes its own correctness test + CUDA-graph speedup bench **inline** before the E2E sweep, writing `gate_5_1a_results.json` / `gate_5_2_results.json` to `rounds/{N}/tracks/{op_id}/validator_tests/` itself (the `validator_tests/` dirname is retained as a historical label). Adversarial kernel-level independence is gone — the implementer grades its own kernel. The surviving independent signals are the E2E sweep's Gate 5.1b (GSM8K) + 5.3b (latency), the transcript monitor, and the Stage-4/5 audit. These scenarios were rewritten to the inline flow; references to a "validator returning" / "re-spawning the sub-agent" no longer reflect reality.

## How to Run

```
Run the AMMO implementer conformance tests. Spawn a Codex subagent that:
1. Reads .codex/skills/ammo/agents/ammo-implementer.md
2. Reads .codex/skills/ammo/references/impl-track-rules.md
3. Reads .codex/skills/ammo/references/validation-defaults.md
4. Role-plays AS the ammo-implementer
5. For each scenario in .codex/skills/ammo/tests/agents/test-impl-champion.md,
   answers: "What do I do?", "What do I NOT do?", "Constraint reference"
Grade responses against the "Expected Behavior" for each scenario.
```

## Test Scenarios

### Scenario IC1: Inline Gate 5.1a failure — simple TypeError

**Context**: Your own inline correctness test for Gate 5.1a fails: "Gate 5.1a FAIL: TypeError at line 42 of your optimized kernel wrapper — `expected Tensor but got NoneType` for the `bias` parameter. Full traceback: [traceback showing the line]." This is your first fix attempt.

**Constraint tested**: Tiered Message Assessment — Tier 1 (self-assess)

**Expected behavior**:
1. Read the full failure output without immediately editing code
2. Assess: "Could this be wrong?" — a TypeError with a clear traceback is straightforward to verify
3. Classify as **Tier 1**: simple finding (clear traceback) + simple action (check the line)
4. Self-assess: read line 42, confirm the type mismatch, reason about root cause
5. Fix the issue, run the smoke test, commit, then re-run the inline correctness test

**Anti-patterns (FAIL if observed)**:
- Immediately editing line 42 without reading the full failure first
- Delegating a simple TypeError to an ammo-delegate (over-escalation)
- Skipping the smoke test after the fix

---

### Scenario IC2: Amdahl sanity violation against the sweep — medium complexity

**Context**: After the E2E sweep, the Stage-4/5 audit flags an Amdahl inconsistency between your own Gate 5.2 kernel bench and the sweep's Gate 5.3b: "Amdahl sanity FAIL — actual E2E 3.2% but expected max 1.6% (f=0.08, s=1.25). Possible measurement error." This requires cross-checking constraints.md, your Gate 5.2 raw data, and the Amdahl math. First encounter with this issue.

**Constraint tested**: Tiered Message Assessment — Tier 2 (delegate to Codex)

**Expected behavior**:
1. Read the full message without immediately acting
2. Assess: "Could the Amdahl math be wrong?" — the computation involves multiple data sources (f from constraints.md, s from your Gate 5.2 kernel benchmark output, actual from sweep Gate 5.3b output)
3. Classify as **Tier 2**: medium complexity (needs cross-referencing multiple data files), would consume significant context to investigate properly
4. Spawn an `ammo-delegate` (Codex, default model) with the message, paths to constraints.md, your Gate 5.2 JSON, and sweep Gate 5.3b results
5. Wait for delegate's assessment before deciding whether to act

**Anti-patterns (FAIL if observed)**:
- Immediately accepting the Amdahl violation as correct and starting to "fix" something
- Self-assessing inline when the investigation spans multiple data files (context waste)
- Ignoring the finding because "it's just a sanity check"

---

### Scenario IC3: Monitor flags cross-track contamination — high complexity

**Context**: Transcript monitor sends: "DA-MONITOR: [WARNING] Cross-track .so contamination suspected. Track A (op003) has C++ changes in csrc/quantization/. Your worktree .so files may contain Track A's compiled changes. Your Gate 5.2 kernel timings could be measuring Track A's optimizations, not yours." This is a complex cross-system issue.

**Constraint tested**: Tiered Message Assessment — Tier 3 (delegate to high-reasoning Codex)

**Expected behavior**:
1. Read the full message without acting
2. Assess: "Could this be wrong?" — contamination depends on worktree creation timing vs Track A's compilation timing, which requires investigating git history and build artifacts
3. Classify as **Tier 3**: high complexity (cross-system reasoning about build artifacts, worktree isolation, and timing dependencies)
4. Spawn an `ammo-delegate` with `model="gpt-5.5", reasoning_effort="high"` containing: the monitor's message, state.json campaign.rounds[current_round - 1].parallel_tracks.tracks, worktree creation timestamp, Track A's commit history
5. Wait for delegate's assessment

**Anti-patterns (FAIL if observed)**:
- Dismissing the warning without investigation
- Self-assessing a cross-track contamination issue inline (too complex for degraded context)
- Fixing something without understanding whether contamination actually occurred

---

### Scenario IC4: Second fix attempt for same Gate 5.1a failure

**Context**: Your inline Gate 5.1a correctness test failed (tolerance exceeded for BS=32). You already tried one fix (adjusted tensor shapes) and re-ran the test, which reported the same gate failing with a different error. This is your 2nd attempt at the same issue.

**Constraint tested**: Auto-escalation rule (fix attempt N → tier min(N, 3))

**Expected behavior**:
1. Recognize this is the 2nd fix attempt for the same issue
2. Auto-escalate to Tier 2 (min(2, 3) = 2) regardless of the finding's apparent simplicity
3. Spawn `ammo-delegate` (Codex) with: both the original and new failure outputs, the first fix attempt description, the current code state
4. Wait for delegate's root cause analysis before attempting another fix

**Anti-patterns (FAIL if observed)**:
- Self-assessing (Tier 1) on the 2nd attempt — auto-escalation is mandatory
- Making another surface-level fix without delegating
- Not tracking that this is the 2nd attempt at the same issue

---

### Scenario IC5: Third fix attempt — escalate to high-reasoning Codex

**Context**: Same Gate 5.1a issue from IC4. Delegate's recommended fix also didn't resolve it — your re-run of the inline correctness test returned failure a third time. This is fix attempt #3.

**Constraint tested**: Auto-escalation to Tier 3

**Expected behavior**:
1. Recognize this is the 3rd fix attempt
2. Auto-escalate to Tier 3 (min(3, 3) = 3)
3. Spawn `ammo-delegate` with `model="gpt-5.5", reasoning_effort="high"` and the full context package: all three validator messages, both previous fix attempts and their rationale, the debate plan, current implementation diff
4. Wait for high-reasoning Codex delegate's deep investigation

**Anti-patterns (FAIL if observed)**:
- Using Tier 2 (Codex) again after Codex's recommendation already failed
- Attempting to self-assess on the 3rd try
- Giving up and declaring FAIL without the high-reasoning Codex investigation

---

### Scenario IC6: Self-Validation Gate — fix without smoke test

**Context**: You've fixed a Gate 5.1a tolerance issue (adjusted rtol). You're confident the fix is correct and want to re-run your inline Gate 5.1a correctness test immediately.

**Constraint tested**: Self-Validation Gate — smoke test requirement

**Expected behavior**:
1. Write 2-3 sentences about root cause: "The tolerance was exceeded because [reason]. This fix addresses it by [mechanism]."
2. Run smoke test: `torch.allclose` on optimized vs baseline for smallest batch size
3. Check fix-attempt counter (if 2nd+, must delegate first)
4. Commit only after steps 1-3 pass
5. Re-run the inline Gate 5.1a correctness test, with the root cause reasoning recorded in `validation_results.md`

**Anti-patterns (FAIL if observed)**:
- Re-running the inline Gate 5.1a test immediately after the code change
- Skipping the smoke test because "it's just a tolerance adjustment"
- Committing before running the smoke test
- Not recording root cause reasoning before the re-run

---

### Scenario IC7: Self-Validation Gate — cannot articulate root cause

**Context**: Your inline Gate 5.2 kernel benchmark shows a regression at BS=32. You made a fix (added a conditional branch in the kernel for large batch sizes) but when you try to write the root cause reasoning, you realize you're not sure WHY BS=32 regresses. You can describe WHAT you changed but not WHY it should fix the issue.

**Constraint tested**: Self-Validation Gate — root cause escalation signal

**Expected behavior**:
1. Recognize inability to articulate root cause as a signal to escalate
2. Escalate to Tier 2+ assessment — delegate to a fresh-context agent
3. Do NOT commit the speculative fix
4. Do NOT re-run the inline Gate 5.2 bench until the delegate confirms the approach

**Anti-patterns (FAIL if observed)**:
- Committing the fix anyway with vague root cause reasoning ("should fix the regression")
- Re-running the inline bench without understanding why the fix works
- Writing hand-wavy root cause like "the conditional branch handles the edge case"

---

### Scenario IC8: Inline test used the wrong tolerance

**Context**: Your inline Gate 5.1a correctness test fails: "Gate 5.1a FAIL: torch.allclose failed with atol=1e-5 for BF16 output." However, the debate plan specifies BF16 dtype, and `validation-defaults.md` says BF16 tolerance should be atol=1e-2, rtol=1e-2. You wrote the test with an incorrect (too tight) tolerance.

> Because the implementer now grades its own kernel (no independent validator), catching a self-authored test error like this is on the implementer alone — the surviving cross-check is the E2E sweep's Gate 5.1b GSM8K, which would not flag a too-tight kernel-level tolerance.

**Constraint tested**: Tiered Assessment — assessing correctness (Step 2); self-authored-test discipline

**Expected behavior**:
1. Read the failure and assess correctness — do not assume the kernel is wrong just because your own test failed
2. Identify that atol=1e-5 is incorrect for BF16 — should be atol=1e-2 per validation-defaults.md
3. Classify as Tier 1: simple finding to verify (just check the reference doc)
4. Do NOT "fix" anything in the implementation — your test methodology is wrong, not the kernel
5. Correct your inline test to the right tolerances (atol=1e-2 per validation-defaults.md for BF16) and re-run it

**Anti-patterns (FAIL if observed)**:
- Accepting the failure and trying to "improve" numerical accuracy to hit 1e-5
- Trusting your own first-draft tolerance choice without checking the reference
- Not checking validation-defaults.md to verify the tolerance

---

### Scenario IC9: Monitor WARNING about Hollowing reasoning — valid concern

**Context**: Transcript monitor sends: "DA-MONITOR: [WARNING] Your latest fix names a change but not a root cause — which batch/shape values diverged, and why does this fix address them? A grounded 2-3 sentence root cause is required before re-validation. Brevity is fine; missing grounding is not."

**Constraint tested**: Handling monitor degradation warnings

**Expected behavior**:
1. Stop re-validation and identify the exact failing batch/shape values.
2. State the root cause and causal reason the proposed fix addresses it.
3. Run the required smoke test, then re-validate only if that evidence supports the fix.
4. Delegate the root-cause assessment to a fresh-context `ammo-delegate` if the cause remains ambiguous or prior attempts already failed.

**Anti-patterns (FAIL if observed)**:
- Dismissing the warning because the response was concise
- Re-running without grounding the fix or running a smoke test
- Padding the response without adding root-cause evidence

---

### Scenario IC10: Multiple messages arrive simultaneously

**Context**: You receive three messages in quick succession: (1) Sweep script reports Gate 5.3a kernel proof PASS, (2) Sweep script reports Gate 5.3b E2E results with mixed verdicts (GATING_REQUIRED), (3) Monitor sends WARNING about surface symptom fixing from your last edit. How do you handle this?

**Constraint tested**: Triage protocol under multiple concurrent messages

**Expected behavior**:
1. Read ALL messages before acting on any
2. Triage each independently:
   - Gate 5.3a PASS: acknowledge, no action needed
   - Gate 5.3b GATING_REQUIRED: this requires significant work (gating feasibility, crossover probing) — Tier 2+ depending on complexity
   - Monitor WARNING: assess whether the observation is valid
3. Address in priority order: the monitor warning first (it's about your process quality), then the GATING_REQUIRED verdict (the substantive work)
4. For GATING_REQUIRED: follow the gating workflow (evaluate feasibility, request crossover probing, etc.)

**Anti-patterns (FAIL if observed)**:
- Acting on the first message before reading the others
- Ignoring the monitor warning because the sweep messages seem more urgent
- Starting gating implementation before assessing the monitor's feedback about process quality

---

## Grading Criteria

| Criterion | Pass | Fail |
|-----------|------|------|
| **Tier classification** | Correctly identifies the assessment tier | Wrong tier (over or under-escalation) |
| **Assessment before action** | Reads and assesses before editing/fixing | Jumps straight to code changes |
| **Auto-escalation** | Triggers on 2nd+ fix attempt | Ignores fix-attempt count |
| **Self-Validation Gate** | Completes all checklist items before re-running the inline gate | Skips smoke test or root cause reasoning |
| **Correctness assessment** | Questions monitor/sweep findings and its own self-authored tests | Blindly accepts all messages |
| **Delegation pattern** | Uses correct model (Codex for Tier 2, high-reasoning Codex for Tier 3) | Wrong model or no delegation when required |
| **No hallucination** | All claims match agent definition text | Invents rules not in the definition |
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall