ccppccpp home

Profiles

CCPP Tester

Only the cpo:ccpp-tester agent writes tests (tests, helpers, fixtures, snapshots, Lighthouse audits), and it never reads the code under test nor the mutation reports that hold it. Needs the cpo plugin, which ships the agent.

Set this profile

ccpp cpo profile set ccpp-tester

Inside Claude Code, prefix the command with ! to run it in the session. Downloading a profile needs a Builder or Team plan; listing them does not.

Policies

13 policies, grouped by what they guard.

Tests 13

Tests assert behavior, stay deterministic and are not removed or skipped silently.

  • ccpp-tester-deletes-tests-only

    cpo:ccpp-tester deletes test-side files only, never the code (a shell deletion leaves no file.write to judge)

  • ccpp-tester-mutation-copy

    cpo:ccpp-tester's shell reaches a Python campaign copy, a mutants/ tree or its cache only through names, the engine, quiet pytest, cp or tar into the copy, and the skill's reader

  • ccpp-tester-mutation-engine

    cpo:ccpp-tester runs mutmut's run only inside a campaign copy, never apply, show or browse, hides no script naming the copy and leaves the skill's readers alone

  • ccpp-tester-mutation-report

    cpo:ccpp-tester sees Stryker mutants as diffs (clear-text, outcomes.jq), and no tool reads the source a mutation report, sandbox or campaign copy holds

  • ccpp-tester-no-code-read

    cpo:ccpp-tester does not read the code under test (source the other agents wrote this session)

  • ccpp-tester-python-runs

    Mark the cpo:ccpp-tester shell calls that run Python or pytest, whose bytecode and pytest cache writes are not code

  • ccpp-tester-shell-writes

    cpo:ccpp-tester's commands change nothing in HOME or /tmp outside its scratch directories and create no jq filter

  • ccpp-tester-skill-only

    The cpo:ccpp-tester skill is loaded by cpo:ccpp-tester only

  • ccpp-tester-track-code

    Remember the source files written by any agent other than cpo:ccpp-tester, so ccpp-tester cannot read them

  • ccpp-tester-track-helpers

    Remember the Python helpers cpo:ccpp-tester writes (known by their pytest or unittest imports), so their deletion is undone like a test's

  • ccpp-tester-writes-tests

    cpo:ccpp-tester writes test-side files only, never the code

  • tests-by-ccpp-tester-delete

    Only cpo:ccpp-tester deletes test-side files (a shell deletion leaves no file.write to judge)

  • tests-by-ccpp-tester

    Only cpo:ccpp-tester creates or changes test-side files (tests, test helpers, fixtures, snapshots, Lighthouse audits)