All authors
Claude Skills by Goldziher
github.com/Goldziher115 skills0 installs77 views
- Repository LayoutRepository LayoutVotes: 0GitHub stars: 150
- 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: 150
- 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
- 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: 150
- LintRun the project linters and fix what they reportVotes: 0GitHub stars: 150
- ReleaseCut a releaseVotes: 0GitHub stars: 150
- Clean BranchesClean up unnecessary local branches and prune stale remote-tracking branchesVotes: 0GitHub stars: 150
- Clean BranchesClean up unnecessary local branches and prune stale remote-tracking branchesVotes: 0GitHub stars: 150
- Release NotesDraft release notes from merged pull requestsVotes: 0GitHub stars: 150
- DeployDeploy the service safely.Votes: 0GitHub stars: 150
- Layout ExplainerExplain this project's directory layout. Use when asked where code lives; not for build instructions.Votes: 0GitHub stars: 150
- Changelog SummariserSummarise merged pull requests into a changelog entry. Use when preparing release notes; not for writing code.Votes: 0GitHub stars: 150
- 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: 150
- Go ConventionsGo code conventions covering linting, formatting, table-driven tests, concurrency, modules and context usage. Load when writing or reviewing Go code.Votes: 0GitHub stars: 150
- Branch NamingName git branches. Use when asked to name or rename a branch; not for commit messages.Votes: 0GitHub stars: 150
- Merge PolicyLand a feature branch on main. Use when asked how to merge or finish a branch; not for syncing a branch with main.Votes: 0GitHub stars: 150
- Commit SizeCommit size policy. Use when asked how big a commit should be; not for message wording.Votes: 0GitHub stars: 150
- Rebase PolicyKeep a feature branch current with main. Use when asked how to update or sync a branch; not for merging it into main.Votes: 0GitHub stars: 150
- Test StructureHow to structure Go tests. Use when writing Go unit tests; not for integration tests.Votes: 0GitHub stars: 150
- 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. Do not use for build or CI pipeline questions, or for other languages.Votes: 0GitHub stars: 150
- Go ConventionsHelps with Go programming tasks.Votes: 0GitHub stars: 150
- Go ConventionsGo conventions.Votes: 0GitHub stars: 150
- Pr SummarySummarise a pull request for the reviewer. Use when asked to describe or summarise a PR; not for writing the code change itself.Votes: 0GitHub stars: 150
- Prompt Injection ReviewHow to review code for prompt-injection risks. Load when reviewing an integration that sends user or repository text to a language model.Votes: 0GitHub stars: 150
- 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: 150
- 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: 150
- 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: 150
- 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: 150
- 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: 150
- Module RulesRules for keeping modules healthy. Use when asked to review a module; not for reviewing build files.Votes: 0GitHub stars: 150
- Release NotesWrite release notes from merged pull requests. Use when preparing a release; not for code changes.Votes: 0GitHub stars: 150
- Golang Style GuideGo style rules: error wrapping, linting and table-driven tests. Load when writing or reviewing Go code.Votes: 0GitHub stars: 150
- Deploy StagingDeploy a build to the staging environment. Use when asked to ship to staging; not for production or rollbacks.Votes: 0GitHub stars: 150
- Go FormatterFormat Go source files with gofmt. Use when asked to format Go code; not for linting.Votes: 0GitHub stars: 150
- Todo ListerRead-only: list TODO comments in the repository. Use when asked to find TODOs; not for editing files.Votes: 0GitHub stars: 150
- Readme LinterLint README headings and links. Use when asked to check a README; it reports problems and never edits files.Votes: 0GitHub stars: 150
- Readme LinterLint README headings and links. Use when asked to check a README; it reports problems and never edits files.Votes: 0GitHub stars: 150
- Tdd WorkflowTest-driven development discipline: RED (failing test), GREEN (minimal code), REFACTOR. Load before starting a feature or bug fix, or when reproducing a reported bug. Not for naming tests or choosing assertions (see testing-conventions).Votes: 0GitHub stars: 150
- Testing GuidanceUseful testing guidance for developers.Votes: 0GitHub stars: 150
- Changelog WriterWrite a changelog from merged pull requests. Use when preparing a release; not for code changes.Votes: 0GitHub stars: 150
- Commit WordingWrite commit messages. Use when asked to word or review a commit message; not for deciding how to split commits.Votes: 0GitHub stars: 150
- Deploy ProductionDeploy a build to production. Use when asked to release to production; not for staging or rollbacks.Votes: 0GitHub stars: 150
- Squash PolicySquash policy. Use when asked how to merge a branch's commits; not for commit wording.Votes: 0GitHub stars: 150
- Test Style SimpleStyle for small Go unit tests. Use when writing Go tests with one or two cases; not for large suites.Votes: 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