pszypowicz
UserA small Claude Code marketplace: ado, swift-concurrency, modern-swift, go-dev, worktrees.
Categories
Indexed Skills (5)
ado
Azure DevOps operations - PRs, pipelines, policies, builds, variable groups, environments, feeds, branches, work items, comments. This skill should be used when the user asks to "create a PR", "list pipelines", "run a pipeline", "check build status", "debug failed pipeline", "create a policy", "add reviewers", "create a work item", "update a task", "list environments", "approve a pipeline", "manage variable groups", "delete a branch", "comment on a PR", "review PR comments", "comment on work items", "resolve PR thread", "code suggestion", or mentions Azure DevOps, ADO, or az devops CLI. Uses az CLI with PAT auth.
go-dev
Go development with toolchain-first verification workflow. Use whenever the user (1) writes, modifies, debugs, or reviews Go code, (2) works with go.mod, go.sum, or Go module dependencies, (3) writes or runs Go tests, benchmarks, or fuzz tests, (4) mentions go doc, go vet, go fix, go test, go build, go mod, gofmt, staticcheck, golangci-lint, govulncheck, or pprof, (5) asks about Go error handling (errors.Is/As/AsType/Join), concurrency (goroutines, channels, sync, context), interfaces, or package design, (6) encounters Go compiler errors, test failures, or race conditions, (7) profiles Go code for performance or works with PGO, (8) asks about Go best practices, code review, or idiomatic Go, (9) works with files ending in .go or _test.go, (10) wants to modernize Go code to 1.21-1.26 features. Trigger this skill proactively when the user is working in a Go codebase even if they do not explicitly ask for Go help - the toolchain-first workflow (verify APIs with go doc before coding, run go vet after) catches bugs
modern-swift
Swift language features beyond concurrency: attributes (@available, @discardableResult, @frozen, @inlinable, @usableFromInline, @backDeployed, @resultBuilder, @propertyWrapper) and macro usage (#Preview, custom macros). Use when the user asks about API availability checks, library evolution, deprecating or renaming APIs, back-deploying functions to older OSes, result builders / DSLs, property wrappers, or Swift macros. Do NOT use this skill for concurrency topics (async/await, actors, Sendable, @MainActor, @Observable) - those belong to swift-concurrency.
swift-concurrency
Diagnose data races, convert callback-based code to async/await, implement actor isolation patterns, resolve Sendable conformance issues, fix @Observable + @MainActor interaction problems, and guide Swift 6 migration. Use when developers mention: (1) Swift Concurrency, async/await, actors, or tasks, (2) "use Swift Concurrency" or "modern concurrency patterns", (3) migrating to Swift 6, (4) data races or thread safety issues, (5) refactoring closures to async/await, (6) @MainActor, Sendable, or actor isolation, (7) @Observable with concurrency or actor isolation, (8) concurrent code architecture or performance optimization, (9) concurrency-related linter warnings (SwiftLint or similar), (10) SwiftUI view model patterns with Observation framework.
start-project
Batch-provision git worktrees for a set of planned tasks across one or more repos under ~/Developer/. Use whenever the user names a set of tasks or branches to work on, wants to "start a project", "kick off" or "begin" planned work, "set up worktrees for X/Y/Z", or otherwise wants isolated working copies to land commits against before a single-repo edit makes sense. Trigger even if the user doesn't use the exact word "worktree" - if they're framing upcoming work as a list of {repo, branch} pairs, this skill handles it. Do NOT trigger for inventory questions ("what worktrees do I have?" - that's `/worktree-status`), single-branch lookups ("where's the worktree for X?" - `/worktree-for`), or teardown ("clean up my worktrees" - `/worktree-cleanup`).
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.