All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Aas Devtools Monorepo Change Scope Exception Triage QueueUse when the monorepo change impact scoping workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the package impact map with evidence, owner, and next action. Success means every exception has a severity rationale, source, owner or explicit unassigned state, and a bounded next step; affected packages and required checks are justified from the graph. Use configured search, fetch, read, browser, test, and write capabilities only when re...Votes: 0GitHub stars: 2
- Aas Devtools Monorepo Change Scope Recovery Readiness DrillUse when the monorepo change impact scoping workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the package impact map with starting state, test, and observed outcome. Success means the dry-run or approved non-production drill meets the predeclared recovery target and leaves the baseline intact; affected packages and required checks are justified from the graph. Use configured search, fetch, read, browser, test, and write capabilities o...Votes: 0GitHub stars: 2
- Aas Devtools Monorepo Change Scope Scenario Sensitivity MatrixUse when the monorepo change impact scoping team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the package impact map with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; affected packages and required checks are justified from the graph. Use configured search, fetch, read, browser, test, and write capabilities only when relevant...Votes: 0GitHub stars: 2
- Aas Devtools Monorepo Change Scope Scope Intake GateUse when a new monorepo change impact scoping request needs a bounded work scope to produce a scoped intake card for the package impact map. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; affected packages and required checks are justified from the graph. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focused passes, and seek...Votes: 0GitHub stars: 2
- Aas Devtools Monorepo Change Scope Source Provenance LedgerUse when a decision about monorepo change impact scoping depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the package impact map. Success means each material claim has a source, version/date, location, and confidence note; affected packages and required checks are justified from the graph. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to th...Votes: 0GitHub stars: 2
- Aas Devtools Monorepo Change Scope Threshold Rule CheckUse when a monorepo change impact scoping decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the package impact map showing source, units, boundary case, and outcome. Success means the rule source and effective date are verified, units and scope match, and borderline cases are flagged rather than auto-approved; affected packages and required checks are justified from the graph. Use configured search, fetch, read, browser, test, and write capabi...Votes: 0GitHub stars: 2
- Aas Devtools Workspace Bootstrap Approval Evidence PacketUse when a local developer workspace bootstrap result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the clean-workspace readiness checklist containing options, evidence, risks, and open questions. Success means the decision owner, requested decision, source evidence, alternatives, uncertainty, and consequence of no action are all visible; a fresh environment reaches the declared smoke test without undocumented global state. Use configured search, ...Votes: 0GitHub stars: 2
- Aas Devtools Workspace Bootstrap Change Impact TraceUse when a version, rule, source, or stakeholder change may affect local developer workspace bootstrap to produce a before/after change record and impact map for the clean-workspace readiness checklist. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; a fresh environment reaches the declared smoke test without undocumented global state. Use configured search, fetch, read, browser, test, and write capabilities ...Votes: 0GitHub stars: 2
- Aas Devtools Workspace Bootstrap Closeout Handoff LedgerUse when a local developer workspace bootstrap work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the clean-workspace readiness checklist with status, evidence, owner, and retention state. Success means all deliverables, unresolved items, approvals, and next owners are recorded, and the stop reason is explicit; a fresh environment reaches the declared smoke test without undocumented global state. Use configured search, fetch, read, browser, t...Votes: 0GitHub stars: 2
- Aas Devtools Workspace Bootstrap Completeness ReconciliationUse when the local developer workspace bootstrap workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the clean-workspace readiness checklist with matched, unmatched, and unresolved rows. Success means counts and key fields reconcile or every variance is quantified, sourced, and left unresolved for an owner; a fresh environment reaches the declared smoke test without undocumented global state. Use configured search, fetch, re...Votes: 0GitHub stars: 2
- Aas Devtools Workspace Bootstrap Exception Triage QueueUse when the local developer workspace bootstrap workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the clean-workspace readiness checklist with evidence, owner, and next action. Success means every exception has a severity rationale, source, owner or explicit unassigned state, and a bounded next step; a fresh environment reaches the declared smoke test without undocumented global state. Use configured search, fetch, read, browser, ...Votes: 0GitHub stars: 2
- Aas Devtools Workspace Bootstrap Recovery Readiness DrillUse when the local developer workspace bootstrap workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the clean-workspace readiness checklist with starting state, test, and observed outcome. Success means the dry-run or approved non-production drill meets the predeclared recovery target and leaves the baseline intact; a fresh environment reaches the declared smoke test without undocumented global state. Use configured search, fetch, read...Votes: 0GitHub stars: 2
- Aas Devtools Workspace Bootstrap Scenario Sensitivity MatrixUse when the local developer workspace bootstrap team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the clean-workspace readiness checklist with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; a fresh environment reaches the declared smoke test without undocumented global state. Use configured search, fetch, read, browser, test, ...Votes: 0GitHub stars: 2
- Aas Devtools Workspace Bootstrap Scope Intake GateUse when a new local developer workspace bootstrap request needs a bounded work scope to produce a scoped intake card for the clean-workspace readiness checklist. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; a fresh environment reaches the declared smoke test without undocumented global state. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit ref...Votes: 0GitHub stars: 2
- Aas Devtools Workspace Bootstrap Source Provenance LedgerUse when a decision about local developer workspace bootstrap depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the clean-workspace readiness checklist. Success means each material claim has a source, version/date, location, and confidence note; a fresh environment reaches the declared smoke test without undocumented global state. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized...Votes: 0GitHub stars: 2
- Aas Devtools Workspace Bootstrap Threshold Rule CheckUse when a local developer workspace bootstrap decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the clean-workspace readiness checklist showing source, units, boundary case, and outcome. Success means the rule source and effective date are verified, units and scope match, and borderline cases are flagged rather than auto-approved; a fresh environment reaches the declared smoke test without undocumented global state. Use configured search, fet...Votes: 0GitHub stars: 2
- Agents Generator Capability Surface MapUse when the actual capability boundary of Repository instruction generation needs to be distinguished from assumptions. Produce a capability map for Repository instruction generation 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 observed project conventi...Votes: 0GitHub stars: 2
- Agents Generator Change Impact AssessmentUse when a proposed Repository instruction generation version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Repository instruction generation 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 observed project conven...Votes: 0GitHub stars: 2
- Agents Generator Failure Triage RecordUse when a reproducible Repository instruction generation symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Repository instruction generation 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 observed project conventions, verified commands, package boun...Votes: 0GitHub stars: 2
- Agents Generator Input Output ContractUse when the accepted inputs or produced outputs for Repository instruction generation need a checkable boundary. Produce an input/output contract for Repository instruction generation 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 observed project conventions, verified commands, pack...Votes: 0GitHub stars: 2
- Agents Generator Integration Parity TraceUse when Repository instruction generation exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Repository instruction generation 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 observed project conventions, verified commands, package boundaries, a...Votes: 0GitHub stars: 2
- Agents Generator Performance EnvelopeUse when Repository instruction generation must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Repository instruction generation 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 observed project conventions, verified comm...Votes: 0GitHub stars: 2
- Agents Generator Permission Boundary ReviewUse when Repository instruction generation may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Repository instruction generation 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 observed project conventions, ve...Votes: 0GitHub stars: 2
- Agents Generator Release Handoff RecordUse when a Repository instruction generation review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Repository instruction generation 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 observed project conventi...Votes: 0GitHub stars: 2
- Agents Generator Reproducibility Fixture PlanUse when a Repository instruction generation result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Repository instruction generation 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
- Agents Generator Version CompatibilityUse when a Repository instruction generation integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Repository instruction generation 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 observed project con...Votes: 0GitHub stars: 2
- Architecture Blueprint GeneratorUse when a task involves turning system requirements into a reviewable architecture blueprint with boundaries, data flows, and decision points 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...Votes: 0GitHub stars: 2
- Architecture Decision RecordsUse when a durable technical decision changes architecture, platform, data, security, API, or operational constraints and future maintainers will need its rationale to capture context, alternatives, decision, consequences, status, and owner in the repository's existing ADR format. Trigger for material trade-offs, not routine implementation details.Votes: 0GitHub stars: 2
- Chrome DevtoolsUse when a task involves diagnosing a browser page with Chrome DevTools evidence from console, network, performance, or rendering panels 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 n...Votes: 0GitHub stars: 2
- Cli MasteryUse when a task involves learning or using an unfamiliar command-line tool safely and efficiently 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 install or run third-party commands ...Votes: 0GitHub stars: 2
- Code Review And Diff AuditUse when reviewing a code or configuration change for correctness, regressions, security, maintainability, and compatibility before it is accepted or merged to inspect the actual diff against its intended behavior and report only actionable, evidence-backed findings. Trigger for requested reviews, pull requests, or high-impact changes; do not silently rewrite the implementation during a review.Votes: 0GitHub stars: 2
- Code Snippet Dependency Dry Run ReviewUse when a guide includes a shell, Python, or package-manager example to create or update a snippet review record with dependencies, scope, and safe validation path. Use the configured search, fetch, read, browser, and test capabilities only when available and authorized. Success criterion: the snippet is syntactically plausible and its external effects are disclosed. Preserve evidence and a run record, limit rework to three meaningful passes, and obtain approval before externally visible or ...Votes: 0GitHub stars: 2
- Codebase DesignUse when a task involves improving module boundaries and codebase structure without introducing speculative abstractions 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 install or ru...Votes: 0GitHub stars: 2
- Codebase OnboardingUse when a developer or agent needs to understand an unfamiliar repository, find its entry points and conventions, or prepare a concise project map to inspect instructions, manifests, structure, tests, and a representative data flow without reading every file. Trigger for repo onboarding, first-session orientation, or targeted architecture familiarization.Votes: 0GitHub stars: 2
- CodeqlUse when a task involves triaging CodeQL alerts or developing a CodeQL query against a defined codebase and language 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 install or run th...Votes: 0GitHub stars: 2
- Command Line Tool DevelopmentUse when designing or implementing a command-line program, subcommand, or shell-facing interface to specify arguments, input sources, output streams, exit codes, configuration precedence, and destructive-action safeguards before expanding functionality. Trigger for CLI creation, command changes, scripting interfaces, or terminal automation.Votes: 0GitHub stars: 2
- Configuration Default Documentation Drift CheckUse when a config field’s default, precedence, or deprecation status changes to create or update a field-by-field drift table with authoritative source locations. Use the configured search, fetch, read, browser, and test capabilities only when available and authorized. Success criterion: each documented default matches the implementation for the stated version. Preserve evidence and a run record, limit rework to three meaningful passes, and obtain approval before externally visible or irrever...Votes: 0GitHub stars: 2
- Create Github Action Workflow SpecificationUse when a task involves specifying a GitHub Actions workflow before implementation, including events, permissions, jobs, outputs, and failure handling 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 focus...Votes: 0GitHub stars: 2
- Create Github Pull Request From SpecificationUse when a task involves turning an approved technical specification into a small, reviewable GitHub pull request 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 install or run third...Votes: 0GitHub stars: 2
- Create SpecificationUse when a task involves writing a self-contained technical specification with requirements, constraints, interfaces, and testable acceptance criteria 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 focuse...Votes: 0GitHub stars: 2
- Dependency Lockfile Change Proof LoopUse when a dependency manifest or lockfile changed in a branch to create or update a dependency-diff rationale with selected tests. Use the configured search, fetch, read, browser, and test capabilities only when available and authorized. Success criterion: every lockfile change is attributable to an approved manifest change and project checks pass. 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
- Effective Config Defaults Black Box CheckUse when a documented default may differ from the effective application setting to create or update a case table for absent, explicit, invalid, and inherited values. Use the configured search, fetch, read, browser, and test capabilities only when available and authorized. Success criterion: observed runtime behavior matches the approved configuration contract. Preserve evidence and a run record, limit rework to three meaningful passes, and obtain approval before externally visible or irrevers...Votes: 0GitHub stars: 2
- Generated Artifact Source Parity Hash CheckUse when generated code, schemas, clients, or docs may be stale after source edits to create or update a deterministic parity report containing generator and input fingerprints. Use the configured search, fetch, read, browser, and test capabilities only when available and authorized. Success criterion: regeneration produces no unexplained diff or a reviewed diff is linked to changed inputs. Preserve evidence and a run record, limit rework to three meaningful passes, and obtain approval before...Votes: 0GitHub stars: 2
- Gh Image Capability Surface MapUse when the actual capability boundary of GitHub image attachment workflows needs to be distinguished from assumptions. Produce a capability map for GitHub image attachment workflows 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 image identity, local ass...Votes: 0GitHub stars: 2
- Gh Image Change Impact AssessmentUse when a proposed GitHub image attachment workflows version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for GitHub image attachment workflows 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 image identity, local a...Votes: 0GitHub stars: 2
- Gh Image Failure Triage RecordUse when a reproducible GitHub image attachment workflows symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for GitHub image attachment workflows 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 image identity, local asset rights, upload target, rendered r...Votes: 0GitHub stars: 2
- Gh Image Input Output ContractUse when the accepted inputs or produced outputs for GitHub image attachment workflows need a checkable boundary. Produce an input/output contract for GitHub image attachment workflows 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 image identity, local asset rights, upload target, re...Votes: 0GitHub stars: 2
- Gh Image Integration Parity TraceUse when GitHub image attachment workflows exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for GitHub image attachment workflows 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 image identity, local asset rights, upload target, rendered reference,...Votes: 0GitHub stars: 2
- Gh Image Performance EnvelopeUse when GitHub image attachment workflows must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for GitHub image attachment workflows 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 image identity, local asset rights, upload ...Votes: 0GitHub stars: 2
- Gh Image Permission Boundary ReviewUse when GitHub image attachment workflows may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for GitHub image attachment workflows 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 image identity, local asset righ...Votes: 0GitHub stars: 2