All authors

Claude Skills by Dadmin88
github.com/Dadmin88818 skills21 installs1,070 views
- Browser Api AutomationImplement browser and API automation that validates user-observable behavior without coupling tests to incidental implementation details.Votes: 0GitHub stars: 16
- Ci Test OptimizationOptimize automated test execution for feedback speed and signal quality using sharding, caching, selective execution, quarantine discipline, and artifact retention.Votes: 0GitHub stars: 16
- Flaky Test DiagnosisDiagnose and eliminate flaky automated tests by classifying nondeterminism across timing, shared state, environment, ordering, network, resources, and assertions.Votes: 0GitHub stars: 16
- Test Fixture EngineeringBuild deterministic fixtures and test data with explicit lifecycle, ownership, isolation, and cleanup across parallel test execution.Votes: 0GitHub stars: 16
- Test Harness DesignDesign an automated test harness with stable boundaries, fixtures, observability, and failure diagnostics appropriate to the product architecture.Votes: 0GitHub stars: 16
- Defect TriageTriage defects by establishing reproducibility, user/system impact, severity, scope, regression status, ownership, duplicates, release relevance, and the evidence needed for a decision without turning priority into guesswork.Votes: 0GitHub stars: 16
- Quality MetricsDefine and interpret quality metrics that connect defects, test evidence, release outcomes, escapes, reliability, support, and recovery to decisions without rewarding vanity test counts or gaming.Votes: 0GitHub stars: 16
- Release Quality PlanDefine the quality evidence required for a release by mapping changed behavior, critical journeys, risks, environments, test ownership, entry/exit criteria, known gaps, and post-release validation.Votes: 0GitHub stars: 16
- Risk Based TestingPrioritize testing by identifying plausible failures, affected users/assets, likelihood, impact, detectability, change novelty, and existing controls, then spend validation effort where it buys the most confidence.Votes: 0GitHub stars: 16
- Test StrategyDesign a risk-based test strategy that maps product and technical risks to appropriate validation layers and release evidence.Votes: 0GitHub stars: 16
- Bug ReproductionTurn a reported defect into a reliable, minimal, evidence-backed reproduction with exact environment, preconditions, steps, frequency, expected behavior, actual behavior, and scope clues.Votes: 0GitHub stars: 16
- E2e ValidationValidate a critical user or system journey end to end across real application boundaries, state changes, integrations, side effects, recovery behavior, and observable final outcomes.Votes: 0GitHub stars: 16
- Exploratory TestingExecute a focused exploratory test session that probes real user behavior, edge cases, state transitions, and unexpected interactions.Votes: 0GitHub stars: 16
- Regression TestingPlan and execute risk-based regression testing around a change by mapping affected behavior, preserved critical flows, integrations, data states, environments, and prior defect history.Votes: 0GitHub stars: 16
- Test Case DesignDesign high-value test cases from requirements, risks, state transitions, input partitions, boundaries, permissions, decisions, failures, and realistic user workflows.Votes: 0GitHub stars: 16
- Abuse Case TestingPerform authorized defensive testing of misuse and abuse scenarios by turning attacker or malicious-user goals into bounded hypotheses, evidence, impact, and remediation without exceeding the approved test scope.Votes: 0GitHub stars: 16
- Adversarial AssessmentConduct an authorized adversarial assessment to identify exploitable assumptions, abuse paths, privilege escalation, and control failures.Votes: 0GitHub stars: 16
- Attack Surface ReviewMap and prioritize a system's externally and internally reachable attack surface across identities, interfaces, data inputs, files, network paths, dependencies, automation, admin functions, agents/tools, and lifecycle operations for authorized defensive review.Votes: 0GitHub stars: 16
- Privilege Boundary TestingPerform authorized defensive tests of identity, role, tenant, resource-ownership, service, node, and administrative privilege boundaries using bounded negative cases and clear evidence of allowed versus denied behavior.Votes: 0GitHub stars: 16
- Prompt Injection TestingConduct authorized defensive testing of AI instruction-boundary failures using controlled untrusted content, tool/retrieval scenarios, and trace evidence to verify that external data cannot silently override higher-priority intent or expand authority.Votes: 0GitHub stars: 16
- Change ControlControl consequential release changes by making scope, revision, evidence, approvals, timing, exceptions, and post-approval drift explicit without turning every small change into bureaucracy.Votes: 0GitHub stars: 16
- Post Release ValidationValidate a release after deployment using revision-specific health, critical user flows, data integrity, migrations, observability, error budgets, and rollback criteria before declaring it complete.Votes: 0GitHub stars: 16
- Release ChecklistBuild and execute a release checklist from the actual release surface, required evidence, owners, dependencies, approvals, rollout steps, and recovery conditions rather than a generic template.Votes: 0GitHub stars: 16
- Release ReadinessAssess whether a release is ready to ship using evidence from scope, testing, security, operations, documentation, rollback, and stakeholder approvals.Votes: 0GitHub stars: 16
- Rollback PlanDesign a release rollback or forward-recovery plan from failure modes, state changes, data compatibility, trigger conditions, authority, execution steps, and validation evidence.Votes: 0GitHub stars: 16
- Audience SegmentationSegment release-note information by the readers whose actions or workflows differ, such as end users, administrators, developers, operators, or integrators, without duplicating the entire release for each audience.Votes: 0GitHub stars: 16
- Breaking Change CalloutDocument a breaking or behaviorally incompatible release change with affected users, old and new behavior, required migration, deadlines, mixed-version implications, recovery, and exact references.Votes: 0GitHub stars: 16
- Changelog CurationCurate repository and product changes into a user-meaningful changelog by selecting externally relevant behavior, grouping related changes, verifying versions and scope, and excluding internal noise.Votes: 0GitHub stars: 16
- Release NotesTurn verified shipped changes into concise release notes organized around user impact, upgrade implications, fixes, and compatibility concerns.Votes: 0GitHub stars: 16
- Upgrade SummarySummarize an upgrade for existing users through benefits, changed behavior, prerequisites, compatibility, migration effort, validation, rollback or recovery, and post-upgrade differences.Votes: 0GitHub stars: 16
- Acceptance CriteriaTurn requirements into precise, observable acceptance criteria covering success, failure, permissions, boundaries, states, and constraints without dictating unnecessary implementation details.Votes: 0GitHub stars: 16
- Ambiguity ReviewReview requirements for undefined actors, terms, states, timing, ownership, limits, conflicts, assumptions, and hidden implementation choices before ambiguity turns into divergent work.Votes: 0GitHub stars: 16
- Edge Case AnalysisIdentify and classify requirement edge cases across boundaries, invalid or missing input, permissions, concurrency, timing, partial failure, state transitions, limits, recovery, and unusual but plausible user behavior.Votes: 0GitHub stars: 16
- Requirements SpecificationConvert approved product and business intent into precise functional, non-functional, interface, data, and acceptance requirements.Votes: 0GitHub stars: 16
- TraceabilityMaintain requirement-level traceability from source need through decisions, product behavior, acceptance evidence, implementation references, and change history so scope and validation remain auditable.Votes: 0GitHub stars: 16
- Evidence BriefProduce a concise decision brief that presents the research question, strongest evidence, contrary evidence, confidence, implications, and unresolved gaps with citations.Votes: 0GitHub stars: 16
- Fact VerificationVerify consequential factual claims through primary or authoritative sources, exact dates/versions, cross-checks, and context review.Votes: 0GitHub stars: 16
- Literature SynthesisSynthesize multiple papers, reports, standards, and primary sources into a coherent evidence map that preserves differing definitions, methods, and results.Votes: 0GitHub stars: 16
- Research Question FramingConvert a broad question into answerable subquestions, evidence requirements, scope limits, source hierarchy, and stop criteria.Votes: 0GitHub stars: 16
- Source Quality AssessmentAssess a source for authority, proximity, methodology, incentives, currency, completeness, reproducibility, and fit to the specific claim.Votes: 0GitHub stars: 16
- Crm Data GovernanceGovern CRM and revenue-system data through field definitions, ownership, required evidence, deduplication, identity resolution, access, change control, and quality monitoring.Votes: 0GitHub stars: 16
- Pipeline Health ReviewReview pipeline health using stage aging, conversion, coverage, source quality, slippage, loss reasons, capacity, and data completeness without treating booked value as guaranteed.Votes: 0GitHub stars: 16
- Revenue Forecast OperationsProduce an operational revenue forecast by reconciling pipeline evidence, historical conversion/velocity, renewals/expansion, owner commits, timing risk, and scenario ranges.Votes: 0GitHub stars: 16
- Revenue Handoff AutomationDesign reliable automation for marketing-sales-CS handoffs with eligibility rules, enrichment, routing, SLA timers, deduplication, retries, and exception queues.Votes: 0GitHub stars: 16
- Revenue Lifecycle DesignDesign a shared revenue lifecycle from audience/lead through qualification, opportunity, customer, expansion, renewal, and exit with explicit entry/exit rules and ownership.Votes: 0GitHub stars: 16
- Dynamic Behavior AnalysisTest bounded hypotheses about an authorized software artifact through controlled execution, tracing, and instrumentation.Votes: 0GitHub stars: 16
- Protocol Format ReconstructionInfer and validate an undocumented protocol or file format from authorized samples, captures, and implementation evidence.Votes: 0GitHub stars: 16
- Software Artifact TriageTriage an authorized binary, application package, firmware image, or capture into a safe, evidence-preserving analysis plan.Votes: 0GitHub stars: 16
- Static Binary AnalysisReconstruct program structure and behavior from an authorized compiled artifact without executing it.Votes: 0GitHub stars: 16
- Demo ScriptWrite a product demo script that proves one or more capabilities through a realistic user goal, exact setup, visible actions, narration, proof points, transitions, and recovery from likely live-demo failure.Votes: 0GitHub stars: 16