Rea Ci Tests Audit

morluto/rea/.agents/skills/rea-ci-tests-audit

作者 morlutoc8d5413d0fe54c5f8236e1cb8f61ad462d08fd1d無授權條款472K 個星標收錄於 2026年10月17日更新於 2026年11月14日儲存庫今天更新

Audit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.

AI 產生的概覽

稽核 CI 工作流程與測試套件,找出假通過、測試資料漂移與效能成本,產出經核實的修正或有證據支持的建議。

功能
引導代理先建立已執行的基準(固定 SHA、工作流程版本、確切指令與工具鏈),再追蹤工作流程觸發、變更路徑篩選、工作相依性、測試探索與報告閘門,一路追到真正執行的指令。內容涵蓋測試資料漂移、可疑的綠色測試、共用初始化與提供者涵蓋範圍,並藉由區分建置、執行、插樁與排程成本來評估效率。產出為稽核紀錄、分類後的發現,以及在獲授權時的最小修正、回歸測試與交接報告。
適用情境
適用於對整個 CI 流程或測試套件進行調查:懷疑有假通過、測試資料過期、涵蓋閘門缺失,或工作流程緩慢且雜訊過多。不適用於一般功能測試或單一測試失敗的排查。
執行需求
僅為說明文件,不含腳本。需要存取儲存庫工作區、其 AGENTS.md、測試指南與貢獻規則、CI 工作流程定義與產出物,並能在本機執行儲存庫固定的工具鏈與測試指令。

REA CI and tests audit

Establish which checks still catch real regressions and which costs can be removed without losing that protection. The outcome may be a verified fix, an evidence-backed recommendation, or an explicit decision to stop.

Follow the checkout's AGENTS.md, testing guide, and contribution rules. Use their current commands and pinned toolchain, rather than commands remembered from an earlier audit. Preserve the requested scope: investigation alone does not authorize edits; this skill does not grant permission to publish issues, push, or merge. Existing user authorization still applies. Keep audit notes and raw results outside the tracked tree, normally in a task-specific /tmp directory.

Establish the executed baseline

Fetch when the user asks for latest main. Pin the baseline SHA and inspected workflow revision; use an isolated worktree when changing or comparing code. Do not modify another task's checkout. Record dirty changes and the exact command, toolchain, host, selected tests, instrumentation, and prerequisites. An old run is evidence for its executed revision, even if main advances.

Trace workflow triggers, changed-path selection, job dependencies, reusable actions, package scripts, test discovery, artifact producers, and report gates through to the commands that actually execute. Include scripts, generated data, runtime registration, and subprocess boundaries missing from import graphs. Check positive and negative selection paths: required files must be discovered once per intended test configuration; deliberate platform/configuration repeats are separate coverage. A missing explicit test or missing required report must not turn green. Optional lanes may skip; preserve their stated prerequisites.

Use existing timing and failure artifacts to select suspicious families. Run relevant checks to establish a baseline; reserve a full local suite for broad CI diagnosis or uncertainty that focused checks cannot resolve. Do not rebuild or rerun an unchanged complete suite after every documentation edit.

Prove the failure or protection

For each candidate, state the expected observable behavior and its owner, then construct the smallest reproduction against production behavior. Follow the producer and affected consumers before deciding where to fix it.

  • For drift, compare fixtures with current admission requirements, protocol replies, named contracts, tool versions, and actual public entrypoints. A plausible-looking mock can fail before the behavior its test claims to cover. Search the whole affected fixture family, including other version strings. Preserve intentionally malformed fixtures and test their intended rejection.
  • For a suspicious green test, perturb the relevant behavior in an isolated copy or inject a controlled failure. Verify that the existing assertion or gate detects it. A test may merely repeat its mock, import abandoned code, or hide a subprocess/checker failure. Restore mutations after the experiment.
  • For shared setup or pruning, map distinct assertions to their retained scenarios. Preserve malformed inputs, cancellation, cleanup failure, permissions, capacity, identity, and meaningful concurrency interactions. A faster run that skips a case or weakens its oracle is not an improvement.
  • For provider coverage, separate fake-producer, boundary, and actual-engine evidence. Inspect named skips and prerequisites; fixtures do not establish real Ghidra, LLDB, browser, or other provider behavior.

Classify findings as reproduced defects, supported costs, hypotheses, or unavailable evidence. Record the baseline command, observed output/exit status, expected result, affected scope, and competing explanation. A failure on main may be pre-existing; that does not by itself make it irrelevant to a CI audit. Attribute PR failures using the executed revision and a clean baseline, not just their resemblance to a previous failure. Retry only to test a specific transient explanation; retain the original failure and stop when repetition adds no evidence. A passing retry does not establish a root cause or a fix.

Assess efficiency without losing the gate

Read measurement and CI checks [blocked] when investigating slowness, caching, runner waits, shared artifacts, or log noise. Compare equivalent completed work before claiming a speedup. Distinguish setup/build time, test execution, coverage instrumentation, dependency waits, and runner scheduling; state which costs remain unmeasured.

Prefer removing proven duplicate preparation, reusing immutable setup, and reducing repeated subprocess work before shrinking correctness coverage. Preserve independent sessions where lifecycle or concurrency is the oracle. Keep live tests fresh; a cached previous pass cannot validate current host, installed provider contents, permissions, or external state.

Fix, verify, and hand off within scope

If implementation is authorized, make the smallest structural change at the owning boundary and add a regression that fails on the baseline for the right reason. Retest affected consumers and meaningful negative paths; verify cache invalidation or discovery when those mechanisms change. Read the installed Turbo documentation before changing its configuration or commands.

Run the repository's applicable checks and inspect complete current-head CI results before an authorized merge. Preserve required coverage and discovery gates. Do not suppress a failure, add blanket retries, raise timeouts, or delete distinct assertions solely to make CI green. Changes to these controls need their own demonstrated reason and retained failure detection. A slow-host failure at a literal test, child, or wait deadline belongs to the test deadline policy: remove the literal rather than raise it, and keep promptness oracles explicit.

Report each confirmed issue with exact revision, reproduction, consequence, proposed correction, and validation limits. Report performance with workload and measurements, not just a percentage. Use English issue/PR records when requested; follow the user's assignment, commit identity, review, and merge preferences without assuming them for other users. Open ready-for-review PRs only when that lifecycle is authorized. Resolve necessary review findings and check final main against the tested tree after merging.

Stop when the authorized work is verified, remaining benefits are unproven, or further changes would trade correctness for speculative speed. List genuine uncertainties without turning them into additional optimization rounds.

來源與署名

來源:morluto/rea位於.agents/skills/rea-ci-tests-audit提交c8d5413

授權條款: 無授權條款

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

在 README 中新增徽章

向讀者展示該技能已收錄於 SourceWeft,徽章連結到本頁。

「Listed on SourceWeft」徽章預覽
[![Listed on SourceWeft](https://sourceweft.com/badge/skills/gh-morluto-rea-rea-ci-tests-audit-agents-skills-rea-ci-tests-audit-c3b90fac129ee7f3.svg)](https://sourceweft.com/skills/gh-morluto-rea-rea-ci-tests-audit-agents-skills-rea-ci-tests-audit-c3b90fac129ee7f3?utm_source=readme&utm_medium=badge)

檢舉或申請下架