Generate and verify up to nine documentation files from the codebase.
npx skills add https://github.com/thecomputer07/qsd --skill qsd-docs-update
Please help me install this Agent Skill. Skill: qsd-docs-update Source: https://github.com/thecomputer07/qsd/tree/main/skills/qsd-docs-update Command: npx skills add https://github.com/thecomputer07/qsd --skill qsd-docs-update
This skill streamlines the creation and maintenance of project documentation by deriving docs directly from the codebase, reducing manual drafting and drift.
Trigger a doc generation and verification pass for the current project.
High-intent search queries and answers about installing and using this skill.
To automate documentation generation from a codebase, trigger the skill without flags to perform a full generation pass. It deploys subagents that explore the repository structure and code annotations to author up to nine documentation files automatically.
You can verify existing docs against the current codebase by running the process with the --verify-only flag. This skips generation and reports verification results, checking that documentation accuracy and consistency are maintained across releases.
To force regenerate existing documentation files, pass the --force flag when triggering the skill. This overrides current files and rewrites the documentation by re-exploring the codebase directly through the subagent workflow.
Yes, the documentation automation requires an execution workflow file located at @$HOME/.claude/qsd/workflows/docs-update.md. This workflow file orchestrates the subagents that explore the codebase and activate flags using the ARGUMENTS context.
The best way to maintain living documentation for onboarding is to derive docs directly from the codebase to reduce drift. By automating generation and running verification passes, documentation coverage stays consistent with the actual code across releases.
A limitation of automating docs with subagents is that generation requires the specified execution workflow file to exist at the exact home directory path. Additionally, the system is designed to author a maximum of nine documentation files per project.
thecomputer07Update local or global qsd npm installations and display the changelog.
fagemxGenerate player-facing patch notes and internal changelogs from git tags and commits.
breakingcircuits1337Apply Test-Driven Development cycles to create process documentation.
channgGenerate static documentation websites from markdown files with sidebar navigation.
