Claude Tools / Commands / optimiziramsi-skills
Commands · optimiziramsi/skills
optimiziramsi-skills
optimiziramsi's Claude Code toolkit as ONE plugin, organized topic-first — one folder per concern (git, commit, reporting, session, review, repo, instructions, flow, patterns, worktree, setup), each owning its own skills/commands/agents/hooks. Opinionated concerns carry env kill-switches; guards self-gate on project config.
CLEARED_STATICclaude-onlyv0.0.10
Pipeline results
Coverage
CLEARED_STATIC
Tests run
7 / 8
Portability
Claude-only
Type
Commands
Tests & results
What the pipeline checked
What's inside
Components found
commit/commands/commit.md
componentmedium
flow/commands/collab.md
componentmedium
flow/commands/feedback.md
componentmedium
flow/commands/grind.md
componentmedium
flow/commands/looper.md
componentmedium
flow/commands/milestone.md
componentmedium
flow/commands/plan.md
componentmedium
flow/commands/scope-cut.md
componentmedium
flow/commands/triage-todo.md
componentmedium
git/commands/hotfix.md
componentmedium
instructions/agents/instructions-auditor.md
componentmedium
instructions/agents/lesson-scout.md
componentmedium
instructions/commands/instructions-audit.md
componentmedium
instructions/commands/instructions-maintenance.md
componentmedium
instructions/commands/lessons.md
componentmedium
instructions/commands/retro.md
componentmedium
instructions/commands/rules-change.md
componentmedium
patterns/agents/pattern-compliance.md
componentmedium
patterns/agents/pattern-verifier.md
componentmedium
patterns/commands/manage-patterns.md
componentmedium
Coverage
Not assessed
- behavioural execution not run
- egress patterns logged (FLAG-INFO): 1 lexical match(es)
README
From the repository
# optimiziramsi-skills — Claude Code toolkit
A personal [Claude Code plugin marketplace](https://docs.claude.com/en/docs/claude-code/plugins)
shipping **one plugin**: reusable **skills, commands, agents, and hooks** shared across all my
projects — so I solve something once and get it everywhere, and update it in one place. The repo
root *is* the plugin, organized **topic-first**: `.claude-plugin/{marketplace,plugin}.json` at
root, then one folder per concern (`git/ commit/ flow/ …`), each owning its own
`skills/ commands/ agents/ hooks/` — so everything for a topic is in one place. `plugin.json`
declares the component paths, so the type dirs don't need to sit at the repo root.
## Install
From a `claude` session in the project you want it in:
```bash
claude plugin marketplace add optimiziramsi/skills
```
```bash
claude plugin install optimiziramsi-skills@optimiziramsi
```
Then **restart** — plugins bind at session start. (`/plugin` does the same from inside a session;
in CCD use Browse → the plugin page → **"Install for project (shared)"** so the enable travels with
the repo.)
Declaring it in settings instead — marketplace global, enablement in the project's
`.claude/settings…