Nearmap
Official@nearmap · Sydney, Australia
Nearmap brings the real world to you
Agent Skills by Nearmap
Showing 13 vetted skills indexed across 1 GitHub repositories.
nearmapexplain
Authors and runs layered explainer docs that teach complex technical topics through interactive checkpoints.
nearmapconfig
Inspect, validate, change, and reload layered Shipyard configuration values with provenance.
nearmapci
Triage, diagnose, and fix the current branch's CI failures until green.
nearmapplan
Turns large objectives into living Epic roadmaps with capped executable tasks.
nearmapspec
Turns a fuzzy goal or task into a versioned, execution-ready plan posted to an issue tracker.
nearmaptracker
Dispatches canonical issue-tracker operations to configured Jira or GitHub Projects adapters.
nearmappr
Create, promote, and merge GitHub pull requests with verified-head commit gating.
nearmaptighten
Rewrites drafted text denser by cutting structural padding while preserving every fact.
nearmapinit-repo
Configures Shipyard tracker settings and validates repository preflight checks.
nearmapspike
Runs falsifiable experiments to decide whether an idea warrants a project.
nearmapship
Execute a planned task into a reviewed pull request with isolated workers and immutable CI coverage.
nearmaphelp
Answers questions about Shipyard configuration and workflow by reading bundled plugin documentation.
nearmapstandards
Resolves authoritative repository engineering policy or runs cited conformance reviews.
Frequently Asked Questions About Nearmap
FAQPage SchemaWhat tasks can I accomplish with Nearmap's Shipyard skills?▼
You can plan epics into capped active tasks, write execution-ready specs, run falsifiable spikes, dispatch Jira or GitHub Projects tracker operations, triage and fix CI failures, create and clean up GitHub PRs, tighten drafted text, and resolve repository engineering standards.
Who are the Shipyard skills designed for?▼
Software engineers and technical leads working in repositories that use Jira or GitHub Projects for issue tracking and GitHub for pull requests. It suits teams practicing spec-driven development who want structured planning, isolated review, and durable task accounting.
How do I set up Shipyard in a repository?▼
Run the init-repo skill, which writes .shipyard/config.json (shared, tracked) and .shipyard/config.local.json (personal, gitignored), retires legacy SY_* env variables, and proves the setup live with the same preflight check every other command runs.
What are the prerequisites and dependencies for Shipyard skills?▼
A configured Shipyard setup via init-repo, plus a supported issue tracker adapter: Jira or GitHub Projects. CI triage and PR skills require a GitHub repository with active CI runs. Secrets are never printed or accepted by the config skill.
Can Shipyard skills merge pull requests or read secrets?▼
No. The ci skill fixes and re-watches runs but never merges. The config skill never prints or accepts secrets. The pr skill manages descriptions and review threads, while ship executes planned tasks to a reviewable PR with independent review.