skills.rest
nearmap
nearmapOFFICIAL
Explore all skills by this author →
WebsiteGitHub

init-repo

Configures Shipyard tracker settings and validates repository preflight checks.

1|1|Updated Jul 23, 2026
Search Tags:#migration#configuration#setup#JIRA#GitHub Projects#preflight#shipyard
One-click install
npx skills add https://github.com/nearmap/shipyard --skill init-repo-nearmap
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: init-repo
Source: https://github.com/nearmap/shipyard/tree/main/skills/init-repo
Command: npx skills add https://github.com/nearmap/shipyard --skill init-repo-nearmap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up a repository for Shipyard requires writing the right config files, migrating legacy environment variables, and verifying tracker connectivity — doing this by hand is error-prone and leaves repos in a half-configured state where every command fails preflight. ## Core Features & Use Cases - Layered config writing: Splits values between the shared tracked .shipyard/config.json and the personal gitignored .shipyard/config.local.json, keeping secrets in the environment only. - Legacy migration: Detects retired SY_* variables in .claude/settings.json env blocks and produces a per-variable worklist for moving them to the new config keys. - Live verification: Runs validate_config and a forced preflight read against the real tracker (Jira or GitHub Projects) so setup is proven, not assumed. - Use Case: A teammate clones an already-configured repo and runs the skill; it reads the committed config, asks only for their personal values, and confirms the tracker connection in a short exchange. ## Quick Start Ask the assistant to initialize Shipyard configuration for this repository and verify the tracker connection.

Frequently Asked Questions about init-repo

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

FAQPage Schema
How do I configure Shipyard for a new repository?▼

Run the init-repo skill, which reads any existing config, asks only for missing values like the tracker type and board column names, writes `.shipyard/config.json`, and verifies everything with a live preflight check.

How do I migrate legacy SY_* environment variables to Shipyard config?▼

The skill's validator names each retired SY_* variable still set in `.claude/settings.json` and the config key it now maps to. Move each value into the appropriate config file, then delete the variable from the env block.

Does Shipyard support both Jira and GitHub Projects?▼

Yes, the skill stays tracker-agnostic and loads the chosen tracker's adapter file to learn its required config keys, secrets, and one-time CLI login. The tracker is selected during setup or passed as an argument.

Where should Shipyard secrets and credentials be stored?▼

Credentials never go into either config file; they stay in the environment where the secret guard covers them. Shared non-secret values go in `.shipyard/config.json` and per-person values in the gitignored `.shipyard/config.local.json`.

Why does Shipyard preflight fail after configuration?▼

Common causes are a missing one-time CLI login for the tracker, a retired SY_* variable still set, or a credential placed in a config file. The skill stops with an action-needed block naming the exact fix.

Related Skills

Explore More Software Engineering Skills→
corticalstackcorticalstack
1

init

Bootstraps a project with AGENTS.md, tracker configuration, and cross-vendor review profiles.

Community
Intermediate
tkoguttkogut
1

om-pipeline-retro

Classify finished pull request pipeline runs and rank rework causes by wall-clock hours.

Community
Advanced
borderuxborderux
1

recursica-skill-layers

Applies Recursica layer rules for declaring token-scoped surfaces in application layouts.

Official
Intermediate
MearmanMearman
3

schema-validate

Validate JSON documents against a provided JSON Schema and report detailed errors.

Community
Intermediate