Code Quality
doorkeeper-gem/doorkeeper
Maintain code health and architecture standards when implementing features or refactoring Doorkeeper.
Creates and refactors model and controller concerns for shared behavior.
$ npx skills add dilolabs/nosia --skill concern-patterns -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install dilolabs/nosia concern-patterns --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/dilolabs/nosia.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.vibe/skills/concern-patterns .claude/skills/concern-patterns && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "concern-patterns" agent skill from https://github.com/dilolabs/nosia/tree/main/.vibe/skills/concern-patterns into .claude/skills/concern-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "concern-patterns", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/dilolabs/nosia/tree/main/.vibe/skills/concern-patternsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add dilolabs/nosia --skill concern-patterns -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install dilolabs/nosia concern-patterns --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dilolabs/nosia.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.vibe/skills/concern-patterns .agents/skills/concern-patterns && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "concern-patterns" agent skill from https://github.com/dilolabs/nosia/tree/main/.vibe/skills/concern-patterns into .agents/skills/concern-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "concern-patterns", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add dilolabs/nosia --skill concern-patterns -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install dilolabs/nosia concern-patterns --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dilolabs/nosia.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.vibe/skills/concern-patterns .cursor/skills/concern-patterns && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "concern-patterns" agent skill from https://github.com/dilolabs/nosia/tree/main/.vibe/skills/concern-patterns into .cursor/skills/concern-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "concern-patterns", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/dilolabs/nosia.git --path .vibe/skills/concern-patterns--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add dilolabs/nosia --skill concern-patterns -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install dilolabs/nosia concern-patterns --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dilolabs/nosia.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.vibe/skills/concern-patterns .gemini/skills/concern-patterns && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "concern-patterns" agent skill from https://github.com/dilolabs/nosia/tree/main/.vibe/skills/concern-patterns into .gemini/skills/concern-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "concern-patterns", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install dilolabs/nosia concern-patternsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add dilolabs/nosia --skill concern-patterns -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/dilolabs/nosia.git skills-src && mkdir -p .github/skills && cp -r skills-src/.vibe/skills/concern-patterns .github/skills/concern-patterns && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "concern-patterns" agent skill from https://github.com/dilolabs/nosia/tree/main/.vibe/skills/concern-patterns into .github/skills/concern-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "concern-patterns", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add dilolabs/nosia --skill concern-patterns -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install dilolabs/nosia concern-patterns --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dilolabs/nosia.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.vibe/skills/concern-patterns .opencode/skills/concern-patterns && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "concern-patterns" agent skill from https://github.com/dilolabs/nosia/tree/main/.vibe/skills/concern-patterns into .opencode/skills/concern-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "concern-patterns", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
concern-patternsCreates and refactors model and controller concerns for shared behavior.
Concern Patterns is an agent skill from dilolabs/nosia. Creates and refactors model and controller concerns for shared behavior. Use when extracting shared code, organizing models with horizontal concerns, DRYing up controllers, or when user mentions concerns, mixins, or modules. WHEN NOT: Logic used by only one model (keep in place), service object extraction (use model-patterns), or job organization (use job-patterns).
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/concern-catalog.md`). Compatibility notes: Ruby 3.3+, Rails 8.0+
It sits in Development, covering Refactoring. It works with Ruby on Rails. The repository describes itself as: Self-hosted AI RAG + MCP Platform. The licence is MIT.
4 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 0ef5e5d. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
railsFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Ruby 3.3+, Rails 8.0+
From compatibility in the SKILL.md frontmatter.
Concern Patterns loads about 1.8k tokens when it runs, and up to ~3.1k if it reads all its reference files. Until then it costs about 96 tokens; SKILL.md has 325 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from dilolabs/nosia at commit 0ef5e5d, republished under its MIT licence (© dilolabs). 325 words, ~1,801 tokens.
.claude/skills/concern-patterns/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.Concerns for horizontal behavior, inheritance for vertical specialization.
Tech Stack: Rails 8.2 (edge), ActiveSupport::Concern
Location: app/models/[model]/ for model concerns, app/controllers/concerns/ for controller concerns
Commands:
ls app/models/concerns/ # List shared concerns
ls app/models/card/ # List Card concerns
bin/rails runner "puts Card.included_modules" # Check usage
bin/rails test test/models/ # Run model testsEach concern should be:
Closeable, Watchable, Searchable)Repeated associations across models
# Multiple models have:
has_many :comments, as: :commentable
# Extract to: app/models/concerns/commentable.rbRepeated state patterns
# Multiple models have close/reopen pattern
# Extract to: Card::Closeable, Board::Publishable, etc.Repeated scopes
# Multiple models have:
scope :recent, -> { order(created_at: :desc) }
# Extract to: Timestampable concernRepeated controller patterns
# Multiple controllers load parent resource
# Extract to: ParentScoped concern# app/models/card/closeable.rb
module Card::Closeable
extend ActiveSupport::Concern
included do
has_one :closure, dependent: :destroy
scope :open, -> { where.missing(:closure) }
scope :closed, -> { joins(:closure) }
end
def close(user: Current.user)
create_closure!(user: user)
track_event "card_closed", user: user
end
def reopen
closure&.destroy!
track_event "card_reopened"
end
def closed?
closure.present?
end
def open?
!closed?
end
def closed_at
closure&.created_at
end
def closed_by
closure&.user
end
end# app/models/card/assignable.rb
module Card::Assignable
extend ActiveSupport::Concern
included do
has_many :assignments, dependent: :destroy
has_many :assignees, through: :assignments, source: :assignee
scope :assigned_to, ->(users) { joins(:assignments).where(assignments: { assignee: users }).distinct }
scope :unassigned, -> { where.missing(:assignments) }
end
def assign(user)
assignments.create!(user: user) unless assigned_to?(user)
track_event "card_assigned", user: user, particulars: { assignee_id: user.id }
end
def unassign(user)
assignments.where(user: user).destroy_all
end
def assigned_to?(user)
assignees.include?(user)
end
end# app/models/card/searchable.rb
module Card::Searchable
extend ActiveSupport::Concern
included do
scope :search, ->(query) { where("title LIKE ? OR body LIKE ?", "%#{query}%", "%#{query}%") }
end
class_methods do
def search_with_ranking(query)
search(query).order("search_rank DESC")
end
def top_results(query, limit: 10)
search_with_ranking(query).limit(limit)
end
end
end# app/controllers/concerns/card_scoped.rb
module CardScoped
extend ActiveSupport::Concern
included do
before_action :set_card
before_action :set_board
end
private
def set_card
@card = Current.account.cards.find(params[:card_id])
end
def set_board
@board = @card.board
end
def render_card_replacement
respond_to do |format|
format.turbo_stream do
render turbo_stream: turbo_stream.replace(
dom_id(@card, :card_container),
partial: "cards/container",
locals: { card: @card.reload }
)
end
format.html { redirect_to @card }
end
end
endCloseable, Publishable, Watchable, Assignable, Searchable, Eventable, Broadcastable, Readable, PositionableCardScoped, BoardScoped, FilterScoped, CurrentRequest, CurrentTimezone, Authentication# test/models/concerns/closeable_test.rb
class CloseableTest < ActiveSupport::TestCase
setup do
@card = cards(:logo)
end
test "close creates closure record" do
assert_difference -> { Closure.count }, 1 do
@card.close
end
assert @card.closed?
end
test "reopen destroys closure record" do
@card.close
assert_difference -> { Closure.count }, -1 do
@card.reopen
end
assert @card.open?
end
test "closed scope finds closed records" do
@card.close
assert_includes Card.closed, @card
refute_includes Card.open, @card
end
endapp/models/[model]/[concern].rb or app/controllers/concerns/[concern].rbinclude ConcernName to models/controllersapp/models/card/closeable.rb or app/controllers/concerns/card_scoped.rbinclude ConcernNametest/models/concerns/closeable_test.rbSee references/concern-catalog.md for the full catalog of concern types.
extend ActiveSupport::Concern, namespace model concerns under the modelincluded do block for callbacks/associations, create concerns for one-off code© dilolabs, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 1 other file (references) in .vibe/skills/concern-patterns of dilolabs/nosia.
Open the folder on GitHubat commit 0ef5e5d
We found 3 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in dilolabs/nosia, which our catalogue first saw on October 7, 2026.
Concern Patterns next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Concern Patterns this skilldilolabs/nosia | 213 | 1 repos | ~1.8k | Automated safety check: Pass | MIT | |
| Code Qualitydoorkeeper-gem/doorkeeper | 5.5k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Rails ArchitectureThibautBaissac/rails_ai_agents | 665 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Rubyericrisco/rsc-harness | 156 | — | ~3.2k | Automated safety check: Pass | MIT | |
| Ruby Optimisepproenca/dot-skills | 214 | — | ~1.7k | Automated safety check: Pass | MIT | |
| Antipattern Preventiondoorkeeper-gem/doorkeeper | 5.5k | — | ~1.1k | Automated safety check: Pass | MIT |
doorkeeper-gem/doorkeeper
Maintain code health and architecture standards when implementing features or refactoring Doorkeeper.
ThibautBaissac/rails_ai_agents
Guides modern Rails 8 code architecture decisions and patterns.
ericrisco/rsc-harness
A skill your agent uses when writing or refactoring plain Ruby outside Rails — scripts, CLIs, gems, libraries: Enumerable chains and blocks, module mixins and value objects, Bundler/gemspec…
pproenca/dot-skills
Ruby performance optimization guidelines. An agent skill from pproenca/dot-skills.
doorkeeper-gem/doorkeeper
Avoid common Ruby and Rails antipatterns that degrade maintainability and performance.
evilmartians/redprints-cfp
Write, refactor, and review Rails code using layered architecture principles from "Layered Design for Ruby on Rails Applications".
dilolabs/nosia
Builds REST APIs using respondto blocks with Jbuilder templates following the 37signals same-controllers-different-formats philosophy.
dilolabs/nosia
Implements custom passwordless authentication without Devise.
dilolabs/nosia
Implements HTTP caching with ETags, fragment caching, Russian doll caching, and Solid Cache configuration.
dilolabs/nosia
Builds event tracking, activity feeds, and webhook systems following 37signals patterns with a generic Event model and Eventable concern.
dilolabs/nosia
Implements shallow background jobs with later/now conventions using Solid Queue.
dilolabs/nosia
Creates minimal Action Mailer classes with bundled notification patterns following 37signals conventions.
Works with
Categories
Creates and refactors model and controller concerns for shared behavior. Concern Patterns is an agent skill from dilolabs/nosia. Creates and refactors model and controller concerns for shared behavior.
Concern Patterns fits situations like: extracting shared code; organizing models with horizontal concerns; DRYing up controllers; user mentions concerns.
Run `npx skills add dilolabs/nosia --skill concern-patterns -a claude-code`. Or copy the skill folder (.vibe/skills/concern-patterns in dilolabs/nosia) into .claude/skills/concern-patterns in your project. Claude Code loads it when a task matches its description.
Run `npx skills add dilolabs/nosia --skill concern-patterns -a codex`. Or copy the skill folder (.vibe/skills/concern-patterns in dilolabs/nosia) into .agents/skills/concern-patterns in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add dilolabs/nosia --skill concern-patterns -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/concern-patterns, .gemini/skills/concern-patterns, .github/skills/concern-patterns and .opencode/skills/concern-patterns in your project.
Going by SKILL.md and its folder, Concern Patterns needs the command-line tools its instructions call (rails). Compatibility (from SKILL.md): Ruby 3.3+, Rails 8.0+.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Concern Patterns is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.8k tokens (SKILL.md is roughly 7.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.3k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Concern Patterns: Code Quality (doorkeeper-gem/doorkeeper, 5.5k stars), Rails Architecture (ThibautBaissac/rails_ai_agents, 665 stars), Ruby (ericrisco/rsc-harness, 156 stars) and Ruby Optimise (pproenca/dot-skills, 214 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
dilolabs (a GitHub organization) maintains it in dilolabs/nosia, which has 213 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on September 9, 2026.
Source: dilolabs/nosia on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.