All authors
Claude Skills by Goldziher
github.com/Goldziher76 skills0 installs42 views
- Observability StandardsObservability standards: JSON structured logging with key=value fields and never string interpolation, the ERROR/WARN/INFO/DEBUG/TRACE level taxonomy, a /health endpoint with per-component status wired to orchestrator probes, counter/gauge/histogram metric choice with no high-cardinality labels, and correlation-ID propagation across service boundaries. Load when adding logging, metrics, tracing or a health endpoint to a service, or reviewing what a service emits.Votes: 0GitHub stars: 150
- Release NotesDraft release notes from merged pull requestsVotes: 0GitHub stars: 150
- Capability Delivery ChecklistEnd-to-end checklist for delivering new capabilities across CLI, presets, and testsVotes: 0GitHub stars: 146
- Config Schema MaintainerConfig and Schema MaintainerVotes: 0GitHub stars: 146
- Core WorkflowsCore WorkflowsVotes: 0GitHub stars: 146
- Docs And SiteDocs and Site StewardVotes: 0GitHub stars: 146
- Mcp IntegrationsMCP IntegrationsVotes: 0GitHub stars: 146
- Release And DistributionRelease and Distribution StewardVotes: 0GitHub stars: 146
- Repository LayoutRepository LayoutVotes: 0GitHub stars: 146
- Test Fixture MaintainerTest and Fixture MaintainerVotes: 0GitHub stars: 146
- Cgo Bindingscgo conventions for linking Go to a C or Rust static library: import \"C\" directives, type/string conversion, CString memory management, thread safety, and Go pointer pinning. Load when generating or reviewing cgo bindings that call a C or Rust core from Go.Votes: 0GitHub stars: 146
- Ext Php Rs Bindingsext-php-rs conventions for building PHP 8.2+ native extensions from a Rust core: php_class/php_function macros, Zval conversion, PhpException mapping, php.ini loading, and PHPUnit testing. Load when generating or reviewing ext-php-rs PHP bindings for a Rust library.Votes: 0GitHub stars: 146
- Extendr Bindingsextendr conventions for exposing a Rust core to R: extendr macros and module registration, Robj type mapping, NA handling, rextendr builds, R package scaffolding, and CRAN compliance. Load when generating or reviewing extendr R bindings for a Rust library.Votes: 0GitHub stars: 146
- Jni Rs Bindingsjni-rs conventions for exposing a Rust core to Java/JVM: JNI export naming, JNIEnv usage, string conversion, exception checks/throws, global references, and library loading. Load when generating or reviewing jni-rs Java/JVM bindings for a Rust library.Votes: 0GitHub stars: 146
- Magnus BindingsMagnus conventions for building Ruby native extensions from a Rust core: define_class, TryConvert/IntoValue, exception mapping, GVL handling, TypedData GC integration, and rake-compiler distribution. Load when generating or reviewing Magnus Ruby bindings for a Rust library.Votes: 0GitHub stars: 146
- Napi Rs Bindingsnapi-rs conventions for exposing a Rust core to Node.js: #[napi] macros, napi::Error mapping, auto-generated .d.ts types, async Promises, and CommonJS/ESM output. Load when generating or reviewing napi-rs Node.js bindings for a Rust library.Votes: 0GitHub stars: 146
- Pyo3 BindingsPyO3 conventions for exposing a Rust core to Python: pyclass/pymethods, PyErr/PyResult error mapping, GIL release, properties, maturin builds, and pytest. Load when generating or reviewing PyO3 Python bindings for a Rust library.Votes: 0GitHub stars: 146
- Rustler BindingsRustler conventions for building Elixir NIFs from a Rust core: nif macros, tagged {:ok,_}/{:error,_} tuples, dirty schedulers, ResourceArc state, NifStruct derives, and mix compile. Load when generating or reviewing Rustler Elixir NIF bindings for a Rust library.Votes: 0GitHub stars: 146
- Vite Plus Conventionsvite+ unified TypeScript toolchain conventions: the vp CLI for package/node management, oxlint/oxfmt, type-aware linting, vitest, rolldown/tsdown bundling, task caching, and migration. Load when configuring or reviewing a vite+ TypeScript toolchain.Votes: 0GitHub stars: 146
- Wasm Bindingswasm-bindgen conventions for compiling a Rust core to WebAssembly for JavaScript: wasm-pack packaging, JsValue mapping, async futures, bundle-size tuning, web-sys/js-sys, and TypeScript defs. Load when generating or reviewing WebAssembly/JS bindings for a Rust library.Votes: 0GitHub stars: 146
- Csharp ConventionsC# code conventions covering .NET 8+/C# 12, nullable reference types, Roslyn analyzers, xUnit, record types, async/await discipline, and dependency security. Load when writing or reviewing C# code.Votes: 0GitHub stars: 146
- Elixir ConventionsElixir code conventions covering Elixir 1.14+/OTP 25+, pattern matching, mix format, Credo/Dialyzer, ExUnit, ExDoc, OTP process patterns, and dependency security. Load when writing or reviewing Elixir code.Votes: 0GitHub stars: 146
- Go ConventionsGo code conventions covering Effective Go, error wrapping, golangci-lint, govulncheck, table-driven tests, interfaces, context usage, modules, and concurrency. Load when writing or reviewing Go code.Votes: 0GitHub stars: 146
- Java ConventionsJava code conventions covering Java 17+ records and sealed classes, formatting/static analysis, Maven/Gradle, JUnit 5, exception handling, constructor injection, streams, and security. Load when writing or reviewing Java code.Votes: 0GitHub stars: 146
- Php ConventionsPHP code conventions covering PHP 8.2+ strict types, PSR-12 formatting, PHPStan/Psalm static analysis, PHPUnit, Composer dependency management, PSR-4 autoloading, and security. Load when writing or reviewing PHP code.Votes: 0GitHub stars: 146
- Python ConventionsPython code conventions covering type hints, Ruff formatting/linting, mypy/pyright, pytest, async I/O, uv packaging, and dependency security scanning. Load when writing or reviewing Python code.Votes: 0GitHub stars: 146
- R ConventionsR code conventions covering R 4.1+, tidyverse/base style, styler/lintr, roxygen2, testthat, error handling, input validation, C/C++/Rust interop, and CRAN compliance. Load when writing or reviewing R code.Votes: 0GitHub stars: 146
- Ruby ConventionsRuby code conventions covering Ruby 3.2+, RuboCop, RBS type checking, RSpec/Minitest, security scanning, exception handling, composition, Bundler, and gem packaging. Load when writing or reviewing Ruby code.Votes: 0GitHub stars: 146
- Rust ConventionsRust code conventions covering edition 2024, cargo fmt/clippy, Result-based error handling, unsafe discipline, async with tokio, API-guideline naming, trait implementations, benchmarking, and security scanning. Load when writing or reviewing Rust code.Votes: 0GitHub stars: 146
- Typescript ConventionsTypeScript code conventions covering strict tsconfig, ESM imports, discriminated unions, formatting/linting, Vitest testing, lockfile-based packaging, Node.js, and security. Load when writing or reviewing TypeScript code.Votes: 0GitHub stars: 146
- Code Quality StandardsConcrete code-quality thresholds and anti-patterns: 120-char lines, max 20 cyclomatic complexity, max 4 nesting levels, max 50 lines per function, no magic numbers, no global state, composition over inheritance, no bare except, rule-of-three before extracting an abstraction, delete dead code instead of commenting it out. Load when writing a new function or module, reviewing a diff for quality, refactoring a long or deeply nested function, or deciding whether to extract shared logic.Votes: 0GitHub stars: 146
- Error HandlingLanguage-idiomatic error handling: wrap errors with the failed operation's context, never swallow silently, `Result<T, E>` in Rust, `fmt.Errorf(\"doing X: %w\", err)` in Go, typed exceptions in Python/Java, fail fast on unrecoverable errors. Load when writing or reviewing an error path, a catch/except block, a custom error type, or code that returns or propagates failures.Votes: 0GitHub stars: 146
- Container StandardsContainer build and runtime standards: multi-stage builds into a minimal runtime (Alpine/Distroless/Scratch), manifest-before-source layer ordering for cache hits, non-root user, vulnerability scan failing on HIGH/CRITICAL, no secrets in the image, tini/dumb-init as PID 1, HEALTHCHECK, and semver+SHA tags that are never reused. Load when writing or reviewing a Dockerfile, docker-compose file, container build pipeline, or image tagging scheme.Votes: 0GitHub stars: 146
- BindingsCross-language binding architecture rules: bindings as minimal glue, canonical API surface ordering (core, ABI, language), per-language test suites in CI, generated-code discipline, and error/async boundary preservation. Load when designing or reviewing polyglot language bindings for a shared core.Votes: 0GitHub stars: 146
- Ffi And Language InteropFFI and native interop rules: single documented pointer ownership, opaque handles, null-pointer checks, allocate/free pairs, unsafe-block invariants, generated C headers, stable C ABI, frozen struct layouts, and error/context conversion. Load when writing or reviewing FFI boundaries between native and host languages.Votes: 0GitHub stars: 146
- Rust Polyglot ConventionsRust conventions for a core that backs multiple language bindings: stable-edition tooling, typed Result errors with no panics in library paths, rustdoc with error docs, isolated unsafe, Send futures, FFI-friendly DTOs, and single-source version syncing. Load when writing or reviewing a Rust core exposed through polyglot bindings.Votes: 0GitHub stars: 146
- Dependency AwarenessPer-language dependency vulnerability audit tool reference (cargo audit/deny, pip-audit, npm/pnpm audit, govulncheck, bundler-audit, composer audit, OWASP dependency-check, dotnet vulnerable, mix_audit). Load when adding, updating, or auditing project dependencies, wiring up CI supply-chain checks, or triaging CVEs in a lock file.Votes: 0GitHub stars: 146
- Owasp Quick ReferenceOWASP Top 10 quick reference: the ten most critical web application security risks (access control, crypto, injection, insecure design, misconfiguration, vulnerable components, auth, integrity, logging, SSRF) each with a one-line mitigation. Load when reviewing code or designs for security vulnerabilities or threat modeling.Votes: 0GitHub stars: 146
- Tdd WorkflowTest-driven development discipline: RED (failing test) → GREEN (minimal code) → REFACTOR, delete-and-restart if production code was written first, and the test-type taxonomy (integration for API surfaces, unit for business logic, property for edge-case-heavy code). Load before starting a feature or bug fix, when reproducing a reported bug, or when deciding which kind of test a change needs.Votes: 0GitHub stars: 146
- Testing ConventionsHow to write a good test: behaviour-describing names (`should_return_error_when_input_is_empty`, `given_when_then`), exact-value assertions over truthiness, snapshot and property-based testing, order-independent and idempotent tests with no shared mutable state, and the anti-patterns (testing mocks, test-only production methods, mocking what you don't own, asserting implementation details). Load when writing or reviewing a test file, naming test cases, choosing assertions, or diagnosing a fla...Votes: 0GitHub stars: 146
- Incremental ApproachBuild in verified increments rather than one speculative block: smallest viable change first, verify, then extend; prototype the risky part before committing to a design; batch edits to one file into a single operation. Load when planning a large or multi-file change, when uncertain which of several approaches will work, or when tempted to generate a whole subsystem before running anything.Votes: 0GitHub stars: 146
- Task RunnerUse `task` (go-task) instead of raw build/test/lint commands in any repository whose root contains a Taskfile.yaml or Taskfile.yml, with the standard target names setup, build, test, lint, format, bench. Load on seeing a Taskfile.yaml/Taskfile.yml in the repository root, or before running a build, test, lint or format command in an unfamiliar repository.Votes: 0GitHub stars: 146
- ReviewReview a changeVotes: 0GitHub stars: 146
- Ai RulezManage AI assistant governance rules across 52 harnesses (Claude Code, Cursor, Codex, Copilot, Gemini CLI, OpenCode, Devin, and more) using ai-rulez. Use when configuring rules, context, skills, checks, hooks, permissions, domains, profiles, includes, plugins, or generating tool-specific outputs.Votes: 0GitHub stars: 146
- Backend OnlyBackend migration procedureVotes: 0GitHub stars: 146
- Big BodyShort.Votes: 0GitHub stars: 146
- Folded DescriptionA folded block scalar that spans several source lines, so a regex which stops at the end of the first line reads this description as the single character ">" and reports its cost as zero.Votes: 0GitHub stars: 146
- BasemindNavigate large codebases via the basemind MCP server.Votes: 0GitHub stars: 146
- Pr ReviewReviews a pull request against the team checklist.Votes: 0GitHub stars: 146
- Pr ReviewReviews a pull request against the team checklist.Votes: 0GitHub stars: 146