Skill Bay

Battle-tested agent skills for coding harnesses (Oh My Pi / OMP, Claude Code, and anything that loads skills/<name>/SKILL.md).

Not prompts for show — delivery playbooks: issue → green PR, zone-aware review, and resolving Request changes with evidence.

Skills

Skill	What it does
issue-to-green-pr	Full GitHub issue sprint: board hygiene, mandatory project-rules preflight, dependency/existing-PR gate, worktree isolation, parallel research, implementer + orchestrator verify, rules/context compliance, high-risk review, PR, CI babysit, handoff
pr-zone-reviewer	Strict PR review: rules/context preflight, zone/CODEOWNERS ownership gate, parallel analysis axes, severity rubric, cross-verify, natural tech-lead publish, no rubber stamps
resolve-pr-feedback	Your PR got Request changes / inline comments: inventory all threads, triage vs project rules (FIX / PUSHBACK / CLARIFY), fix only what is right, reply with evidence on the rest, push + CI + re-request review

Each skill is a single directory:

skills/<skill-name>/SKILL.md

---

Install

Option A — Oh My Pi (OMP) — global user skills

git clone https://github.com/ART1KZ/skill-bay.git ~/skill-bay
# later: git -C ~/skill-bay pull --ff-only

install_skill() {
  local name="$1"
  mkdir -p "$HOME/.omp/agent/skills/$name"
  cp "$HOME/skill-bay/skills/$name/SKILL.md" \
     "$HOME/.omp/agent/skills/$name/SKILL.md"
}

install_skill issue-to-green-pr
install_skill pr-zone-reviewer
install_skill resolve-pr-feedback

Project-local (only this repo):

for name in issue-to-green-pr pr-zone-reviewer resolve-pr-feedback; do
  mkdir -p ".omp/skills/$name"
  cp "$HOME/skill-bay/skills/$name/SKILL.md" ".omp/skills/$name/SKILL.md"
done

Restart the OMP session so discovery reloads.

Option B — Claude Code — global user skills

git clone https://github.com/ART1KZ/skill-bay.git ~/skill-bay

for name in issue-to-green-pr pr-zone-reviewer resolve-pr-feedback; do
  mkdir -p "$HOME/.claude/skills/$name"
  cp "$HOME/skill-bay/skills/$name/SKILL.md" \
     "$HOME/.claude/skills/$name/SKILL.md"
done

Restart Claude Code / start a new session.

Option C — one-liner update (both harnesses, all skills)

REPO=~/skill-bay
git -C "$REPO" pull --ff-only

for name in issue-to-green-pr pr-zone-reviewer resolve-pr-feedback; do
  for root in ~/.omp/agent/skills ~/.claude/skills; do
    mkdir -p "$root/$name"
    cp "$REPO/skills/$name/SKILL.md" "$root/$name/SKILL.md"
  done
done

Option D — npx skills (if you use the skills CLI)

npx skills add ART1KZ/skill-bay@issue-to-green-pr -g -y
npx skills add ART1KZ/skill-bay@pr-zone-reviewer -g -y
npx skills add ART1KZ/skill-bay@resolve-pr-feedback -g -y

(Exact package path may vary by CLI version — if it fails, use Option A/B.)

---

Usage

After install + session restart:

Ship an issue

/issue-to-green-pr #12

Review someone else's PR (zones + rules)

/pr-zone-reviewer 42

Resolve Request changes on your PR

/resolve-pr-feedback 42

or: «разбери request changes по моему PR #42, инлайны тоже»

Resolver should:

1. Collect all reviews + inline code comments
2. Preflight project rules/context
3. Triage each item: FIX / FIX-PARTIAL / PUSHBACK / CLARIFY / …
4. Fix only valid feedback; push back with evidence when wrong
5. Reply on the correct threads; push; CI; re-request review

---

Layout

skill-bay/
├── README.md
├── LICENSE
└── skills/
    ├── issue-to-green-pr/
    │   └── SKILL.md
    ├── pr-zone-reviewer/
    │   └── SKILL.md
    └── resolve-pr-feedback/
        └── SKILL.md

Compatibility

Harness	Skills path
Oh My Pi (OMP) user	~/.omp/agent/skills/<name>/SKILL.md
Oh My Pi project	<repo>/.omp/skills/<name>/SKILL.md
Claude Code user	~/.claude/skills/<name>/SKILL.md
Claude Code project	<repo>/.claude/skills/<name>/SKILL.md

Frontmatter requires name + description. OMP native discovery is non-recursive under skills/.

License

MIT — use, fork, ship. Keep attribution if you redistribute.