Skip to content
unversioned · 055a1834eac5

Development workflow and coding standards skills

branch

Start a branch, either from the default branch or stacked on the current branch. Invoke before the first commit when no usable branch exists yet, when the user asks to split work into a separate pull request, when a change must be merged or released separately (e.g. an API that ships before its client), or when groundwork is better reviewed and merged on its own — never just because a follow-up request could stand alone.

coding-standards

Standards for writing, editing, or reviewing code. Load before any code change, however small.

commit

Create a git commit with Conventional Commits format. Invoke as soon as changes are ready — staging and message authoring are part of this workflow.

fixup

Create a fixup commit and autosquash rebase

git-workflow

Mandatory for every git/GitHub operation in development — branch, commit, push, pull request, issue, review/CI feedback, sync, squash. Load before running any, even for a bare "commit" or "push", and even when the repository has its own git rules.

ruby-on-rails-best-practices

Ruby on Rails conventions. Load before writing or reviewing Rails code, or running rails, rspec, rubocop, rake, or other gem executables.

squash

Squash all branch commits into a single commit

sync

Sync feature branch with its base via rebase

textlint

Auto-format Japanese prose with textlint — katakana loanword replacement, half-width spacing and parentheses, ja-technical-writing rules. Use on any Japanese text before it is published or committed — drafts (PR descriptions, issue bodies, review replies, documents) and Japanese text in source files (code comments, docstrings, test case titles) — or when asked to lint/format Japanese text.