All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Aas Devtools Cli Option Contract Exception Triage QueueUse when the developer CLI option contracts workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the CLI option contract matrix 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; documented options match executable behavior and invalid combinations fail clearly. Use configured search, fetch, read, browser, test, and write c...Votes: 0GitHub stars: 2
- Aas Devtools Cli Option Contract Recovery Readiness DrillUse when the developer CLI option contracts workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the CLI option contract matrix 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; documented options match executable behavior and invalid combinations fail clearly. Use configured search, fetch, read, browser, test, ...Votes: 0GitHub stars: 2
- Aas Devtools Cli Option Contract Scenario Sensitivity MatrixUse when the developer CLI option contracts team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the CLI option contract matrix with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; documented options match executable behavior and invalid combinations fail clearly. Use configured search, fetch, read, browser, test, and write capabil...Votes: 0GitHub stars: 2
- Aas Devtools Cli Option Contract Scope Intake GateUse when a new developer CLI option contracts request needs a bounded work scope to produce a scoped intake card for the CLI option contract matrix. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; documented options match executable behavior and invalid combinations fail clearly. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three ...Votes: 0GitHub stars: 2
- Aas Devtools Cli Option Contract Source Provenance LedgerUse when a decision about developer CLI option contracts depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the CLI option contract matrix. Success means each material claim has a source, version/date, location, and confidence note; documented options match executable behavior and invalid combinations fail clearly. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence...Votes: 0GitHub stars: 2
- Aas Devtools Cli Option Contract Threshold Rule CheckUse when a developer CLI option contracts decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the CLI option contract matrix 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; documented options match executable behavior and invalid combinations fail clearly. Use configured search, fetch, read, browser...Votes: 0GitHub stars: 2
- Aas Devtools Codegen Reproducibility Approval Evidence PacketUse when a developer code generation reproducibility result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the code-generation reproducibility record 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; identical declared inputs produce equivalent output or a nondeterministic input is named. Use configu...Votes: 0GitHub stars: 2
- Aas Devtools Codegen Reproducibility Change Impact TraceUse when a version, rule, source, or stakeholder change may affect developer code generation reproducibility to produce a before/after change record and impact map for the code-generation reproducibility record. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; identical declared inputs produce equivalent output or a nondeterministic input is named. Use configured search, fetch, read, browser, test, and write c...Votes: 0GitHub stars: 2
- Aas Devtools Codegen Reproducibility Closeout Handoff LedgerUse when a developer code generation reproducibility work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the code-generation reproducibility record 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; identical declared inputs produce equivalent output or a nondeterministic input is named. Use configured search, fetch, read...Votes: 0GitHub stars: 2
- Aas Devtools Codegen Reproducibility Completeness ReconciliationUse when the developer code generation reproducibility workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the code-generation reproducibility record 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; identical declared inputs produce equivalent output or a nondeterministic input is named. Use configured searc...Votes: 0GitHub stars: 2
- Aas Devtools Codegen Reproducibility Exception Triage QueueUse when the developer code generation reproducibility workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the code-generation reproducibility record 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; identical declared inputs produce equivalent output or a nondeterministic input is named. Use configured search, fetch, rea...Votes: 0GitHub stars: 2
- Aas Devtools Codegen Reproducibility Recovery Readiness DrillUse when the developer code generation reproducibility workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the code-generation reproducibility record 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; identical declared inputs produce equivalent output or a nondeterministic input is named. Use configured search,...Votes: 0GitHub stars: 2
- Aas Devtools Codegen Reproducibility Scenario Sensitivity MatrixUse when the developer code generation reproducibility team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the code-generation reproducibility record with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; identical declared inputs produce equivalent output or a nondeterministic input is named. Use configured search, fetch, read, bro...Votes: 0GitHub stars: 2
- Aas Devtools Codegen Reproducibility Scope Intake GateUse when a new developer code generation reproducibility request needs a bounded work scope to produce a scoped intake card for the code-generation reproducibility record. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; identical declared inputs produce equivalent output or a nondeterministic input is named. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidenc...Votes: 0GitHub stars: 2
- Aas Devtools Codegen Reproducibility Source Provenance LedgerUse when a decision about developer code generation reproducibility depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the code-generation reproducibility record. Success means each material claim has a source, version/date, location, and confidence note; identical declared inputs produce equivalent output or a nondeterministic input is named. Use configured search, fetch, read, browser, test, and write capabilities only when relevant an...Votes: 0GitHub stars: 2
- Aas Devtools Codegen Reproducibility Threshold Rule CheckUse when a developer code generation reproducibility decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the code-generation reproducibility record 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; identical declared inputs produce equivalent output or a nondeterministic input is named. Use configured...Votes: 0GitHub stars: 2
- Aas Devtools Config Precedence Approval Evidence PacketUse when a developer tool configuration precedence result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the configuration precedence table 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; the effective setting is explainable without exposing secret values. Use configured search, fetch, read, browse...Votes: 0GitHub stars: 2
- Aas Devtools Config Precedence Change Impact TraceUse when a version, rule, source, or stakeholder change may affect developer tool configuration precedence to produce a before/after change record and impact map for the configuration precedence table. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; the effective setting is explainable without exposing secret values. Use configured search, fetch, read, browser, test, and write capabilities only when relevant ...Votes: 0GitHub stars: 2
- Aas Devtools Config Precedence Closeout Handoff LedgerUse when a developer tool configuration precedence work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the configuration precedence table 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; the effective setting is explainable without exposing secret values. Use configured search, fetch, read, browser, test, and write capa...Votes: 0GitHub stars: 2
- Aas Devtools Config Precedence Completeness ReconciliationUse when the developer tool configuration precedence workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the configuration precedence table 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; the effective setting is explainable without exposing secret values. Use configured search, fetch, read, browser, test, ...Votes: 0GitHub stars: 2
- Aas Devtools Config Precedence Exception Triage QueueUse when the developer tool configuration precedence workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the configuration precedence table 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; the effective setting is explainable without exposing secret values. Use configured search, fetch, read, browser, test, and write cap...Votes: 0GitHub stars: 2
- Aas Devtools Config Precedence Recovery Readiness DrillUse when the developer tool configuration precedence workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the configuration precedence table 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; the effective setting is explainable without exposing secret values. Use configured search, fetch, read, browser, test, an...Votes: 0GitHub stars: 2
- Aas Devtools Config Precedence Scenario Sensitivity MatrixUse when the developer tool configuration precedence team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the configuration precedence table with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; the effective setting is explainable without exposing secret values. Use configured search, fetch, read, browser, test, and write capabilit...Votes: 0GitHub stars: 2
- Aas Devtools Config Precedence Scope Intake GateUse when a new developer tool configuration precedence request needs a bounded work scope to produce a scoped intake card for the configuration precedence table. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; the effective setting is explainable without exposing secret values. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three fo...Votes: 0GitHub stars: 2
- Aas Devtools Config Precedence Source Provenance LedgerUse when a decision about developer tool configuration precedence depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the configuration precedence table. Success means each material claim has a source, version/date, location, and confidence note; the effective setting is explainable without exposing secret values. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, ...Votes: 0GitHub stars: 2
- Aas Devtools Config Precedence Threshold Rule CheckUse when a developer tool configuration precedence decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the configuration precedence table 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; the effective setting is explainable without exposing secret values. Use configured search, fetch, read, browser, ...Votes: 0GitHub stars: 2
- Aas Devtools Devcontainer Parity Approval Evidence PacketUse when a development container parity result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the devcontainer parity report 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; containerized setup meets the declared development tasks without unexpected host access. Use configured search, fetch, read, b...Votes: 0GitHub stars: 2
- Aas Devtools Devcontainer Parity Change Impact TraceUse when a version, rule, source, or stakeholder change may affect development container parity to produce a before/after change record and impact map for the devcontainer parity report. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; containerized setup meets the declared development tasks without unexpected host access. Use configured search, fetch, read, browser, test, and write capabilities only when rele...Votes: 0GitHub stars: 2
- Aas Devtools Devcontainer Parity Closeout Handoff LedgerUse when a development container parity work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the devcontainer parity report 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; containerized setup meets the declared development tasks without unexpected host access. Use configured search, fetch, read, browser, test, and write...Votes: 0GitHub stars: 2
- Aas Devtools Devcontainer Parity Completeness ReconciliationUse when the development container parity workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the devcontainer parity report 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; containerized setup meets the declared development tasks without unexpected host access. Use configured search, fetch, read, browser, t...Votes: 0GitHub stars: 2
- Aas Devtools Devcontainer Parity Exception Triage QueueUse when the development container parity workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the devcontainer parity report 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; containerized setup meets the declared development tasks without unexpected host access. Use configured search, fetch, read, browser, test, and writ...Votes: 0GitHub stars: 2
- Aas Devtools Devcontainer Parity Recovery Readiness DrillUse when the development container parity workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the devcontainer parity report 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; containerized setup meets the declared development tasks without unexpected host access. Use configured search, fetch, read, browser, tes...Votes: 0GitHub stars: 2
- Aas Devtools Devcontainer Parity Scenario Sensitivity MatrixUse when the development container parity team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the devcontainer parity report with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; containerized setup meets the declared development tasks without unexpected host access. Use configured search, fetch, read, browser, test, and write capa...Votes: 0GitHub stars: 2
- Aas Devtools Devcontainer Parity Scope Intake GateUse when a new development container parity request needs a bounded work scope to produce a scoped intake card for the devcontainer parity report. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; containerized setup meets the declared development tasks without unexpected host access. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to thr...Votes: 0GitHub stars: 2
- Aas Devtools Devcontainer Parity Source Provenance LedgerUse when a decision about development container parity depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the devcontainer parity report. Success means each material claim has a source, version/date, location, and confidence note; containerized setup meets the declared development tasks without unexpected host access. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evide...Votes: 0GitHub stars: 2
- Aas Devtools Devcontainer Parity Threshold Rule CheckUse when a development container parity decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the devcontainer parity report 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; containerized setup meets the declared development tasks without unexpected host access. Use configured search, fetch, read, brow...Votes: 0GitHub stars: 2
- Aas Devtools Lockfile Migration Approval Evidence PacketUse when a package manager lockfile migration result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the lockfile migration comparison 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; the migration preserves declared constraints or lists every changed dependency. Use configured search, fetch, read, b...Votes: 0GitHub stars: 2
- Aas Devtools Lockfile Migration Change Impact TraceUse when a version, rule, source, or stakeholder change may affect package manager lockfile migration to produce a before/after change record and impact map for the lockfile migration comparison. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; the migration preserves declared constraints or lists every changed dependency. Use configured search, fetch, read, browser, test, and write capabilities only when rele...Votes: 0GitHub stars: 2
- Aas Devtools Lockfile Migration Closeout Handoff LedgerUse when a package manager lockfile migration work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the lockfile migration comparison 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; the migration preserves declared constraints or lists every changed dependency. Use configured search, fetch, read, browser, test, and write...Votes: 0GitHub stars: 2
- Aas Devtools Lockfile Migration Completeness ReconciliationUse when the package manager lockfile migration workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the lockfile migration comparison 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; the migration preserves declared constraints or lists every changed dependency. Use configured search, fetch, read, browser, t...Votes: 0GitHub stars: 2
- Aas Devtools Lockfile Migration Exception Triage QueueUse when the package manager lockfile migration workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the lockfile migration comparison 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; the migration preserves declared constraints or lists every changed dependency. Use configured search, fetch, read, browser, test, and writ...Votes: 0GitHub stars: 2
- Aas Devtools Lockfile Migration Recovery Readiness DrillUse when the package manager lockfile migration workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the lockfile migration comparison 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; the migration preserves declared constraints or lists every changed dependency. Use configured search, fetch, read, browser, tes...Votes: 0GitHub stars: 2
- Aas Devtools Lockfile Migration Scenario Sensitivity MatrixUse when the package manager lockfile migration team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the lockfile migration comparison with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; the migration preserves declared constraints or lists every changed dependency. Use configured search, fetch, read, browser, test, and write capa...Votes: 0GitHub stars: 2
- Aas Devtools Lockfile Migration Scope Intake GateUse when a new package manager lockfile migration request needs a bounded work scope to produce a scoped intake card for the lockfile migration comparison. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; the migration preserves declared constraints or lists every changed dependency. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to thr...Votes: 0GitHub stars: 2
- Aas Devtools Lockfile Migration Source Provenance LedgerUse when a decision about package manager lockfile migration depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the lockfile migration comparison. Success means each material claim has a source, version/date, location, and confidence note; the migration preserves declared constraints or lists every changed dependency. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evide...Votes: 0GitHub stars: 2
- Aas Devtools Lockfile Migration Threshold Rule CheckUse when a package manager lockfile migration decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the lockfile migration comparison 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; the migration preserves declared constraints or lists every changed dependency. Use configured search, fetch, read, brow...Votes: 0GitHub stars: 2
- Aas Devtools Monorepo Change Scope Approval Evidence PacketUse when a monorepo change impact scoping result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the package impact map 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; affected packages and required checks are justified from the graph. Use configured search, fetch, read, browser, test, and write cap...Votes: 0GitHub stars: 2
- Aas Devtools Monorepo Change Scope Change Impact TraceUse when a version, rule, source, or stakeholder change may affect monorepo change impact scoping to produce a before/after change record and impact map for the package impact map. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; 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...Votes: 0GitHub stars: 2
- Aas Devtools Monorepo Change Scope Closeout Handoff LedgerUse when a monorepo change impact scoping work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the package impact map 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; affected packages and required checks are justified from the graph. Use configured search, fetch, read, browser, test, and write capabilities only when rel...Votes: 0GitHub stars: 2
- Aas Devtools Monorepo Change Scope Completeness ReconciliationUse when the monorepo change impact scoping workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the package impact map 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; affected packages and required checks are justified from the graph. Use configured search, fetch, read, browser, test, and write capabilities...Votes: 0GitHub stars: 2