All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Testlab Browser Interaction Testing Flaky Failures Option Comparison MatrixUse when several tools, designs, methods, or workflows could satisfy the same need for Software testing and release assurance: browser interaction testing for flaky failures. Produce an evidence-backed option-comparison matrix with scope, versions, decisions, and evidence for this task-specific gate: Collect repeated outcomes with a stable seed/environment and retain every failure trace for triage. Success means options are compared on user-approved criteria with uncertainty and trade-offs sh...Votes: 0GitHub stars: 2
- Testlab Browser Interaction Testing Flaky Failures Requirements And Decision BriefUse when a request must be converted into testable constraints and an owned decision for Software testing and release assurance: browser interaction testing for flaky failures. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: Collect repeated outcomes with a stable seed/environment and retain every failure trace for triage. Success means requirements have priorities, evidence, owners, and measurable acceptance cond...Votes: 0GitHub stars: 2
- Testlab Browser Interaction Testing Flaky Failures Scope And Baseline RecordUse when the work needs a verified goal, authorized boundary, and starting state for Software testing and release assurance: browser interaction testing for flaky failures. Produce a scope-and-baseline record with scope, versions, decisions, and evidence for this task-specific gate: Collect repeated outcomes with a stable seed/environment and retain every failure trace for triage. Success means the owner, constraints, baseline, and acceptance signal are explicit. Use permissioned inputs, pres...Votes: 0GitHub stars: 2
- Testlab Browser Interaction Testing Flaky Failures Security Rights And Safety ReviewUse when the workflow could affect people, systems, confidential data, intellectual property, or physical outcomes for Software testing and release assurance: browser interaction testing for flaky failures. Produce a scoped risk-and-control review with scope, versions, decisions, and evidence for this task-specific gate: Collect repeated outcomes with a stable seed/environment and retain every failure trace for triage. Success means the review names relevant hazards, permissions, controls, ev...Votes: 0GitHub stars: 2
- Testlab Browser Interaction Testing Flaky Failures Source Research And Provenance LedgerUse when a decision depends on current, source-grounded information for Software testing and release assurance: browser interaction testing for flaky failures. Produce a source-and-claim ledger with scope, versions, decisions, and evidence for this task-specific gate: Collect repeated outcomes with a stable seed/environment and retain every failure trace for triage. Success means material claims are linked to current primary sources with dates and limitations. Use permissioned inputs, preserv...Votes: 0GitHub stars: 2
- Testlab Browser Interaction Testing Flaky Failures Verification And Acceptance Test PlanUse when a result must be checked against explicit behavior, safety, or quality conditions for Software testing and release assurance: browser interaction testing for flaky failures. Produce a risk-weighted verification plan with saved evidence with scope, versions, decisions, and evidence for this task-specific gate: Collect repeated outcomes with a stable seed/environment and retain every failure trace for triage. Success means each critical requirement maps to a reproducible check and a tr...Votes: 0GitHub stars: 2
- Testlab Browser Interaction Testing Legacy Code Build Configuration RunbookUse when an authorized implementation needs repeatable steps and a visible change boundary for Software testing and release assurance: browser interaction testing for legacy code. Produce a bounded build or configuration runbook with scope, versions, decisions, and evidence for this task-specific gate: Map existing behavior before refactoring; use characterization tests for unknown behavior rather than assuming it is accidental. Success means the prepared result is reproducible, reviewable, a...Votes: 0GitHub stars: 2
- Testlab Browser Interaction Testing Legacy Code Design BlueprintUse when a solution needs a coherent structure before implementation or production for Software testing and release assurance: browser interaction testing for legacy code. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: Map existing behavior before refactoring; use characterization tests for unknown behavior rather than assuming it is accidental. Success means interfaces, dependencies, constraints, and review points are testable bef...Votes: 0GitHub stars: 2
- Testlab Browser Interaction Testing Legacy Code Failure Triage And RecoveryUse when an unexpected result needs diagnosis without widening risk or losing evidence for Software testing and release assurance: browser interaction testing for legacy code. Produce a failure-triage record and reversible recovery plan with scope, versions, decisions, and evidence for this task-specific gate: Map existing behavior before refactoring; use characterization tests for unknown behavior rather than assuming it is accidental. Success means the failure is bounded by observations, on...Votes: 0GitHub stars: 2
- Testlab Browser Interaction Testing Legacy Code Measured Improvement And HandoffUse when a measured result or recurring failure suggests a change worth testing and handing to an owner for Software testing and release assurance: browser interaction testing for legacy code. Produce a versioned improvement proposal and handoff packet with scope, versions, decisions, and evidence for this task-specific gate: Map existing behavior before refactoring; use characterization tests for unknown behavior rather than assuming it is accidental. Success means the proposed change is com...Votes: 0GitHub stars: 2
- Testlab Browser Interaction Testing Legacy Code Option Comparison MatrixUse when several tools, designs, methods, or workflows could satisfy the same need for Software testing and release assurance: browser interaction testing for legacy code. Produce an evidence-backed option-comparison matrix with scope, versions, decisions, and evidence for this task-specific gate: Map existing behavior before refactoring; use characterization tests for unknown behavior rather than assuming it is accidental. Success means options are compared on user-approved criteria with unc...Votes: 0GitHub stars: 2
- Testlab Browser Interaction Testing Legacy Code Requirements And Decision BriefUse when a request must be converted into testable constraints and an owned decision for Software testing and release assurance: browser interaction testing for legacy code. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: Map existing behavior before refactoring; use characterization tests for unknown behavior rather than assuming it is accidental. Success means requirements have priorities, evidence, owners, and ...Votes: 0GitHub stars: 2
- Testlab Browser Interaction Testing Legacy Code Scope And Baseline RecordUse when the work needs a verified goal, authorized boundary, and starting state for Software testing and release assurance: browser interaction testing for legacy code. Produce a scope-and-baseline record with scope, versions, decisions, and evidence for this task-specific gate: Map existing behavior before refactoring; use characterization tests for unknown behavior rather than assuming it is accidental. Success means the owner, constraints, baseline, and acceptance signal are explicit. Use...Votes: 0GitHub stars: 2
- Testlab Browser Interaction Testing Legacy Code Security Rights And Safety ReviewUse when the workflow could affect people, systems, confidential data, intellectual property, or physical outcomes for Software testing and release assurance: browser interaction testing for legacy code. Produce a scoped risk-and-control review with scope, versions, decisions, and evidence for this task-specific gate: Map existing behavior before refactoring; use characterization tests for unknown behavior rather than assuming it is accidental. Success means the review names relevant hazards,...Votes: 0GitHub stars: 2
- Testlab Browser Interaction Testing Legacy Code Source Research And Provenance LedgerUse when a decision depends on current, source-grounded information for Software testing and release assurance: browser interaction testing for legacy code. Produce a source-and-claim ledger with scope, versions, decisions, and evidence for this task-specific gate: Map existing behavior before refactoring; use characterization tests for unknown behavior rather than assuming it is accidental. Success means material claims are linked to current primary sources with dates and limitations. Use pe...Votes: 0GitHub stars: 2
- Testlab Browser Interaction Testing Legacy Code Verification And Acceptance Test PlanUse when a result must be checked against explicit behavior, safety, or quality conditions for Software testing and release assurance: browser interaction testing for legacy code. Produce a risk-weighted verification plan with saved evidence with scope, versions, decisions, and evidence for this task-specific gate: Map existing behavior before refactoring; use characterization tests for unknown behavior rather than assuming it is accidental. Success means each critical requirement maps to a r...Votes: 0GitHub stars: 2
- Testlab Browser Interaction Testing Regression Coverage Build Configuration RunbookUse when an authorized implementation needs repeatable steps and a visible change boundary for Software testing and release assurance: browser interaction testing for regression coverage. Produce a bounded build or configuration runbook with scope, versions, decisions, and evidence for this task-specific gate: Demonstrate that the test fails on the known regression and passes on the corrected behavior. Success means the prepared result is reproducible, reviewable, and within the approved scop...Votes: 0GitHub stars: 2
- Testlab Browser Interaction Testing Regression Coverage Design BlueprintUse when a solution needs a coherent structure before implementation or production for Software testing and release assurance: browser interaction testing for regression coverage. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: Demonstrate that the test fails on the known regression and passes on the corrected behavior. Success means interfaces, dependencies, constraints, and review points are testable before build. Use permissioned...Votes: 0GitHub stars: 2
- Testlab Browser Interaction Testing Regression Coverage Failure Triage And RecoveryUse when an unexpected result needs diagnosis without widening risk or losing evidence for Software testing and release assurance: browser interaction testing for regression coverage. Produce a failure-triage record and reversible recovery plan with scope, versions, decisions, and evidence for this task-specific gate: Demonstrate that the test fails on the known regression and passes on the corrected behavior. Success means the failure is bounded by observations, one testable hypothesis, and ...Votes: 0GitHub stars: 2
- Testlab Browser Interaction Testing Regression Coverage Measured Improvement And HandoffUse when a measured result or recurring failure suggests a change worth testing and handing to an owner for Software testing and release assurance: browser interaction testing for regression coverage. Produce a versioned improvement proposal and handoff packet with scope, versions, decisions, and evidence for this task-specific gate: Demonstrate that the test fails on the known regression and passes on the corrected behavior. Success means the proposed change is compared with a baseline, regr...Votes: 0GitHub stars: 2
- Testlab Browser Interaction Testing Regression Coverage Option Comparison MatrixUse when several tools, designs, methods, or workflows could satisfy the same need for Software testing and release assurance: browser interaction testing for regression coverage. Produce an evidence-backed option-comparison matrix with scope, versions, decisions, and evidence for this task-specific gate: Demonstrate that the test fails on the known regression and passes on the corrected behavior. Success means options are compared on user-approved criteria with uncertainty and trade-offs sho...Votes: 0GitHub stars: 2
- Testlab Browser Interaction Testing Regression Coverage Requirements And Decision BriefUse when a request must be converted into testable constraints and an owned decision for Software testing and release assurance: browser interaction testing for regression coverage. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: Demonstrate that the test fails on the known regression and passes on the corrected behavior. Success means requirements have priorities, evidence, owners, and measurable acceptance condi...Votes: 0GitHub stars: 2
- Testlab Browser Interaction Testing Regression Coverage Scope And Baseline RecordUse when the work needs a verified goal, authorized boundary, and starting state for Software testing and release assurance: browser interaction testing for regression coverage. Produce a scope-and-baseline record with scope, versions, decisions, and evidence for this task-specific gate: Demonstrate that the test fails on the known regression and passes on the corrected behavior. Success means the owner, constraints, baseline, and acceptance signal are explicit. Use permissioned inputs, prese...Votes: 0GitHub stars: 2
- Testlab Browser Interaction Testing Regression Coverage Security Rights And Safety ReviewUse when the workflow could affect people, systems, confidential data, intellectual property, or physical outcomes for Software testing and release assurance: browser interaction testing for regression coverage. Produce a scoped risk-and-control review with scope, versions, decisions, and evidence for this task-specific gate: Demonstrate that the test fails on the known regression and passes on the corrected behavior. Success means the review names relevant hazards, permissions, controls, evi...Votes: 0GitHub stars: 2
- Testlab Browser Interaction Testing Regression Coverage Source Research And Provenance LedgerUse when a decision depends on current, source-grounded information for Software testing and release assurance: browser interaction testing for regression coverage. Produce a source-and-claim ledger with scope, versions, decisions, and evidence for this task-specific gate: Demonstrate that the test fails on the known regression and passes on the corrected behavior. Success means material claims are linked to current primary sources with dates and limitations. Use permissioned inputs, preserve...Votes: 0GitHub stars: 2
- Testlab Browser Interaction Testing Regression Coverage Verification And Acceptance Test PlanUse when a result must be checked against explicit behavior, safety, or quality conditions for Software testing and release assurance: browser interaction testing for regression coverage. Produce a risk-weighted verification plan with saved evidence with scope, versions, decisions, and evidence for this task-specific gate: Demonstrate that the test fails on the known regression and passes on the corrected behavior. Success means each critical requirement maps to a reproducible check and a tru...Votes: 0GitHub stars: 2
- Testlab Browser Interaction Testing Release Candidates Build Configuration RunbookUse when an authorized implementation needs repeatable steps and a visible change boundary for Software testing and release assurance: browser interaction testing for release candidates. Produce a bounded build or configuration runbook with scope, versions, decisions, and evidence for this task-specific gate: Use a fixed candidate build and attach environment identity, test results, open risks, and rollback evidence. Success means the prepared result is reproducible, reviewable, and within th...Votes: 0GitHub stars: 2
- Testlab Browser Interaction Testing Release Candidates Design BlueprintUse when a solution needs a coherent structure before implementation or production for Software testing and release assurance: browser interaction testing for release candidates. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: Use a fixed candidate build and attach environment identity, test results, open risks, and rollback evidence. Success means interfaces, dependencies, constraints, and review points are testable before build. U...Votes: 0GitHub stars: 2
- Testlab Browser Interaction Testing Release Candidates Failure Triage And RecoveryUse when an unexpected result needs diagnosis without widening risk or losing evidence for Software testing and release assurance: browser interaction testing for release candidates. Produce a failure-triage record and reversible recovery plan with scope, versions, decisions, and evidence for this task-specific gate: Use a fixed candidate build and attach environment identity, test results, open risks, and rollback evidence. Success means the failure is bounded by observations, one testable h...Votes: 0GitHub stars: 2
- Testlab Browser Interaction Testing Release Candidates Measured Improvement And HandoffUse when a measured result or recurring failure suggests a change worth testing and handing to an owner for Software testing and release assurance: browser interaction testing for release candidates. Produce a versioned improvement proposal and handoff packet with scope, versions, decisions, and evidence for this task-specific gate: Use a fixed candidate build and attach environment identity, test results, open risks, and rollback evidence. Success means the proposed change is compared with a...Votes: 0GitHub stars: 2
- Testlab Browser Interaction Testing Release Candidates Option Comparison MatrixUse when several tools, designs, methods, or workflows could satisfy the same need for Software testing and release assurance: browser interaction testing for release candidates. Produce an evidence-backed option-comparison matrix with scope, versions, decisions, and evidence for this task-specific gate: Use a fixed candidate build and attach environment identity, test results, open risks, and rollback evidence. Success means options are compared on user-approved criteria with uncertainty and...Votes: 0GitHub stars: 2
- Testlab Browser Interaction Testing Release Candidates Requirements And Decision BriefUse when a request must be converted into testable constraints and an owned decision for Software testing and release assurance: browser interaction testing for release candidates. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: Use a fixed candidate build and attach environment identity, test results, open risks, and rollback evidence. Success means requirements have priorities, evidence, owners, and measurable a...Votes: 0GitHub stars: 2
- Testlab Browser Interaction Testing Release Candidates Scope And Baseline RecordUse when the work needs a verified goal, authorized boundary, and starting state for Software testing and release assurance: browser interaction testing for release candidates. Produce a scope-and-baseline record with scope, versions, decisions, and evidence for this task-specific gate: Use a fixed candidate build and attach environment identity, test results, open risks, and rollback evidence. Success means the owner, constraints, baseline, and acceptance signal are explicit. Use permissione...Votes: 0GitHub stars: 2
- Testlab Browser Interaction Testing Release Candidates Security Rights And Safety ReviewUse when the workflow could affect people, systems, confidential data, intellectual property, or physical outcomes for Software testing and release assurance: browser interaction testing for release candidates. Produce a scoped risk-and-control review with scope, versions, decisions, and evidence for this task-specific gate: Use a fixed candidate build and attach environment identity, test results, open risks, and rollback evidence. Success means the review names relevant hazards, permissions...Votes: 0GitHub stars: 2
- Testlab Browser Interaction Testing Release Candidates Source Research And Provenance LedgerUse when a decision depends on current, source-grounded information for Software testing and release assurance: browser interaction testing for release candidates. Produce a source-and-claim ledger with scope, versions, decisions, and evidence for this task-specific gate: Use a fixed candidate build and attach environment identity, test results, open risks, and rollback evidence. Success means material claims are linked to current primary sources with dates and limitations. Use permissioned i...Votes: 0GitHub stars: 2
- Testlab Browser Interaction Testing Release Candidates Verification And Acceptance Test PlanUse when a result must be checked against explicit behavior, safety, or quality conditions for Software testing and release assurance: browser interaction testing for release candidates. Produce a risk-weighted verification plan with saved evidence with scope, versions, decisions, and evidence for this task-specific gate: Use a fixed candidate build and attach environment identity, test results, open risks, and rollback evidence. Success means each critical requirement maps to a reproducible ...Votes: 0GitHub stars: 2
- Testlab Browser Interaction Testing Test Isolation Build Configuration RunbookUse when an authorized implementation needs repeatable steps and a visible change boundary for Software testing and release assurance: browser interaction testing for test isolation. Produce a bounded build or configuration runbook with scope, versions, decisions, and evidence for this task-specific gate: Ensure tests cannot leak files, sockets, credentials, shared state, or nondeterministic ordering into neighboring tests. Success means the prepared result is reproducible, reviewable, and wi...Votes: 0GitHub stars: 2
- Testlab Browser Interaction Testing Test Isolation Design BlueprintUse when a solution needs a coherent structure before implementation or production for Software testing and release assurance: browser interaction testing for test isolation. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: Ensure tests cannot leak files, sockets, credentials, shared state, or nondeterministic ordering into neighboring tests. Success means interfaces, dependencies, constraints, and review points are testable before b...Votes: 0GitHub stars: 2
- Testlab Browser Interaction Testing Test Isolation Failure Triage And RecoveryUse when an unexpected result needs diagnosis without widening risk or losing evidence for Software testing and release assurance: browser interaction testing for test isolation. Produce a failure-triage record and reversible recovery plan with scope, versions, decisions, and evidence for this task-specific gate: Ensure tests cannot leak files, sockets, credentials, shared state, or nondeterministic ordering into neighboring tests. Success means the failure is bounded by observations, one tes...Votes: 0GitHub stars: 2
- Testlab Browser Interaction Testing Test Isolation Measured Improvement And HandoffUse when a measured result or recurring failure suggests a change worth testing and handing to an owner for Software testing and release assurance: browser interaction testing for test isolation. Produce a versioned improvement proposal and handoff packet with scope, versions, decisions, and evidence for this task-specific gate: Ensure tests cannot leak files, sockets, credentials, shared state, or nondeterministic ordering into neighboring tests. Success means the proposed change is compared...Votes: 0GitHub stars: 2
- Testlab Browser Interaction Testing Test Isolation Option Comparison MatrixUse when several tools, designs, methods, or workflows could satisfy the same need for Software testing and release assurance: browser interaction testing for test isolation. Produce an evidence-backed option-comparison matrix with scope, versions, decisions, and evidence for this task-specific gate: Ensure tests cannot leak files, sockets, credentials, shared state, or nondeterministic ordering into neighboring tests. Success means options are compared on user-approved criteria with uncertai...Votes: 0GitHub stars: 2
- Testlab Browser Interaction Testing Test Isolation Requirements And Decision BriefUse when a request must be converted into testable constraints and an owned decision for Software testing and release assurance: browser interaction testing for test isolation. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: Ensure tests cannot leak files, sockets, credentials, shared state, or nondeterministic ordering into neighboring tests. Success means requirements have priorities, evidence, owners, and measu...Votes: 0GitHub stars: 2
- Testlab Browser Interaction Testing Test Isolation Scope And Baseline RecordUse when the work needs a verified goal, authorized boundary, and starting state for Software testing and release assurance: browser interaction testing for test isolation. Produce a scope-and-baseline record with scope, versions, decisions, and evidence for this task-specific gate: Ensure tests cannot leak files, sockets, credentials, shared state, or nondeterministic ordering into neighboring tests. Success means the owner, constraints, baseline, and acceptance signal are explicit. Use perm...Votes: 0GitHub stars: 2
- Testlab Browser Interaction Testing Test Isolation Security Rights And Safety ReviewUse when the workflow could affect people, systems, confidential data, intellectual property, or physical outcomes for Software testing and release assurance: browser interaction testing for test isolation. Produce a scoped risk-and-control review with scope, versions, decisions, and evidence for this task-specific gate: Ensure tests cannot leak files, sockets, credentials, shared state, or nondeterministic ordering into neighboring tests. Success means the review names relevant hazards, perm...Votes: 0GitHub stars: 2
- Testlab Browser Interaction Testing Test Isolation Source Research And Provenance LedgerUse when a decision depends on current, source-grounded information for Software testing and release assurance: browser interaction testing for test isolation. Produce a source-and-claim ledger with scope, versions, decisions, and evidence for this task-specific gate: Ensure tests cannot leak files, sockets, credentials, shared state, or nondeterministic ordering into neighboring tests. Success means material claims are linked to current primary sources with dates and limitations. Use permiss...Votes: 0GitHub stars: 2
- Testlab Browser Interaction Testing Test Isolation Verification And Acceptance Test PlanUse when a result must be checked against explicit behavior, safety, or quality conditions for Software testing and release assurance: browser interaction testing for test isolation. Produce a risk-weighted verification plan with saved evidence with scope, versions, decisions, and evidence for this task-specific gate: Ensure tests cannot leak files, sockets, credentials, shared state, or nondeterministic ordering into neighboring tests. Success means each critical requirement maps to a reprod...Votes: 0GitHub stars: 2
- Testlab Browser Interaction Testing Version Migrations Build Configuration RunbookUse when an authorized implementation needs repeatable steps and a visible change boundary for Software testing and release assurance: browser interaction testing for version migrations. Produce a bounded build or configuration runbook with scope, versions, decisions, and evidence for this task-specific gate: Verify forward and recovery paths on disposable data, including compatibility and partial-failure behavior. Success means the prepared result is reproducible, reviewable, and within the ...Votes: 0GitHub stars: 2
- Testlab Browser Interaction Testing Version Migrations Design BlueprintUse when a solution needs a coherent structure before implementation or production for Software testing and release assurance: browser interaction testing for version migrations. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: Verify forward and recovery paths on disposable data, including compatibility and partial-failure behavior. Success means interfaces, dependencies, constraints, and review points are testable before build. Use...Votes: 0GitHub stars: 2
- Testlab Browser Interaction Testing Version Migrations Failure Triage And RecoveryUse when an unexpected result needs diagnosis without widening risk or losing evidence for Software testing and release assurance: browser interaction testing for version migrations. Produce a failure-triage record and reversible recovery plan with scope, versions, decisions, and evidence for this task-specific gate: Verify forward and recovery paths on disposable data, including compatibility and partial-failure behavior. Success means the failure is bounded by observations, one testable hyp...Votes: 0GitHub stars: 2
- Testlab Browser Interaction Testing Version Migrations Measured Improvement And HandoffUse when a measured result or recurring failure suggests a change worth testing and handing to an owner for Software testing and release assurance: browser interaction testing for version migrations. Produce a versioned improvement proposal and handoff packet with scope, versions, decisions, and evidence for this task-specific gate: Verify forward and recovery paths on disposable data, including compatibility and partial-failure behavior. Success means the proposed change is compared with a b...Votes: 0GitHub stars: 2