docmancer-onboarding

Solid

Create or adopt a local curated Markdown tree without forcing a taxonomy or enabling capture.

AI & Automation 112 stars 12 forks Updated today MIT

Install

View on GitHub

Quality Score: 84/100

Stars 20%
68
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
39
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Onboard a project to Docmancer 1. Run `docmancer init` from the project root. Existing valid Markdown files are adopted rather than rewritten. 2. Run `docmancer status` to inspect the tree, inbox, local index, integrations, and optional Cloud state. 3. Preview existing agent evidence with `docmancer harvest <path>`. Add `--apply` only when the user wants a bounded copy placed in the uncurated inbox. 4. Use `docmancer curate` to preview one complete file diff. Apply only the complete accepted operation. 5. Run `docmancer reindex` after external edits when automatic watching is unavailable. Onboarding does not enable capture hooks, connect Cloud, publish Team memory, or create a universal folder taxonomy. Canonical memory remains readable Markdown under `.docmancer/tree`.

Details

Author
docmancer
Repository
docmancer/docmancer
Created
3 months ago
Last Updated
today
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category