Documents software repositories into Claude-facing files from verified facts.
npx skills add https://github.com/MDGrey33/memnyx --skill scribe-mdgrey33
Please help me install this Agent Skill. Skill: scribe Source: https://github.com/MDGrey33/memnyx/tree/main/.claude/skills/scribe Command: npx skills add https://github.com/MDGrey33/memnyx --skill scribe-mdgrey33
Scribe turns a software repository into trustworthy, Claude-facing documentation so future work does not depend on tribal knowledge or stale prose. It helps prevent confidently wrong docs by forcing every important claim to be grounded in source.
Ask Scribe to document the project from verified facts and create the missing Claude-facing documentation files.
High-intent search queries and answers about installing and using this skill.
Generate verified documentation by scanning the repository source code to extract confirmed facts, which prevents confidently wrong or stale project knowledge from being committed. The process creates CLAUDE.md files and reference docs grounded in actual source code.
Keeping CLAUDE.md files from getting stale requires detecting the current doc-state of the repository and syncing updates only from verified source facts. This separates confirmed details from unverified claims to ensure documentation remains accurate.
Repository analysis separates confirmed facts from uncertain claims by enforcing source-grounded verification and tracking hazards for contradictory details. This prevents unverified information from being silently written into committed markdown knowledge bases.
You can use markdown documentation workflows to fill in missing repository READMEs by detecting partial or missing structure in the project. The workflow preserves existing doc-layers while generating new content strictly from verified repository facts.
Source-grounded verification for creating reference docs is needed when inheriting an unfamiliar codebase or updating operating conventions. It ensures every important claim is checked against the repository to avoid tribal knowledge dependencies.
Generating knowledge management files without hazards tracking risks silently writing unverified or contradictory details into committed documentation. Without separating confirmed facts, future work depends on misleading prose rather than grounded repository truths.
musher-devOrganize raw inputs into structured context briefs with verified facts and references.
rkz91Cascade documentation updates across PRDs, decks, and knowledge bases with diff-based proposals.
lucasfthIngest sources into an interlinked markdown wiki with YAML frontmatter and linting.
aaronlordAudit static context files and update project documentation using git and grep.
