All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Browser Print To Pdf Pagination ValidationUse when a task involves validating page breaks and completeness when exporting a web page to PDF to record the target site and origin, browser and driver version, active account, test or production context, user authorization, data sensitivity, and intended side effects. Use a bounded, reproducible interaction, verify both browser-visible and relevant underlying state, preserve evidence safely, and report uncertainty. Do not reuse profiles, disclose authentication state, or perform external ...Votes: 0GitHub stars: 2
- Browser Qa And Ui VerificationUse when validating a browser-facing feature through live navigation, browser automation, or visual comparison to check rendered behavior, critical user flows, console and network evidence, and responsive states while treating page content as untrusted. Trigger after UI changes or before release; skip for backend-only work.Votes: 0GitHub stars: 2
- Browser Quick Menu And Shortcut State TestUse when a task involves verifying a web application's menu and keyboard shortcut state transitions to record the target site and origin, browser and driver version, active account, test or production context, user authorization, data sensitivity, and intended side effects. Use a bounded, reproducible interaction, verify both browser-visible and relevant underlying state, preserve evidence safely, and report uncertainty. Do not reuse profiles, disclose authentication state, or perform externa...Votes: 0GitHub stars: 2
- Browser Session Tenant Isolation TestUse when a task involves testing that browser automation sessions for separate users or tenants cannot share state to record the target site and origin, browser and driver version, active account, test or production context, user authorization, data sensitivity, and intended side effects. Use a bounded, reproducible interaction, verify both browser-visible and relevant underlying state, preserve evidence safely, and report uncertainty. Do not reuse profiles, disclose authentication state, or ...Votes: 0GitHub stars: 2
- Browser Test Fixture Data IsolationUse when a task involves ensuring browser tests create and clean up only their own test records to record the target site and origin, browser and driver version, active account, test or production context, user authorization, data sensitivity, and intended side effects. Use a bounded, reproducible interaction, verify both browser-visible and relevant underlying state, preserve evidence safely, and report uncertainty. Do not reuse profiles, disclose authentication state, or perform external wr...Votes: 0GitHub stars: 2
- Browser Unsaved Form Recovery TestUse when a task involves testing recovery of an in-progress browser form after refresh, navigation, or session expiry to record the target site and origin, browser and driver version, active account, test or production context, user authorization, data sensitivity, and intended side effects. Use a bounded, reproducible interaction, verify both browser-visible and relevant underlying state, preserve evidence safely, and report uncertainty. Do not reuse profiles, disclose authentication state, ...Votes: 0GitHub stars: 2
- Browser Visual Regression Flake TriageUse when a task involves triaging intermittent screenshot differences in browser-based visual tests to record the target site and origin, browser and driver version, active account, test or production context, user authorization, data sensitivity, and intended side effects. Use a bounded, reproducible interaction, verify both browser-visible and relevant underlying state, preserve evidence safely, and report uncertainty. Do not reuse profiles, disclose authentication state, or perform externa...Votes: 0GitHub stars: 2
- Browser Websocket Reconnect Continuity TestUse when a task involves testing web application state continuity after a browser WebSocket disconnect to record the target site and origin, browser and driver version, active account, test or production context, user authorization, data sensitivity, and intended side effects. Use a bounded, reproducible interaction, verify both browser-visible and relevant underlying state, preserve evidence safely, and report uncertainty. Do not reuse profiles, disclose authentication state, or perform exte...Votes: 0GitHub stars: 2
- Checkpoint Artifact Hash Consistency ValidatorUse when a long-running task resumes after interruption or context compaction to create or update a checkpoint manifest with artifact hashes and statuses. Use the configured search, fetch, read, browser, and test capabilities only when available and authorized. Success criterion: all resumed artifacts match recorded hashes or are revalidated before use. Preserve evidence and a run record, limit rework to three meaningful passes, and obtain approval before externally visible or irreversible wr...Votes: 0GitHub stars: 2
- Cookie Consent Transition Persistence TestUse when a consent banner or privacy preference flow is implemented or changed to create or update a consent-state transition table with storage and UI evidence. Use the configured search, fetch, read, browser, and test capabilities only when available and authorized. Success criterion: accepted, rejected, and customized states match policy without stale banner behavior. Preserve evidence and a run record, limit rework to three meaningful passes, and obtain approval before externally visible ...Votes: 0GitHub stars: 2
- DependabotUse when a task involves reviewing dependency update alerts or Dependabot pull requests for compatibility, security, and release risk to identify the intended outcome, relevant inputs, platform or version, sensitive data, and permission boundary before acting. Use current primary documentation for version-sensitive behavior, produce a reviewable artifact, and verify it against stated criteria. Trigger for planning, implementation, evaluation, or troubleshooting in this focused domain; do not ...Votes: 0GitHub stars: 2
- Dependency Bump Test Matrix Selection ProofUse when a lockfile or package version changes and CI selection is conditional to create or update a dependency-to-codepath-to-test matrix. Use the configured search, fetch, read, browser, and test capabilities only when available and authorized. Success criterion: every affected integration surface has a test or a reasoned exclusion. Preserve evidence and a run record, limit rework to three meaningful passes, and obtain approval before externally visible or irreversible writes.Votes: 0GitHub stars: 2
- Domain Diversity Search Saturation CheckUse when a research set is dominated by one domain, syndication chain, or repeated search result to create or update a source-diversity matrix and a documented stop decision. Use the configured search, fetch, read, browser, and test capabilities only when available and authorized. Success criterion: new searches add independent evidence across relevant source classes or saturation is justified. Preserve evidence and a run record, limit rework to three meaningful passes, and obtain approval be...Votes: 0GitHub stars: 2
- Earliest Causal Test Error TraceUse when a test command produces multiple failures or a cascade of error messages to create or update a timestamped failure trace with primary and downstream symptoms. Use the configured search, fetch, read, browser, and test capabilities only when available and authorized. Success criterion: the proposed root cause explains the earliest failure and reproduces under a focused check. Preserve evidence and a run record, limit rework to three meaningful passes, and obtain approval before externa...Votes: 0GitHub stars: 2
- Environment Parity Failure ReproducerUse when a change passes in one environment but fails in another to create or update an environment-difference matrix and a reproducible command. Use the configured search, fetch, read, browser, and test capabilities only when available and authorized. Success criterion: one identified environment difference predicts the failure or the discrepancy remains unresolved. Preserve evidence and a run record, limit rework to three meaningful passes, and obtain approval before externally visible or i...Votes: 0GitHub stars: 2
- Flaky Test Repeatability ClassifierUse when the same test alternates between pass and fail across runs to create or update a repeatability table stratified by environment and failure signature. Use the configured search, fetch, read, browser, and test capabilities only when available and authorized. Success criterion: the failure pattern is classified with uncertainty and not hidden by reruns. Preserve evidence and a run record, limit rework to three meaningful passes, and obtain approval before externally visible or irreversi...Votes: 0GitHub stars: 2
- Instruments Leak Cycle Evidence CheckUse when a task involves testing whether an object graph remains retained after a feature's expected lifecycle ends to record Swift, Xcode, operating-system, build, and target versions; reproduction steps; data sensitivity; and the permission boundary before acting. Check current Apple or Swift documentation, preserve source and trace provenance, and verify on an owned test target. Do not change signing credentials, publish, notarize, or operate production systems without explicit approval.Votes: 0GitHub stars: 2
- Instruments Memory Allocation Retention AnalysisUse when a task involves separating transient allocation volume from persistent object retention in a native app to record Swift, Xcode, operating-system, build, and target versions; reproduction steps; data sensitivity; and the permission boundary before acting. Check current Apple or Swift documentation, preserve source and trace provenance, and verify on an owned test target. Do not change signing credentials, publish, notarize, or operate production systems without explicit approval.Votes: 0GitHub stars: 2
- Instruments Network Traffic Privacy ReviewUse when a task involves reviewing which network activity occurs during a bounded native app test to record Swift, Xcode, operating-system, build, and target versions; reproduction steps; data sensitivity; and the permission boundary before acting. Check current Apple or Swift documentation, preserve source and trace provenance, and verify on an owned test target. Do not change signing credentials, publish, notarize, or operate production systems without explicit approval.Votes: 0GitHub stars: 2
- Instruments Time Profiler Hotspot Ranking AuditUse when a task involves ranking CPU hotspots from a native app trace without overstating sample precision to record Swift, Xcode, operating-system, build, and target versions; reproduction steps; data sensitivity; and the permission boundary before acting. Check current Apple or Swift documentation, preserve source and trace provenance, and verify on an owned test target. Do not change signing credentials, publish, notarize, or operate production systems without explicit approval.Votes: 0GitHub stars: 2
- Instruments Trace Capture Scope PlanUse when a task involves planning a bounded Instruments capture for a native Apple app performance question to record Swift, Xcode, operating-system, build, and target versions; reproduction steps; data sensitivity; and the permission boundary before acting. Check current Apple or Swift documentation, preserve source and trace provenance, and verify on an owned test target. Do not change signing credentials, publish, notarize, or operate production systems without explicit approval.Votes: 0GitHub stars: 2
- Ios Memory Pressure Termination InvestigationUse when a task involves triaging an iOS app termination associated with memory pressure to record Swift, Xcode, operating-system, build, and target versions; reproduction steps; data sensitivity; and the permission boundary before acting. Check current Apple or Swift documentation, preserve source and trace provenance, and verify on an owned test target. Do not change signing credentials, publish, notarize, or operate production systems without explicit approval.Votes: 0GitHub stars: 2
- Javascript Testing Patterns Capability Surface MapUse when the actual capability boundary of JavaScript and TypeScript testing needs to be distinguished from assumptions. Produce a capability map for JavaScript and TypeScript testing covering the requested behavior, verified support, exclusions, and unknowns. Success means each in-scope capability is tied to local configuration, a version-matched authoritative reference, or an observed non-production result, and all unknowns remain explicit. The review is bounded to test isolation, async com...Votes: 0GitHub stars: 2
- Javascript Testing Patterns Change Impact AssessmentUse when a proposed JavaScript and TypeScript testing version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for JavaScript and TypeScript testing with baseline, affected dependencies, validation needs, and recovery boundary. Success means affected dependencies and compatibility assumptions are evidenced, unknown consumers are named as unknown, and no migration or rollout is implied. The review is bounded to test isolation, async c...Votes: 0GitHub stars: 2
- Javascript Testing Patterns Failure Triage RecordUse when a reproducible JavaScript and TypeScript testing symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for JavaScript and TypeScript testing with symptom, environment, evidence, hypothesis, and next safe check. Success means the diagnosis distinguishes observation from inference, each proposed check is reversible and scoped, and unresolved causes remain open. The review is bounded to test isolation, async completion, fixture ownership, mock bou...Votes: 0GitHub stars: 2
- Javascript Testing Patterns Input Output ContractUse when the accepted inputs or produced outputs for JavaScript and TypeScript testing need a checkable boundary. Produce an input/output contract for JavaScript and TypeScript testing with types, required fields, exclusions, and representative approved fixtures. Success means the contract names its source and version, boundary cases are visible, and no private or unapproved payload is needed to explain the result. The review is bounded to test isolation, async completion, fixture ownership, ...Votes: 0GitHub stars: 2
- Javascript Testing Patterns Integration Parity TraceUse when JavaScript and TypeScript testing exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for JavaScript and TypeScript testing showing source, transformation, destination, and observed result. Success means each material field or state transition has a traceable mapping and observed mismatches are separated from assumptions. The review is bounded to test isolation, async completion, fixture ownership, mock boundaries, ...Votes: 0GitHub stars: 2
- Javascript Testing Patterns Performance EnvelopeUse when JavaScript and TypeScript testing must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for JavaScript and TypeScript testing with test conditions, baseline, observed range, and limitations. Success means conditions and measurements are reproducible, the comparison uses the stated budget, and limitations or resource costs are visible. The review is bounded to test isolation, async completion, fixture o...Votes: 0GitHub stars: 2
- Javascript Testing Patterns Permission Boundary ReviewUse when JavaScript and TypeScript testing may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for JavaScript and TypeScript testing showing identity, requested capability, data scope, and approval gate. Success means every sensitive capability has a named authorization boundary, unnecessary data and privileges are called out, and no action is treated as approved by implication. The review is bounded to test isolation, async completion...Votes: 0GitHub stars: 2
- Javascript Testing Patterns Release Handoff RecordUse when a JavaScript and TypeScript testing review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for JavaScript and TypeScript testing with version, evidence, open issues, approval state, and safe next step. Success means the receiver can distinguish verified facts, proposals, approvals, and unknowns, and no publication, deployment, write, or contact is claimed unless independently confirmed. The review is bounded to test isolation, async com...Votes: 0GitHub stars: 2
- Javascript Testing Patterns Reproducibility Fixture PlanUse when a JavaScript and TypeScript testing result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for JavaScript and TypeScript testing defining fixture identity, environment, expected observations, and cleanup boundary. Success means another reviewer can identify the fixture and environment, distinguish expected from observed behavior, and repeat the check without an unapproved external effect. The review is bounded ...Votes: 0GitHub stars: 2
- Javascript Testing Patterns Version CompatibilityUse when a JavaScript and TypeScript testing integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for JavaScript and TypeScript testing with exact versions, supported combinations, and open questions. Success means the tested version tuple is explicit, each compatibility claim has a dated source or local result, and unsupported combinations are not presented as working. The review is bounded to test isolation, asyn...Votes: 0GitHub stars: 2
- Json Output Schema Roundtrip Invariant TestUse when an agent or service emits JSON consumed by another component to create or update a round-trip fixture set with invariant results. Use the configured search, fetch, read, browser, and test capabilities only when available and authorized. Success criterion: normalized input and output preserve required fields and meanings. Preserve evidence and a run record, limit rework to three meaningful passes, and obtain approval before externally visible or irreversible writes.Votes: 0GitHub stars: 2
- Macos App Sandbox File Access Boundary TestUse when a task involves checking sandboxed file access for a defined macOS app feature to record Swift, Xcode, operating-system, build, and target versions; reproduction steps; data sensitivity; and the permission boundary before acting. Check current Apple or Swift documentation, preserve source and trace provenance, and verify on an owned test target. Do not change signing credentials, publish, notarize, or operate production systems without explicit approval.Votes: 0GitHub stars: 2
- Macos Crash Diagnostic Log RedactionUse when a task involves redacting sensitive information from crash and diagnostic logs before sharing to record Swift, Xcode, operating-system, build, and target versions; reproduction steps; data sensitivity; and the permission boundary before acting. Check current Apple or Swift documentation, preserve source and trace provenance, and verify on an owned test target. Do not change signing credentials, publish, notarize, or operate production systems without explicit approval.Votes: 0GitHub stars: 2
- Macos Crash Report Symbolication ReadinessUse when a task involves checking whether a macOS crash report can be symbolicated safely and accurately to record Swift, Xcode, operating-system, build, and target versions; reproduction steps; data sensitivity; and the permission boundary before acting. Check current Apple or Swift documentation, preserve source and trace provenance, and verify on an owned test target. Do not change signing credentials, publish, notarize, or operate production systems without explicit approval.Votes: 0GitHub stars: 2
- Macos Installer Package Content InventoryUse when a task involves checking the files and scripts included in a macOS installer package to record Swift, Xcode, operating-system, build, and target versions; reproduction steps; data sensitivity; and the permission boundary before acting. Check current Apple or Swift documentation, preserve source and trace provenance, and verify on an owned test target. Do not change signing credentials, publish, notarize, or operate production systems without explicit approval.Votes: 0GitHub stars: 2
- Macos Notarization Submission Evidence AuditUse when a task involves preparing a traceable evidence record for a notarization submission to record Swift, Xcode, operating-system, build, and target versions; reproduction steps; data sensitivity; and the permission boundary before acting. Check current Apple or Swift documentation, preserve source and trace provenance, and verify on an owned test target. Do not change signing credentials, publish, notarize, or operate production systems without explicit approval.Votes: 0GitHub stars: 2
- Macos Notarization Ticket Stapling VerificationUse when a task involves verifying that a notarization ticket is attached to the intended macOS artifact to record Swift, Xcode, operating-system, build, and target versions; reproduction steps; data sensitivity; and the permission boundary before acting. Check current Apple or Swift documentation, preserve source and trace provenance, and verify on an owned test target. Do not change signing credentials, publish, notarize, or operate production systems without explicit approval.Votes: 0GitHub stars: 2
- Macos Privacy Manifest Consistency CheckUse when a task involves checking consistency among an app's privacy manifest, included SDKs, and collected-data claims to record Swift, Xcode, operating-system, build, and target versions; reproduction steps; data sensitivity; and the permission boundary before acting. Check current Apple or Swift documentation, preserve source and trace provenance, and verify on an owned test target. Do not change signing credentials, publish, notarize, or operate production systems without explicit approval.Votes: 0GitHub stars: 2
- Macos Tcc Permission Attribution TestUse when a task involves testing which process receives a macOS privacy permission prompt for an approved app workflow to record Swift, Xcode, operating-system, build, and target versions; reproduction steps; data sensitivity; and the permission boundary before acting. Check current Apple or Swift documentation, preserve source and trace provenance, and verify on an owned test target. Do not change signing credentials, publish, notarize, or operate production systems without explicit approval.Votes: 0GitHub stars: 2
- Macos Update Feed Integrity ReviewUse when a task involves reviewing an app update feed for version, channel, and artifact consistency to record Swift, Xcode, operating-system, build, and target versions; reproduction steps; data sensitivity; and the permission boundary before acting. Check current Apple or Swift documentation, preserve source and trace provenance, and verify on an owned test target. Do not change signing credentials, publish, notarize, or operate production systems without explicit approval.Votes: 0GitHub stars: 2
- Macos Update Payload Signature Negative TestUse when a task involves testing that a macOS app update client rejects altered or incorrectly signed update payloads to record Swift, Xcode, operating-system, build, and target versions; reproduction steps; data sensitivity; and the permission boundary before acting. Check current Apple or Swift documentation, preserve source and trace provenance, and verify on an owned test target. Do not change signing credentials, publish, notarize, or operate production systems without explicit approval.Votes: 0GitHub stars: 2
- Minimal Test Reproducer SculptorUse when a large fixture, request, or state sequence obscures a test defect to create or update a minimized reproduction and a record of removed dimensions. Use the configured search, fetch, read, browser, and test capabilities only when available and authorized. Success criterion: the reduced case still fails for the same reason and the original case remains available. Preserve evidence and a run record, limit rework to three meaningful passes, and obtain approval before externally visible o...Votes: 0GitHub stars: 2
- Performance Benchmarking And Regression DetectionUse when measuring application, service, build, or browser performance; investigating a slowdown; or comparing a change against a baseline to define representative workloads, environmental controls, metrics, and acceptable variance before optimizing. Trigger for performance investigations and regression gates, not speculative micro-optimization.Votes: 0GitHub stars: 2
- Pull Request Test Failure Change AttributionUse when a CI test fails after a branch update to create or update a failure-attribution note with base comparison and evidence. Use the configured search, fetch, read, browser, and test capabilities only when available and authorized. Success criterion: the failure reproduces on the branch and is distinguishable from the base result. Preserve evidence and a run record, limit rework to three meaningful passes, and obtain approval before externally visible or irreversible writes.Votes: 0GitHub stars: 2
- Release Candidate Evidence Bundle Hash AuditUse when a release candidate is assembled from multiple build and verification outputs to create or update a bundle manifest with artifact hashes, source revision, and check status. Use the configured search, fetch, read, browser, and test capabilities only when available and authorized. Success criterion: all included artifacts trace to the same intended commit and no required check is missing. Preserve evidence and a run record, limit rework to three meaningful passes, and obtain approval b...Votes: 0GitHub stars: 2
- Release Note Bullet To Change Set TraceUse when a release note is prepared from a branch, tag, or pull-request set to create or update a release-note trace table with change links and audience impact. Use the configured search, fetch, read, browser, and test capabilities only when available and authorized. Success criterion: each bullet is supported by a merged or approved change and describes its effect accurately. Preserve evidence and a run record, limit rework to three meaningful passes, and obtain approval before externally v...Votes: 0GitHub stars: 2
- Release Readiness And RollbackUse when preparing a software change for a staged rollout, production release, or deployment decision to check required quality gates, compatibility, operational signals, approvals, and a credible rollback or recovery path. Trigger for release planning and go/no-go reviews; this skill does not itself authorize publishing or deployment.Votes: 0GitHub stars: 2
- Repo Native Test Command DiscoveryUse when test commands are unclear or a generic default may target the wrong stack to create or update a validation plan naming focused, regression, and full-suite commands. Use the configured search, fetch, read, browser, and test capabilities only when available and authorized. Success criterion: each command is justified by project manifests or CI configuration and has a known scope. Preserve evidence and a run record, limit rework to three meaningful passes, and obtain approval before ext...Votes: 0GitHub stars: 2