--- description: Run ament linters (uncrustify, cpplint, flake8…
Community ralph loop for testing, sourced from github. Verified exit condition, evaluator-gated.
--- description: Run ament linters (uncrustify, cpplint, flake8, pep257, xmllint, copyright) and pre-commit against changed files. argument-hint: "[--all | <file paths>]" allowed-tools: ["Bash"] --- Lint the workspace. Argument handling ( $ARGUMENTS ): Empty → only changed-vs-main: pre-commit run --from-ref origin/main --to-ref HEAD --all → pre-commit run --all-files Else treat as a space-separated file list: pre-commit run --files $ARGUMENTS For ament-specific checks (when pre-commit is not configured for a package), run the relevant tools directly: | File kind | Command | |-----------|---------| | C++ | ament uncrustify --reformat <files> then ament cpplint <files> | | Python | ament flake8 <files> then ament pep257 <files> | | XML / launch / package.xml | ament xmllint <files> | | Any source| ament copyright <files> | Rules: Never pass --no-verify or --no-ament-copyright . If a hook fails, fix the root cause. If a formatter auto-fixed a file, tell the user explicitly so they can stage the change. For C++ packages with a compile DB, also offer to run: clang-tidy -p build/<pkg> <files> . End with a one-line summary:
claude-code
More testing loops
Ship the release
Run tests and update changelog until both pass without altering the public API.
/goal ship the release --success "tests pass and changelog updated" --constraints "do not touch the public API" --mode ordered
testingmedium risk
/ralph-loop "fix all tests" --max-iterations 5 (iterates until…
Community ralph loop for testing, sourced from github. Verified exit condition, evaluator-gated.
/ralph-loop "fix all tests" --max-iterations 5 (iterates until passing
testingmedium risk
Trim what loads before first paint
Reduce the data downloaded before the first screen appears, with tests and screenshots guarding behavior and appearance.
Reduce the data [web app] downloads before its first screen appears. First record passing tests, mobile and desktop screenshots, and compressed transferred bytes—the data actually downloaded. Use the build report only to suggest candidates. Defer, compress, or remove one item, then rebuild and rerun every check. Keep it only if tests pass, screenshots are pixel-identical, and bytes decrease; otherwise revert. Stop when no safe candidate remains, progress stalls, or approval is needed. Return measurements, changes, and untested states.
testingmedium risk