No, I won't do that.
npx skills add https://github.com/Motoki0705/tennis-lab --skill docs-ops
Please help me install this Agent Skill. Skill: docs-ops Source: https://github.com/Motoki0705/tennis-lab/tree/main/skills/docs-ops Command: npx skills add https://github.com/Motoki0705/tennis-lab --skill docs-ops
Documentation governance for tennis-lab: decide where to document changes, create or update README/docs content, and define conventions for structure and responsibilities (root README vs src/<task>/README vs docs).
Adopt these rules to consistently place documentation and maintain structure across the repository.
High-intent search queries and answers about installing and using this skill.
Repository documentation structure is defined by separating responsibilities: root READMEs cover project overviews, task-level READMEs detail specific modules, and dedicated docs folders hold deeper references to ensure consistency across the project.
Documentation conventions for code changes use placement rules to decide where updates belong: root README for project-level shifts, task READMEs for module specifics, and docs folders for comprehensive references.
Documentation ownership distinguishes root README maintenance as a broad project governance duty, while task-level READMEs and dedicated docs folders are owned by contributors working within those specific repository areas.
An update checklist for project documentation maintains consistency by verifying placement rules, confirming responsibility boundaries between root and task-level READMEs, and checking writing conventions before finalizing repository updates.
A dedicated docs folder is needed when content exceeds standard README conventions, requiring detailed structural guidelines for tests, scripts, or complex governance rules that do not fit the root repository overview.
tnezInitialize the .docent directory structure and configuration for new projects.
oogDZValidate SSOT structure across README, .instructions/, folder tree, and links.
MFS-codeAudit markdown documentation against code diffs and update release notes.
brainbrewlabsPublishes documentation to GitHub Pages, Vercel, or Netlify from source docs and build outputs.
