@proffesor-for-testing
Knowledge is power. Keep learning. Keep sharing.
스킬 205개저장소 1개 515
Evidence-based investigative code review using deductive reasoning to determine what actually happened versus what was claimed. Use when verifying implementation claims, investigating bugs, validating fixes, or conducting root cause analysis. Elementary approach to finding truth through systematic observation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Move testing activities earlier in the development lifecycle to catch defects when they're cheapest to fix. Use when implementing TDD, CI/CD, or early quality practices.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Testing in production with feature flags, canary deployments, synthetic monitoring, and chaos engineering. Use when implementing production observability or progressive delivery.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply Edward de Bono's Six Thinking Hats methodology to software testing for comprehensive quality analysis. Use when designing test strategies, conducting test retrospectives, analyzing test failures, evaluating testing approaches, or facilitating testing discussions. Each hat provides a distinct testing perspective: facts (White), risks (Black), benefits (Yellow), creativity (Green), emotions (Red), and process (Blue).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when reviewing which QE skills are being used, finding undertriggering skills, or analyzing skill effectiveness. Shows usage patterns and recommendations.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when enforcing TDD discipline — blocks writing production code unless a failing test exists first. Activate with /strict-tdd to enable session-scoped Red-Green-Refactor guardrail.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Advanced swarm orchestration patterns for research, development, testing, and complex distributed workflows
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply London (mock-based) and Chicago (state-based) TDD schools. Use when practicing test-driven development or choosing testing style for your context.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write clear, engaging technical content from real experience. Use when writing blog posts, documentation, tutorials, or technical articles.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design and implement effective test automation with proper pyramid, patterns, and CI/CD integration. Use when building automation frameworks or improving test efficiency.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Strategic test data generation, management, and privacy compliance. Use when creating test data, handling PII, ensuring GDPR/CCPA compliance, or scaling data generation for realistic testing scenarios.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Systematic test design with boundary value analysis, equivalence partitioning, decision tables, state transition testing, and combinatorial testing. Use when designing comprehensive test cases, reducing redundant tests, or ensuring systematic coverage.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Test environment provisioning, infrastructure as code for testing, Docker/Kubernetes for test environments, service virtualization, and cost optimization. Use when managing test infrastructure, ensuring environment parity, or optimizing testing costs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when assessing post-release production health with DORA metrics, root cause analysis, defect prediction, or cross-phase feedback loops in the QCSD Production phase.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when running Quality Criteria sessions during PI/Sprint planning with HTSM v6.3, Risk Storming, or Testability analysis in the QCSD Ideation phase.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when monitoring in-sprint code quality with TDD adherence checks, complexity analysis, coverage gap detection, or defect prediction in the QCSD Development phase.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when enforcing CI/CD quality gates before release, running regression analysis, detecting flaky tests, or assessing deployment readiness in the QCSD Verification phase.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when reviewing a GitHub PR for quality, scope correctness, trust tier compliance, or generating user-friendly review feedback.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Profiles application performance under load using k6, Artillery, or JMeter to measure latency, throughput, and error rates. Use when planning load tests, stress tests, soak tests, benchmarking APIs, or identifying performance bottlenecks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when validating security findings from SAST/DAST scans, proving exploitability of reported vulnerabilities, eliminating false positives, or running the 4-phase pentest pipeline (recon, analysis, validation, report).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implement adaptive learning with ReasoningBank for pattern recognition, strategy optimization, and continuous improvement. Use when building self-learning agents, optimizing workflows, or implementing meta-cognitive systems.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implement ReasoningBank adaptive learning with AgentDB's 150x faster vector database. Includes trajectory tracking, verdict judgment, memory distillation, and pattern recognition. Use when building self-learning agents, optimizing decision-making, or implementing experience replay systems.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
AI-assisted pair programming with multiple modes (driver/navigator/switch), real-time verification, quality monitoring, and comprehensive testing. Supports TDD, debugging, refactoring, and learning sessions. Features automatic role switching, continuous code review, security scanning, and performance optimization with truth-score verification.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.