Security & Testing Agent Skills for DeepSeek Harness

After code changes, run the required baseline (moon tasks run from anywhere in the repo, including CI-marked agent shells): Useful…

Use when writing or changing tests, adding mocks, or tempted to add test-only methods to production code - prevents testing mock behavior…

Use when the user wants to audit test quality, find flaky test patterns, speed up test execution, or prepare for Swift Testing migration.

Unit testing, integration testing, and test-driven development principles.

Automatically generates comprehensive test suites (unit, integration, E2E) based on code and past testing patterns.

Testing code that calls an APIMatic-generated .NET SDK in C# — which seam to fake, covering error and edge paths, asserting real behaviour…

How to write integration tests for error processors in packages/core/src/processors/.

Testing mastracode TUI features interactively in Konsole.

Apply Google Testing on the Toilet (TotT) rules when writing tests, reviewing a test diff, choosing mocks vs fakes, diagnosing brittle or…

Create and audit durable verification and validation evidence for software, documentation, configuration, or operations.

Gate a built v1 to go / no-go on two recorded tests — a true stranger reaches first correct value in ≤60 seconds unaided, AND the…

Diagnosis loop for hard bugs and performance regressions.

Validate AGENTS.md files for structural completeness, operational contract coverage, neutrality, and repository alignment.

Validate that a branch or pull request implementation matches introduced product, technical, security, and related specs.

Use after code changes or before handoff to choose and run validation proportional to risk.

Creates, refactors, and diagnoses Turbo Gherkin feature files for 1C:Enterprise UI automated testing with Vanessa Automation.

Designs and establishes structured directories, naming conventions, and cleanup rules for new Vanessa Automation BDD testing projects.

Secure environment variable management ensuring secrets are never exposed in Claude sessions, terminals, logs, or git commits

Prima di dichiarare una task completata, fixata, funzionante o pronta per il deploy, esegui il comando di verifica e leggi l'output.

Use when verification needs bounded claims, evidence, and approval gates.

Set a repo up to prove engineering-task work actually works before it ships.