Review and audit technical proposal documents for consistency and accuracy.
npx skills add https://github.com/dev-eloper1/clarity-loop --skill cl-reviewer
Please help me install this Agent Skill. Skill: cl-reviewer Source: https://github.com/dev-eloper1/clarity-loop/tree/main/skills/cl-reviewer Command: npx skills add https://github.com/dev-eloper1/clarity-loop --skill cl-reviewer
This Skill acts as a rigorous co-reviewer for technical documentation, ensuring proposals are coherent, consistent with system architecture, and technically sound before they are merged, preventing drift and maintaining a high standard of documentation health.
Use the cl-reviewer skill to perform an initial review of the proposal document P-001-new-feature.md.
High-intent search queries and answers about installing and using this skill.
To review technical documentation for consistency, use an automated pipeline that audits proposal documents for clarity, technical flaws, and architectural alignment. It performs structured initial and re-reviews to catch inconsistencies and gaps before you merge changes.
A documentation audit is a comprehensive review of your entire system documentation set to detect drift and ensure overall health. You need one when maintaining system integrity across multiple proposal documents and verifying architectural alignment.
To synchronize system documentation with your codebase, execute a targeted correction and code-doc sync mode within a structured review pipeline. This identifies drift between documentation and source code, verifying integrity and maintaining alignment.
Yes, you can merge approved technical proposals into system documentation using a dedicated merge mode. The pipeline facilitates the merge and then runs a verification step to ensure the integrity of the merged documentation set.
The best way to catch technical flaws and gaps in a feature proposal is conducting an initial review using a structured documentation pipeline. This identifies inconsistencies, technical flaws, and missing details while ensuring alignment with existing architecture.
Yes, the documentation review pipeline supports design reviews and targeted corrections. You can perform a design review to evaluate architectural soundness, then apply corrections based on specific findings to maintain documentation health.
sameer-thakkarExecute tasks and create handoff documents for complex workflows.
ReinaMacCredyMerge origin/main into a local Git branch with guided conflict resolution.
Prorise-coolGenerate and update READMEs, API specifications, and architecture guides in Markdown.
diberryEnforce Microsoft Learn writing style conventions in technical documentation.
