testing-strategy
Universal testing strategies and best practices for software projects
Discover tools cicd skills, compare source repositories and read the instructions for each workflow.
Universal testing strategies and best practices for software projects
Logging, debugging, profiling, and performance monitoring for development. Use when adding logging, debugging issues, profiling performance, or instrumenting code for observability.
Documentation consistency enforcement - prevents drift between README.md and actual codebase state. Auto-activates when updating docs, committing changes, or working with skills/agents/commands.
GenAI-powered semantic validation - detects outdated docs, version mismatches, and architectural drift
GitHub-first workflow - Issues, PRs, milestones, auto-tracking for solo developer productivity
Documentation standards and automation. Use when updating docs, writing guides, or synchronizing code with documentation.
Git best practices, commit conventions, branching strategies, and pull request workflows. Use when working with git operations, commits, branches, or PRs.
META ORCHESTRATOR for complete implementation workflow - design, test, lint, refactor, review, commit. Use for any code change that should result in a commit (features, bug fixes, refactors). Ensures clean code...
Critical analysis and quality assurance for design documents, implementation plans, and code verification. Use when reviewing designs, plans, or checking code quality.
APKビルドとGitHubリリースを作成するスキル
REQUIRED Phase 5 of /dev workflow. Orchestrates per-task ralph loops with delegated TDD implementation.
This skill should be used when the user asks to 'verify analysis results', 'check reproducibility', 'validate data science output', 'confirm completion', or as Phase 5 of the /ds workflow (final). Enforces repr...
Internal skill used by dev-implement during Phase 5 of /dev workflow. NOT user-facing - should only be invoked by dev-ralph-loop inside each implementation iteration. Handles Task agent spawning with TDD enforc...
REQUIRED Phase 2 of /dev workflow after dev-brainstorm. This skill should be used when the user asks to 'explore the codebase', 'map architecture', 'find similar features', 'discover test infrastructure', 'trac...
REQUIRED Phase 3 of /dev workflow. Asks targeted questions based on codebase exploration findings.
Playwright MCP browser testing. Headless E2E, cross-browser, CI/CD automation.
This skill should be used when the user asks to 'verify completion', 'check that tests pass', 'confirm feature works', or REQUIRED Phase 7 of /dev workflow (final). Enforces fresh runtime evidence before claimi...
This skill should be used when the user asks to "propose architecture", "design implementation approach", "choose between approaches", or in Phase 4 of /dev workflow after exploration is complete. Proposes 2-3...
Set up GitHub repository integration for a SentryVibe project. Use this skill when the user wants to: - Connect their project to GitHub - Create a new GitHub repository for their project - Push their project co...
Deep codebase exploration using semantic search and relationship mapping. Use when you need to understand the current codebase.
/sdlc-studio [type] [action] - SDLC pipeline: requirements, specifications, code, testing. Run /sdlc-studio help for commands and /sdlc-studio status for next steps.
Provide guidelines on how to determine appropriate git commit messages that are compliant with project standards. Should be used when generating, modifying, or reviewing git commit messages.
Provide guidelines on how to develop Ansible playbooks that are compliant with project standards. Should be used when generating, modifying, or reviewing Ansible playbooks, roles, or collections.
Write and edit GitHub Actions workflow files. Use when creating new workflows, editing existing .github/workflows/*.yml files, or setting up CI/CD pipelines. Triggers on requests like "create a workflow", "add...
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.