リポジトリの README を読み込んでいます…
収集済み skill 81 件中 40 件を表示しています。
Manage 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,…
原文の言語: 英語
Use when demonstrating
原文の言語: 判定不能
Deploy the service <safely> & roll back on failure.
原文の言語: 英語
Summarize a diff for review.
原文の言語: 英語
Deploy the service safely.
原文の言語: 英語
Explain this project's directory layout. Use when asked where code lives; not for build instructions.
原文の言語: 英語
Summarise merged pull requests into a changelog entry. Use when preparing release notes; not for writing code.
原文の言語: 英語
Rust 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.
原文の言語: 英語
Go code conventions covering linting, formatting, table-driven tests, concurrency, modules and context usage. Load when writing or reviewing Go code.
原文の言語: 英語
Name git branches. Use when asked to name or rename a branch; not for commit messages.
原文の言語: 英語
Land a feature branch on main. Use when asked how to merge or finish a branch; not for syncing a branch with main.
原文の言語: 英語
Commit size policy. Use when asked how big a commit should be; not for message wording.
原文の言語: 英語
Keep a feature branch current with main. Use when asked how to update or sync a branch; not for merging it into main.
原文の言語: 英語
How to structure Go tests. Use when writing Go unit tests; not for integration tests.
原文の言語: 英語
Go 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…
原文の言語: 英語
Helps with Go programming tasks.
原文の言語: 英語
Go conventions.
原文の言語: 英語
Summarise a pull request for the reviewer. Use when asked to describe or summarise a PR; not for writing the code change itself.
原文の言語: 英語
How to review code for prompt-injection risks. Load when reviewing an integration that sends user or repository text to a language model.
原文の言語: 英語
Build 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…
原文の言語: 英語
Go 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.
原文の言語: 英語
Test-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…
原文の言語: 英語
Use `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…
原文の言語: 英語
Language-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…
原文の言語: 英語
Rules for keeping modules healthy. Use when asked to review a module; not for reviewing build files.
原文の言語: 英語
Write release notes from merged pull requests. Use when preparing a release; not for code changes.
原文の言語: 英語
Go style rules: error wrapping, linting and table-driven tests. Load when writing or reviewing Go code.
原文の言語: 英語
Deploy a build to the staging environment. Use when asked to ship to staging; not for production or rollbacks.
原文の言語: 英語
Format Go source files with gofmt. Use when asked to format Go code; not for linting.
原文の言語: 英語
Read-only: list TODO comments in the repository. Use when asked to find TODOs; not for editing files.
原文の言語: 英語
Lint README headings and links. Use when asked to check a README; it reports problems and never edits files.
原文の言語: 英語
Lint README headings and links. Use when asked to check a README; it reports problems and never edits files.
原文の言語: 英語
Test-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).
原文の言語: 英語
Useful testing guidance for developers.
原文の言語: 英語
Write a changelog from merged pull requests. Use when preparing a release; not for code changes.
原文の言語: 英語
Write commit messages. Use when asked to word or review a commit message; not for deciding how to split commits.
原文の言語: 英語
Deploy a build to production. Use when asked to release to production; not for staging or rollbacks.
原文の言語: 英語
Squash policy. Use when asked how to merge a branch's commits; not for commit wording.
原文の言語: 英語
Style for small Go unit tests. Use when writing Go tests with one or two cases; not for large suites.
原文の言語: 英語
Cut a release
原文の言語: 判定不能
このプロンプトをコピーして、使用中の AI アシスタントに送ってください。
Follow https://skillsmp.com/skill-install/prompt.md to install Agent Skills from https://github.com/Goldziher/ai-rulez.README を読み込めませんでした。リポジトリの Skill 一覧は下で引き続き確認できます。