other · Found in 3 repositories

om-auto-implement-spec

Implement an existing spec and ship a verified, reviewed, ready PR. Resolves the spec by path, name, issue, or spec-PR number (clean stop with candidates when not found). A spec PR stays design-only — implementation ships on its own PR referencing it. Delegates to om-auto-create-pr (om-auto-continue-pr for an existing implementation PR), then runs the review loop and UI verification with screenshots. Use for "implement the spec X", "build spec from issue 123".

Install

Install with the skills CLI. It asks which coding agents to install into:

npx skills add 'polo-blue/sds/.claude/skills/om-auto-implement-spec/SKILL.md#main'

Or install globally for one agent:

# Claude Code → ~/.claude/skills/
npx skills add 'polo-blue/sds/.claude/skills/om-auto-implement-spec/SKILL.md#main' -g -a claude-code
# Codex → ~/.agents/skills/
npx skills add 'polo-blue/sds/.claude/skills/om-auto-implement-spec/SKILL.md#main' -g -a codex
# Cursor → ~/.cursor/skills/
npx skills add 'polo-blue/sds/.claude/skills/om-auto-implement-spec/SKILL.md#main' -g -a cursor

Manual install locations: Claude Code ~/.claude/skills/, Codex ~/.agents/skills/, Cursor ~/.cursor/skills/. Source-path status is inferred from metadata; it does not verify a live download. Scan and quality scores describe registry checks and are not a guarantee of safety.

What the registry checked

Scanned 2026-11-16 by registry scanner 1.1.7 (ruleset 371c677df515, content fd212e0399f5).

  • File size limit
  • Frontmatter and schema
  • Dangerous code patterns
  • Sensitive file paths
  • Bundled scripts and support files
  • Blocked source repositories
  • Prompt injection phrases
  • Hardcoded credentials
  • Obfuscated execution chains

Findings: 1 warning: sensitive path (1).

Checks are pattern-based and cover the archived copy; they do not guarantee the skill is safe.

Content history

  1. 2026-11-14 → 2026-11-16 Matches the author's file; the skill ships extra filessha256:50b8a36e5081 · 1 file

Each entry is a period in which the archived files (SHA-256 per file) and their match against the author's repository stayed the same. Upstream checks run at most weekly, so detection can lag.

Attribution and permissions

Check the original repository for permission and license terms before reuse. Registry metadata does not grant a license.

This guide links to the author’s instructions and includes metadata only.

Request removal or correct attribution

For the skill author

Add this badge to your README to link readers to the registry home:

Listed on Claude Skills Registry

[![Listed on Claude Skills Registry](https://majiayu000.github.io/claude-skill-registry/assets/listed-badge.svg)](https://majiayu000.github.io/claude-skill-registry/)

Copies with matching content

Exact Markdown body copies across 3 repositories. This count does not identify the original author.

More in other