All authors
Claude Skills by tstapler
github.com/tstapler371 skills3 installs420 views
- Github Actions DebuggingDebug GitHub Actions workflow failures by analyzing logs, identifying error patterns, and providing actionable fixes. Use when CI/CD workflows fail, jobs timeout, or actions produce unexpected errors.Votes: 0GitHub stars: 8
- Github Address Pr CommentsSystematically address all open GitHub PR review comments — fix code or decline with reasoning, reply to every thread, resolve when doneVotes: 0GitHub stars: 8
- Github Composite ActionsUse when writing, debugging, or designing GitHub Actions composite actions. Covers the `uses:` field rules, relative path resolution, composite-to-composite calling, secrets limitations, differences from reusable workflows, and best practices.Votes: 0GitHub stars: 8
- Github DebuggerUse this agent when github actions builds or checks are failingVotes: 0GitHub stars: 8
- Github Implement Top IssueUse when asked to find and implement the highest-priority GitHub issue for the current project — e.g. "work the top issue", "pick up the next issue", "implement the most important open issue". Detects the repo from the current directory, ranks open issues, implements the winner, opens a draft PR, and drives it to mergeable via github:pr-ship.Votes: 0GitHub stars: 8
- Github Org Team ActivityLook up GitHub activity for people in a GitHub org by display name or handle. Summarizes PRs opened/merged/reviewed, repos touched, and provides a narrative of what each person worked on over a specified timeframe. Use when asked what teammates have been working on, for sprint reviews, team status reports, or manager 1:1 prep.Votes: 0GitHub stars: 8
- Github Oss ReadmeCreate, improve, or audit a GitHub project's README and open-source community-health files (LICENSE, CONTRIBUTING.md, CODE_OF_CONDUCT.md, issue/PR templates). Use when the user asks for a README, README quality/readability/accuracy/examples, or wants a repo's "open source credentials" / community-standards readiness checked. Do not use for full docs sites, API-reference-only work, or general code review.Votes: 0GitHub stars: 8
- Github PrThis skill should be used when working with GitHub pull requests, reviewing PRs, creating PRs, checking PR status, viewing PR comments, analyzing CI failures, or using gh CLI commands. Emphasizes token-efficient patterns using filters, file buffers, and targeted queries.Votes: 0GitHub stars: 8
- Github Releases Git CliffUse this skill when setting up automated GitHub Releases with conventional-commit changelogs for any project. Covers git-cliff for changelog generation and softprops/action-gh-release for publishing. Tag-push trigger gives intentional control over release timing.Votes: 0GitHub stars: 8
- Pr RefineReview a pull request and suggest refinement options, then document themVotes: 0GitHub stars: 8
- Pr ShipAutonomously iterate on a PR — local CI, code review, remote CI, review comments, merge conflicts — until ready to mergeVotes: 0GitHub stars: 8
- OptimizeApply Go-specific performance fix patterns to a profiling finding. Given a pprof hotspot (location, cycles, count, profile type), walks the decision tree to select the right pattern (atomic shadow, early-return guard, sync.RWMutex, xsync.Map, TTL cache, direct SQL UPDATE), implements the fix, and produces an enforcement test at the highest achievable ladder level.Votes: 0GitHub stars: 8
- Golang BenchmarkGolang benchmarking, profiling, and performance measurement. Use when writing, running, or comparing Go benchmarks, profiling hot paths with pprof, interpreting CPU/memory/trace profiles, analyzing results with benchstat, setting up CI benchmark regression detection, or investigating production performance with Prometheus runtime metrics. Also use when the developer needs deep analysis on a specific performance indicator - this skill provides the measurement methodology, while `samber/cc-skil...Votes: 0GitHub stars: 8
- Golang Ci HardeningAudit or set up a Go repo's CI quality gates against a Rust-toolchain-equivalent bar (clippy/cargo-deny/cargo-audit/miri-level assurance). Use when asked to "harden Go CI", "set up robust Go CI checks", review .golangci.yml / Makefile lint targets, or add security/supply-chain/test-rigor gates to a Go project. Produces a gap report plus concrete config (golangci-lint v2, govulncheck, gosec, coverage/race/fuzz gates) scoped to what CI runner the repo actually uses (GH Actions, Jenkins/Rocket/n...Votes: 0GitHub stars: 8
- Golang Ci PerfSpeed up slow Go test suites and CI pipelines. Covers measuring per-test/per-package timing, eliminating subprocess overhead (shell-outs to git/cli tools), replacing real databases/filesystems with in-memory equivalents, safe t.Parallel() adoption, and CI-level caching/sharding. Use when `make test`/`go test ./...` or CI is slow and you need to find and fix the actual bottleneck rather than guessing.Votes: 0GitHub stars: 8
- Golang Code StyleGolang code style conventions — line length and breaking, variable declarations, control flow clarity, when comments help vs hurt. Use when writing or reviewing Go code, asking about style or clarity, or establishing project coding standards. Not for naming conventions (→ See `samber/cc-skills-golang@golang-naming` skill), linter configuration (→ See `samber/cc-skills-golang@golang-lint` skill), or doc comments (→ See `samber/cc-skills-golang@golang-documentation` skill).Votes: 0GitHub stars: 8
- Golang ConcurrencyChoose and apply the right Go concurrency primitive — channels, mutexes, atomics, copy-on-write, singleflight, and lock-free data structures. Use when designing concurrent access to shared state, diagnosing lock contention (paired with golang-profiling), choosing between sync.RWMutex and atomic.Pointer copy-on-write, evaluating concurrent map options (sync.Map vs xsync.MapOf), implementing singleflight request coalescing, or reaching for a lock-free queue/ring-buffer library. Covers stdlib sy...Votes: 0GitHub stars: 8
- Golang Continuous IntegrationGitHub Actions CI/CD pipeline configuration for Golang projects — workflow files for test, lint, SAST, coverage and vulnerability-scan jobs, Dependabot and Renovate config files, GoReleaser release pipelines, Docker build/push, repository security settings, and AI-driven PR review. Use when setting up or improving Go project CI, writing or fixing `.github/workflows/*.yml`, adding a linter or security scanner as a pipeline job, wiring automated dependency-update bots, or adding quality gates. ...Votes: 0GitHub stars: 8
- Golang Data StructuresGolang data structures — slices (internals, capacity growth, preallocation, slices package), maps (internals, hash buckets, maps package), arrays, container/list/heap/ring, strings.Builder vs bytes.Buffer, generic collections, pointers (unsafe.Pointer, weak.Pointer), and copy semantics. Use when choosing or optimizing Go data structures, implementing generic containers, using container/ packages, unsafe or weak pointers, or questioning slice/map internals. Not for applying optimization patter...Votes: 0GitHub stars: 8
- Golang DatabaseComprehensive guide for Go database access — parameterized queries, struct scanning, NULLable columns, transactions, isolation levels, SELECT FOR UPDATE, connection pool, batch processing, context propagation, and migration tooling. Use when writing, reviewing, or debugging Golang code that interacts with PostgreSQL, MariaDB, MySQL, or SQLite; for database testing; or for questions about database/sql, sqlx, or pgx. Does NOT generate database schemas or migration SQL.Votes: 0GitHub stars: 8
- Golang Dependency InjectionComprehensive guide for dependency injection (DI) in Golang. Covers why DI matters (testability, loose coupling, separation of concerns, lifecycle management), manual constructor injection, and DI library comparison (google/wire, uber-go/dig, uber-go/fx, samber/do). Use this skill when designing service architecture, setting up dependency injection, refactoring tightly coupled code, managing singletons or service factories, or when the user asks about inversion of control, service containers,...Votes: 0GitHub stars: 8
- Golang Depguard ArchitectureConfigure depguard in golangci-lint to enforce hexagonal / clean architecture import direction in a Go project, or pick a standalone architecture-linting tool (arch-go, go-arch-lint, cht-go-lint, go-cleanarch — researched comparison and recommendation included) when import-direction checking alone isn't enough. Use when a Go codebase needs linter rules that prevent domain packages from importing adapters or infrastructure, services from importing global config, or adapters from cross-coupling...Votes: 0GitHub stars: 8
- Golang Design PatternsIdiomatic Golang design patterns — functional options, constructors, error flow and cascading, resource management and lifecycle, graceful shutdown, resilience, architecture, dependency injection, data handling, streaming, and more. Apply when explicitly choosing between architectural patterns, implementing functional options, designing constructor APIs, setting up graceful shutdown, applying resilience patterns, or asking which idiomatic Go pattern fits a specific problem.Votes: 0GitHub stars: 8
- Golang DevelopmentApply idiomatic, well-structured Go development practices. Use when writing, reviewing, or refactoring Go code. Covers Go Proverbs, concurrency fundamentals, type-system maximization (generics, embedding, iota, receivers), primitive-obsession fixes, and anti-patterns based on Effective Go, Go Code Review Comments, and Go Proverbs. For error handling, naming, interfaces/structs, project layout, testing, and design patterns, see the dedicated `golang-error-handling`, `golang-naming`, `golang-st...Votes: 0GitHub stars: 8
- Golang DocumentationComprehensive documentation guide for Golang projects, covering godoc comments, README, CONTRIBUTING, CHANGELOG, Go Playground, Example tests, API docs, and llms.txt. Use when writing or reviewing doc comments, documentation, adding code examples, setting up doc sites, or discussing documentation best practices. Triggers for both libraries and applications/CLIs.Votes: 0GitHub stars: 8
- Golang Error HandlingIdiomatic Golang error handling — creation, wrapping with %w, errors.Is/As, errors.Join, custom error types, sentinel errors, panic/recover, the single handling rule, structured logging with slog, HTTP request logging middleware, and samber/oops for production errors. Built to make logs usable at scale with log aggregation 3rd-party tools. Apply when creating, wrapping, inspecting, or logging errors in Go code. For samber/oops specifics → See `samber/cc-skills-golang@golang-samber-oops` skill...Votes: 0GitHub stars: 8
- Golang GoplsGolang semantic code intelligence via `gopls`, the official Go language server — go-to-definition, find references, call/implementation hierarchy, workspace symbol search, package API discovery, diagnostics, safe rename, refactors (extract/inline/fill/rewrite code actions), formatting, and generated tests. Reaches an agent via gopls's own MCP server (`go_*` tools), Claude Code's native `LSP` tool, or the `gopls` CLI. Use when navigating or refactoring Go code — jumping to a definition, findin...Votes: 0GitHub stars: 8
- Golang GrpcProvides gRPC usage guidelines, protobuf organization, and production-ready patterns for Golang microservices. Use when implementing, reviewing, or debugging gRPC servers/clients, writing proto files, setting up interceptors, handling gRPC errors with status codes, configuring TLS/mTLS, testing with bufconn, or working with streaming RPCs.Votes: 0GitHub stars: 8
- Golang How ToGolang skills orchestrator — always active on any Golang coding, review, debug, or setup task. Reads the task context and loads the most relevant skills from samber/cc-skills-golang, often multiple at once: writing a gRPC service loads golang-grpc + golang-testing + golang-error-handling; debugging a panic loads golang-troubleshooting + golang-safety; auditing security loads golang-security + golang-lint + golang-safety. Also: disambiguates competing clusters when two skills seem to overlap (...Votes: 0GitHub stars: 8
- Golang NamingGo (Golang) naming conventions — covers packages, constructors, structs, interfaces, constants, enums, errors, booleans, receivers, getters/setters, functional options, acronyms, test functions, and subtest names. Use this skill when writing new Go code, reviewing or refactoring, choosing between naming alternatives (New vs NewTypeName, isConnected vs connected, ErrNotFound vs NotFoundError, StatusReady vs StatusUnknown at iota 0), debating Go package names (utils/helpers anti-patterns), or a...Votes: 0GitHub stars: 8
- Golang ObservabilityGolang everyday observability — the always-on signals in production. Covers structured logging with slog, Prometheus metrics, OpenTelemetry distributed tracing, continuous profiling with pprof/Pyroscope, server-side RUM event tracking, alerting, and Grafana dashboards. Apply when instrumenting Go services for production monitoring, setting up metrics or alerting, adding OpenTelemetry tracing, correlating logs with traces, migrating legacy loggers (zap/logrus/zerolog) to slog, adding observabi...Votes: 0GitHub stars: 8
- Golang PerformanceGolang performance optimization patterns and methodology - if X bottleneck, then apply Y. Covers allocation reduction, CPU efficiency, memory layout, GC tuning, pooling, caching, and hot-path optimization. Use when profiling or benchmarks have identified a bottleneck and you need the right optimization pattern to fix it. Also use when performing performance code review to suggest improvements or benchmarks that could help identify quick performance gains. Not for measurement methodology (→ Se...Votes: 0GitHub stars: 8
- Golang Popular LibrariesGolang library and framework selection — vetted production-ready options by category (web, database, testing, logging, messaging), new and experimental stdlib packages, standard-library-first tradeoffs, and maturity signals (maintenance, license, importer counts). Apply when the user asks for library suggestions, wants to compare alternatives, needs to choose a library for a specific task, or when a new dependency is being added to the project. Not for a specific library's API once chosen (→ ...Votes: 0GitHub stars: 8
- Golang ProfilingProfile Go processes using pprof. Covers CPU, memory, goroutine, and mutex profiles; flamegraph visualization; collapsed-stacks and annotated-call-tree output for LLM analysis (with bundled, tested scripts); and benchmark profiling.Votes: 0GitHub stars: 8
- Golang Project LayoutProvides a guide for setting up Golang project layouts and workspaces. Use when starting a new Go project, organizing an existing codebase, setting up a monorepo with multiple packages, creating CLI tools with multiple main packages, deciding between cmd/internal/pkg directory conventions, or discussing package restructuring, package splits, or module splits.Votes: 0GitHub stars: 8
- Golang RefactoringGolang refactoring — safe, at-scale restructuring of existing Go code: a coverage-adaptive safety net, behavior-preserving transforms (gopls Rename/Extract, `gofmt -r`, `gopatch`), the Fowler catalog mapped to Go, breaking import cycles, and small stacked PRs. Apply when a function or type has grown too large, a code smell blocks a feature, or the user asks to refactor Go code — also for renaming at scale, extracting functions or interfaces, moving code between packages, or planning a multi-s...Votes: 0GitHub stars: 8
- Golang Samber DoDependency injection in Golang using samber/do — service containers, lifecycle management, scopes, health checks, graceful shutdown, and module organization. Apply when using or adopting samber/do, when the codebase imports github.com/samber/do or github.com/samber/do/v2, or when refactoring manual constructor injection into a DI container.Votes: 0GitHub stars: 8
- Golang Samber HotIn-memory caching in Golang using samber/hot — eviction algorithms (LRU, LFU, TinyLFU, W-TinyLFU, S3FIFO, ARC, TwoQueue, SIEVE, FIFO), TTL, cache loaders, sharding, stale-while-revalidate, missing key caching, and Prometheus metrics. Apply when using or adopting samber/hot, when the codebase imports github.com/samber/hot, or when the project repeatedly loads the same medium-to-low cardinality resources at high frequency and needs to reduce latency or backend pressure.Votes: 0GitHub stars: 8
- Golang Samber OopsStructured error handling in Golang with samber/oops — error builders, stack traces, error codes, error context, error wrapping, error attributes, user-facing vs developer messages, panic recovery, and logger integration. Apply when using or adopting samber/oops, or when the codebase already imports github.com/samber/oops.Votes: 0GitHub stars: 8
- Golang SecuritySecurity best practices and vulnerability prevention for Golang — injection (SQL, command, XSS), cryptography, path traversal, SSRF and HTTP security headers, cookies, secrets management, memory safety, PII in logs, STRIDE/DREAD threat modeling, plus `gosec` SAST, race detection, and fuzz testing. Apply when writing, reviewing, or auditing Go code for security, or when touching crypto, file or network I/O, secrets, user input, or authentication. Not for non-exploitable defensive bugs such as ...Votes: 0GitHub stars: 8
- Golang Structs InterfacesGolang struct and interface design patterns — composition, embedding, type assertions, type switches, interface segregation, dependency injection via interfaces, struct field tags, and pointer vs value receivers. Use this skill when designing Go types, defining or implementing interfaces, embedding structs or interfaces, writing type assertions or type switches, adding struct field tags for JSON/YAML/DB serialization, or choosing between pointer and value receivers. Also use when the user ask...Votes: 0GitHub stars: 8
- Golang Test DebuggerUse this agent when you need to diagnose and fix failing Go tests withVotes: 0GitHub stars: 8
- Golang TestingProduction-ready Golang tests — table-driven tests, testify suites and mocks, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, code coverage, integration tests, idiomatic test naming. Use when writing or reviewing Go tests, choosing a testing approach, setting up Go test CI, or debugging flaky/slow tests. For testify-specific APIs see `samber/cc-skills-golang@golang-stretchr-testify`; for measurement methodology see `samber/cc-skills-golang@golang-ben...Votes: 0GitHub stars: 8
- Golang TroubleshootingTroubleshoot Golang programs systematically - find and fix the root cause. Use when encountering bugs, crashes, deadlocks, races, or unexpected behavior in Go code. Covers debugging methodology, common Go pitfalls, test-driven debugging, pprof setup and capture, Delve, race detection, GODEBUG tracing, and production debugging. Start here for any 'something is wrong' situation. Not for interpreting profiles or benchmarking (→ See `samber/cc-skills-golang@golang-benchmark` skill), applying opti...Votes: 0GitHub stars: 8
- Google Drive OrganizationSurvey a Google Drive's actual folder structure, apply a PARA-lite organization framework, and produce (then safely execute) a concrete reorganization plan — deduping, sweeping root-level clutter, and fixing misnested folders.Votes: 0GitHub stars: 8
- GritqlUse gritql (grit) for AST-based multi-file code transformations. UseVotes: 0GitHub stars: 8
- PlanEngineering-focused project plans with solo work strategies, critical path analysis, professional-grade techniques, pre-work briefing checklists, and ITP-style stage-gate hold pointsVotes: 0GitHub stars: 8
- Home Project PlanningStructured home project planning workflow (scope → research → plan → prep → execute → close). Use for any home improvement, repair, installation, or maintenance project.Votes: 0GitHub stars: 8
- 1 ScopePhase 1 — Interview to scope the home project. Outputs: home_plans/<project>/scope.mdVotes: 0GitHub stars: 8
- 2 ResearchPhase 2 — Parallel research across 4 dimensions. Outputs: home_plans/<project>/research/*.mdVotes: 0GitHub stars: 8