polidog

Omasushi — Development skill for Claude Code

Development community

Share your Omarchy setup as a recipe repo: packages, plugins, dotfiles, Claude Code skills.

How to install Omasushi

This entry records only its repository, not the path inside it, so there is no exact command to give. Open polidog/omasushi and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Omasushi does

Share your Omarchy setup as a recipe repo: packages, plugins, dotfiles, Claude Code skills.

Alternatives in Development

Gemini CLI Foundations — This repository is a comprehensive skills library for Gemini CLI - reusable, production-ready skill packages t 5.3k ★
Fix Cookbook Recipe — Fix Cookbook Recipe Validation Failures 2.1k ★
Cq — An open standard for shared agent learning 1.3k ★

README

omasushi

English | [日本語](README.ja.md)

Add a feature to a stock [Omarchy](https://omarchy.org) machine — Japanese input, tmux-style keys for herdr, a font setup — as one unit: the packages, the Omarchy plugins, the font and default apps, the config it needs, the agent skills. Diff the machine against it, sync, hand it to someone else.

omasushi use polidog/omakase/ime     # take one pack from a repo
omasushi diff                        # what is missing on this machine
omasushi sync                        # install it, link it

Packs

A **pack** is a directory with an `omasushi.yaml` and the files it refers to. It declares everything one feature needs on top of stock Omarchy:

herdr/
├── omasushi.yaml
├── files/herdr/config.toml
└── hypr/herdr.lua           # a hyprland snippet, loaded alongside other packs'

# herdr/omasushi.yaml — tmux-style herdr: prefix ctrl+b, the plugins it drives,
# and the bar widget that shows agent status.
description: herdr with tmux-style keybindings
packages:
  pacman: [fcitx5, jq]
omarchy:
  plugins:
    - url: https://github.com/fabean/omarchy-herdr.git
      enable: true
herdr:
  plugins:
    - source: polidog/herdr-gh-issue-label
files:
  files/herdr/config.toml: ~/.config/herdr/config.toml
hypr: hypr/herdr.lua

A repo is a set of packs: every subdirectory with an `omasushi.yaml` is one. The root `omasushi.yaml` only names the repo.

omakase/
├── omasushi.yaml     # name: omakase / description: polidog's packs
├── ime/
├── fonts/
├── kitty/
└── herdr/

`omasushi use owner/repo/herdr` takes one pack; `omasushi use owner/repo` takes them all. Packs from different repos stack: `diff` names the pack behind each pending action (`install fcitx5-mozc <- omakase/ime`).

`omasushi use owner/repo/herdr@v1.2.0` pins it: the checkout stays at that tag (or branch, or commit) and `update` re-fetches the ref instead of pulling. `use owner/repo/herdr` again lets it float. A repository is one checkout, s