Creates tests for code files changed in the current git diff.
npx skills add https://github.com/oporpino/commons --skill br4zz4-skill-test-oporpino
Please help me install this Agent Skill. Skill: br4zz4:skill:test Source: https://github.com/oporpino/commons/tree/main/ai/shared/skills/br4zz4%3Atest Command: npx skills add https://github.com/oporpino/commons --skill br4zz4-skill-test-oporpino
git diff and analyzes happy paths, alternative flows, and boundary inputs. - Convention enforcement: Applies Triple A pattern, atomic tests, one assert per test, and correct mock usage for unit vs integration tests. - Safety guardrails: Never modifies existing test files or production code without explicit user confirmation, preventing false positives. - Use Case: After finishing a feature branch, ask the assistant to create tests for your changes; it inspects the diff, writes the tests, and runs make t to verify they pass. ## Quick Start Create tests for the files changed in my current git diff and verify they pass.High-intent search queries and answers about installing and using this skill.
Run git diff to list modified code files, analyze each change for happy paths, alternative flows, and boundary inputs, then write tests following the Triple A pattern. This Skill automates that entire workflow and verifies results with make t.
Structure each test with explicit arrange, act, and assert comments, keep tests atomic by instantiating everything inside the test, and limit assertions to one per test. Use mocks for external dependencies in unit tests only.
No. If test files already exist for the changed code, the Skill asks for explicit permission before modifying them, describing exactly what will change and why. This prevents accidental regressions in existing coverage.
The Skill analyzes the failure: if the issue is in the test, it fixes the test; if the failure indicates a real bug in production code, it reports the problem to the user instead of changing the code to make the test pass.
No. The testing rules applied here use mocks only for external dependencies in unit tests. Integration tests run against real dependencies to validate actual component interactions.
ImaginerLabsAnalyze code diffs and generate prioritized Markdown test reports.
blakesimsValidate feature branch merge readiness with integration checks and summaries.
jorgealvesAnalyze code diffs to identify bugs, style violations, and logic errors.
cenmiaoEnforce test-driven development with failing tests before production code.