Skip to content

verification: .NET/C#/PowerShell-flavored examples and Unix-shell assumptions in stack-agnostic skills (low severity) #424

Description

@kyle-sexton

Plugin: verification · Category: hardcoded opinion (1) — low severity
Source: work-readiness sweep (read-only audit vs docs/PLUGIN-PHILOSOPHY.md + docs/MIGRATION-PLAYBOOK.md)

Findings

  • plugins/verification/skills/confirm/context/fix.md:52-54 — "UserService_ShouldReturnNull_WhenUserIsDeleted", "NullReferenceException" (C# idiom)
  • plugins/verification/skills/measure/context/metrics.md:16 — "Count using/import, ProjectReference count", "dotnet test output"; :24git show <base>:<file> | wc -l (Unix shell assumed)
  • plugins/verification/skills/measure/context/performance.md:14-19 — "dotnet test timing, Measure-Command", "dotnet-counters, dotnet-trace", "BenchmarkDotNet"

Why flagged

Illustrative examples lean .NET/C#/PowerShell in a plugin sold as ecosystem-agnostic, reinforcing the stack bias of the portable-defaults and cross-plugin-refs issues; wc -l assumes a Unix shell against the cross-platform contract ("never assume Bash"). Lower severity — table cells, not hard behavior.

Fix direction

Neutralize examples (generic test-name form, "count imports/dependencies", "your project's benchmark harness") or present a multi-ecosystem set; keep the C# example only if paired with at least one non-.NET example.

Metadata

Metadata

Assignees

No one assigned

    Labels

    priority: highSignificant impact, or blocks an imminent release; staff this cycle.status: readyTriaged, unblocked, and fully specified; eligible to pick up.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions