share-docs

Promote personal documents to a shared namespace via atomic git workflow.

10|2|Updated Dec 23, 2025
One-click install
npx skills add https://github.com/eveld/claude --skill share-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: share-docs
Source: https://github.com/eveld/claude/tree/main/skills/share-docs
Command: npx skills add https://github.com/eveld/claude --skill share-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Promotes personal documents to the shared namespace for team collaboration by managing numbering, updating frontmatter, and performing git operations atomically so team-wide records stay consistent.

Core Features & Use Cases

  • Atomic sharing workflow: copies a personal document from thoughts/{username}/NNNN-{slug} to thoughts/shared/${NEW_SHARED}-{slug} and updates frontmatter in both copies.
  • Frontmatter synchronization: ensures the personal copy is marked as shared and the shared copy references the original, with status fields reflecting publishing.
  • Collaboration readiness: enables publishing research notes, plans, and changelogs for team review and implementation.

Quick Start

Promote a personal document to the shared namespace by running the share operation on thoughts/{username}/NNNN-{slug}.

Frequently Asked Questions about share-docs

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

FAQPage Schema
How do I publish personal documents to a shared team namespace using git?

To publish personal documents to a shared team namespace, the Skill copies a document from thoughts/{username}/ to thoughts/shared/, updates frontmatter in both copies, and commits the changes atomically via git with conflict retries.

How does document frontmatter synchronization work when sharing files for collaboration?

Frontmatter synchronization marks the personal copy as shared and updates the shared copy to reference the original document, ensuring status fields accurately reflect the publication state for team collaboration.

Can I use this atomic git workflow to publish research notes and changelogs?

Yes, you can use this workflow to publish research notes, plans, and changelogs by validating the personal document, pulling the latest shared state, computing the next shared number, and committing atomically.

What is the best way to manage shared document numbering across a team?

The best way to manage shared document numbering is to compute the next shared number automatically by pulling the latest shared state before copying and updating the frontmatter of the promoted personal document.

What happens when git conflicts occur during the document publication process?

When git conflicts occur during document publication, the atomic workflow automatically retries the commit and push operations after pulling the latest shared state, ensuring team-wide records remain consistent.

Do I need a specific directory structure to promote documents to the shared namespace?

Yes, you need personal documents located at thoughts/{username}/NNNN-slug, as the Skill validates this specific path structure before copying and promoting them to the canonical shared namespace.