publish-docs

Copy Augur atlas, stories, and journeys into the docs repository and update navigation.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/Kord96/kordinate --skill publish-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: publish-docs
Source: https://github.com/Kord96/kordinate/tree/main/agents/charon/skills/publish-docs
Command: npx skills add https://github.com/Kord96/kordinate --skill publish-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates publishing of Augur-generated project architecture artifacts so teams do not have to manually copy atlas, stories, and journeys into the documentation site or hand-edit the home page navigation.

Core Features & Use Cases

  • Content sync: Copies atlas.json, story files, journey files, and optional manifest artifacts from local Augur output into the docs repository structure.
  • Navigation wiring: Reads and updates the docs site's index content to add or refresh a project LinkCard using the atlas purpose as the card description.
  • Repository workflow: Clones the docs repo, stages changes, commits with a descriptive message, and pushes to the main branch so the live site picks up updates.
  • Use Case: Publish a newly analyzed project's architecture to the canonical docs site and ensure the home page reflects the latest project purpose.

Quick Start

Use the publish-docs skill with the project name to copy its augur output into the docs repo and update the home page LinkCard.

Frequently Asked Questions about publish-docs

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

FAQPage Schema
How do I publish project architecture docs to a git repository automatically?

Publishing project architecture docs to a git repository is automated by cloning the docs repo, copying atlas, stories, and journeys files, and pushing the commit to update the live site.

What is the best way to update documentation site home page navigation with new project artifacts?

Updating documentation site home page navigation is handled by modifying the index file to add or refresh a project LinkCard using the atlas purpose as the card description during the publish workflow.

Do I need augur output files to automate documentation publishing?

Yes, you need augur output files including atlas.json, stories, and journeys to copy into the docs repository structure for the automated publishing process to work.

What git permissions are required to sync augur atlas and journey files to the docs website?

Syncing augur atlas and journey files requires git commit and push permissions to the docs repository, read access to the augur output path, and ability to modify index content.

Can I use manual copying instead of automating documentation navigation wiring?

Manual copying is possible, but automating the process prevents the need to hand-edit home page navigation and manually copy atlas, stories, and journeys into the documentation site.

Why does the docs publishing workflow clone the repository before copying files?

The docs publishing workflow clones the repository to stage changes locally, commit with a descriptive message, and push to the main branch so the live documentation site picks up updates.