sorah-guides

Plugin sorah-guides from marketplace sorah-marketplace in sorah/config. Commands read from the repo's manifest — 5 days ago.

Skills (23)

• coding

  This skill should be used when writing or reviewing code in any language. Provides language-agnostic coding conventions for code quality, comments, error handling, and formatting. Project-specific conventions always take priority.

• commit-style

  This skill should be used when writing git commit messages, creating git commits, composing pull request titles and descriptions, or when the user asks to "commit", "git commit", "write commit message", "pull request", or "PR description". Provides conventions for subject lines, prefix patterns, bod

• dsql-on-rails

  This skill should be used when building, extending, or testing a Rails app on Amazon Aurora DSQL, or when moving a Rails app onto DSQL. Use it when writing a transaction, a uniqueness check, a schema change, a spec, a rake task, or CI for such an app, even if the user only says "add a model" or "fix

• english-text

  This skill should be used when writing English text on behalf of the user, such as GitHub issue/PR descriptions, code review comments, replies to maintainers or contributors, commit message bodies, business emails, or when the user asks to "write in English", "draft a reply", "write a PR description

• github-ci

  This skill should be used when writing, editing, or reviewing GitHub Actions workflows (`.github/workflows/*.yml`, composite actions in `.github/actions/`), or when setting up CI, a release pipeline, a Docker image build, or gem/crate publishing for a project. Use it whenever the user mentions "GitH

• japanese-text

  This skill should be used when writing Japanese text, blog posts, diary entries, technical articles, prose, or when the user asks to write in Japanese, compose a blog post, draft a diary entry, or write technical content in Japanese. Provides writing style, orthography, and composition conventions a

• rails-canonical-log-line

  This skill should be used when making a Rails app's request log answer who made a request and how it went, such as when the ActionController "Completed" line lacks the user, session or error behind a request, when tags set in an `around_action` with `logger.tagged` are missing from the Completed lin

• rails-on-lambda

  This skill should be used when deploying, running, or debugging a Rails app on AWS Lambda, or when moving a Rails app from ECS, App Runner, Heroku or a VM onto Lambda. Use it when touching the Dockerfile, an entrypoint, a Lambda handler, ActiveJob on SQS, secrets loading, CloudFront in front of a fu

• rails-problem

  This skill should be used when designing, writing, or reviewing error handling in a Rails API that answers RFC 9457 / RFC 7807 problem details through the `problem` gem, or when adding an error class, a `rescue_from`, an exceptions app, or an error response shape to a Rails API. Signs include `Probl

• rails-protobuf

  This skill should be used when building, extending, or reviewing a Rails app whose API schema is Protocol Buffers, served with connect_rpc_rails (Connect RPC as controller actions) and protobufable (protobuf request bodies, responses, columns, errors). Use it when adding an RPC, a `.proto` message,

• rails

  This skill should be used when writing or reviewing Ruby on Rails code, or when the project uses "Rails", "ActiveRecord", "ActiveJob", "concerns", "migrations", "Rails.configuration", "request specs", or "controller". Provides Rails coding conventions, patterns, and best practices. Project-specific

• readme

  This skill should be used when the user asks to "write a README", "create a README", "improve the README", "polish the README", "rewrite README.md", "make the README look good", "prepare a project for open-sourcing", or asks how to promote or present an OSS library, gem, crate, CLI tool, or service.

• ruby

  This skill should be used when writing or reviewing Ruby code, or when the project uses "Ruby", "RSpec", "service objects", "Struct", "Data class", or Ruby class/module patterns. Provides Ruby coding conventions, patterns, and best practices. Project-specific conventions always take priority.

• rust

  This skill should be used when writing or reviewing Rust code, or when the project uses "Rust", "Cargo", "cargo clippy", "crate", or Rust module patterns. Provides Rust coding conventions, patterns, and best practices. Project-specific conventions always take priority.

• security

  This skill should be used when reviewing code for security vulnerabilities, performing security audits, or when the user asks about "security review", "vulnerability", "XSS", "CSRF", "injection", "race conditions", "OAuth security", "OIDC pitfalls", "timing attacks", or "access control". Provides a

• sorbet-adoption

  This skill should be used when introducing Sorbet static type checking to an existing Ruby or Rails application, or when continuing such a rollout. It applies when the user asks to "add type checking", "adopt Sorbet", "set up Sorbet and tapioca", "add RBS types to the codebase", "type the app gradua

• sorbet

  This skill should be used when writing, reviewing, or fixing types in a Ruby or Rails project typechecked by Sorbet with inline RBS comments, or when adding a Ruby file to such a project. Signs include a `sorbet/config` file, `# typed:` sigils, `#:` signature comments, or the user mentioning "Sorbet

• sqldef-on-rails

  This skill should be used when a Rails app manages its PostgreSQL schema declaratively with psqldef (sqldef) instead of ActiveRecord migrations, or when setting that up, changing a table, or replacing `db/migrate`. Signs include `db/schema/*.sql`, a `psqldef` call in a rake file, `BEFORE_APPLY_SQL`,

• steep-adoption

  This skill should be used when introducing static type checking to an existing Ruby library or gem, or when continuing such a rollout. It applies when the user asks to "add type checking to this gem", "adopt Steep", "add RBS signatures", "set up rbs-inline", "ship sig/ with the gem", "add a Steepfil

• steep

  This skill should be used when writing, reviewing, or fixing types in a Ruby library or gem typechecked by Steep, or when adding a Ruby file to such a project. Signs include a `Steepfile`, `rbs_collection.yaml`, a `sig/` directory (`sig/generated`, `sig/manual`, `sig-stub`), `# rbs_inline: enabled`

• terraform

  This skill should be used when writing or reviewing Terraform code, or when the project uses "Terraform", "HCL", "tfvars", "aws_iam_role", "data sources", or infrastructure-as-code patterns. Provides Terraform coding conventions, patterns, and best practices. Project-specific conventions always take

• toolchain

  This skill should be used when setting up or changing a project's developer toolchain with mise and hk, such as creating or editing `mise.toml`, `mise.lock` or `hk.pkl`, adding a tool, a task, a linter, a formatter, a code generator or a pre-commit hook, or scaffolding a new gem, app or repository.

• typescript

  This skill should be used when writing or reviewing TypeScript or TSX code, or when the project uses "TypeScript", "React", "tsx", "SWR", "Vite", "Next.js", or TypeScript type patterns. Provides TypeScript coding conventions, React patterns, and best practices. Project-specific conventions always ta

Slash commands (3)

• /sorah-guides:commit

  Create git commit(s) following sorah's commit style conventions

• /sorah-guides:perform-security-review

  Perform a thorough security review of code changes

• /sorah-guides:pull-request

  Create a GitHub pull request following sorah's commit/PR style

Subagents (1)

• security-reviewer

  Use this agent when performing security reviews of code changes, auditing for vulnerabilities, or when the user asks to "review security", "check for vulnerabilities", "security audit", or "perform security review". Examples: