Modern C++ testing workflow using GoogleTest/GoogleMock with CMake/CTest integration.
Automate repetitive workflows and reduce manual effort
Example: Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example: Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example: Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Time estimate: 15-45 minutes depending on use case complexity
Prerequisites
Submit your Claude Code skill and start earning
epx add affaan-m/everything-claude-code --skill cpp-testingCompatible with
Supported agents
Covers unit and integration test design with TDD red-green-refactor loop, fixtures, mocks, and fakes for dependency isolation
Includes CMake/CTest configuration with automatic test discovery via gtest_discover_tests() and filtering strategies
Provides coverage setup for GCC (gcov/lcov) and Clang (llvm-cov), plus sanitizer configuration (ASan, UBSan, TSan) for memory and race detection
Documents f
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versioncpp-testingExecute the skills CLI command in your project's root directory to begin installation:
epx add affaan-m/everything-claude-code --skill cpp-testingFetches cpp-testing from affaan-m/everything-claude-code and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
.cursor/skills/cpp-testing
Restart Cursor to activate cpp-testing. Access via /cpp-testingin your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
flutter-dart-code-review
affaan-m/everything-claude-code · Productivity · same repo
django-patterns
affaan-m/everything-claude-code · Backend · same repo
deep-research
affaan-m/everything-claude-code · Productivity · same repo
nuxt4-patterns
affaan-m/everything-claude-code · Productivity · same repo
investor-outreach
affaan-m/everything-claude-code · Productivity · same repo
wordpress-penetration-testing
davila7/claude-code-templates · Testing · tag: testing
cpp-testing has been reliable in day-to-day use. Documentation quality is above average for community skills.
Keeps context tight: cpp-testing is the kind of skill you can hand to a new teammate without a long onboarding doc.
Keeps context tight: cpp-testing is the kind of skill you can hand to a new teammate without a long onboarding doc.
cpp-testing has been reliable in day-to-day use. Documentation quality is above average for community skills.
cpp-testing reduced setup friction for our internal harness; good balance of opinion and flexibility.
cpp-testing is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
cpp-testing fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for cpp-testing matched our evaluation — installs cleanly and behaves as described in the markdown.
Registry listing for cpp-testing matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in cpp-testing — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 64