drydock

Scaffolds a shared repository harness of context, rules, tools, and standards surfaces.

38.9k|3.5k|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/Yeachan-Heo/oh-my-claudecode --skill drydock
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: drydock
Source: https://github.com/Yeachan-Heo/oh-my-claudecode/tree/main/skills/drydock
Command: npx skills add https://github.com/Yeachan-Heo/oh-my-claudecode --skill drydock

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Repositories where knowledge lives in chat history and people's heads force every new human or agent contributor to ask instead of read. Drydock lays the keel of a shared shipyard harness so every contributor inherits the same context, rules, tools, and standards from files in the repo.

Core Features & Use Cases

  • Four-pillar scaffolding: Creates and seeds CLAUDE.md, CONTEXT.md, docs/adr/, docs/standards/, docs/business/, design-system/, .omc/skills/, .mcp.json, and scripts/ without clobbering existing files.
  • Document language resolution: Detects or asks for a BCP-47 document language (including zh-Hans/zh-Hant script disambiguation) and persists it as the documentLanguage frontmatter key in CONTEXT.md.
  • Drift auditing with --check: Read-only mode that reports missing surfaces, invalid language tags, dead CLAUDE.md links, and unused glossary terms.
  • Use Case: When starting a repo that both humans and AI agents will build on, run drydock once to scaffold the harness, then let launch, retro, and code-review flows sediment decisions and standards into it over time.

Quick Start

Ask the agent to run the drydock skill in this repository to scaffold the shared shipyard harness and report what was created.

Frequently Asked Questions about drydock

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up a shared CLAUDE.md and context harness for a repo?

Run the drydock skill once per repository. It inventories existing files, asks only what detection cannot answer, then scaffolds CLAUDE.md, CONTEXT.md, docs/adr/, docs/standards/, docs/business/, design-system/, .omc/skills/, .mcp.json, and scripts/ with minimal seeds.

How do I audit drift in an existing shipyard harness?

Re-run drydock with the --check flag. It performs a read-only diff of the repo against the shipyard map, reporting missing surfaces, invalid documentLanguage tags, dead CLAUDE.md links, unused CONTEXT.md terms, and unreferenced standards.

Does drydock overwrite existing CLAUDE.md or AGENTS.md files?

No. Drydock detects before writing and never clobbers. If CLAUDE.md or AGENTS.md exists, it extends the file in place and creates the missing one only as a one-line pointer, never creating both fresh.

How does drydock handle Chinese document languages?

Chinese must resolve to an explicit script-qualified tag: zh-Hans or zh-Hant. Bare zh or region-only tags are treated as ambiguous and trigger one batched language question rather than guessing, and the resolved tag is persisted in CONTEXT.md frontmatter.

When should I not use drydock?

Skip it for throwaway prototypes with no collaborators, and for repos already running the harness, where you should use --check instead. It is designed for repos where humans and agents share long-term context.