cosmosmith-governance-review
starsforks
How to install cosmosmith-governance-review?
devnomad-byte/cosmosmith/cosmosmith-governance-review
$npx -y skills add devnomad-byte/cosmosmith --skill cosmosmith-governance-reviewReview Cosmosmith artifacts, task ledgers, generated project rules, and skill outputs for coherence, layer separation, missing evidence, and rule drift. Use before marking Cosmosmith planning or implementation tasks done, after spec generation, or when project rules and generated
SKILL.md
| 1 | # Cosmosmith Governance Review |
| 2 | |
| 3 | ## Purpose |
| 4 | |
| 5 | Protect the project from drift: rules, skills, templates, and tasks must stay coherent. |
| 6 | |
| 7 | ## Workflow |
| 8 | |
| 9 | 1. Read project `AGENTS.md`, `task.md`, and relevant Cosmosmith artifacts. |
| 10 | 2. Check layer separation: |
| 11 | - Project instructions belong in `AGENTS.md`. |
| 12 | - Claude-specific adaptation belongs in `CLAUDE.md`. |
| 13 | - Reusable workflows belong in Cosmosmith skills. |
| 14 | - Long standards belong in references or docs. |
| 15 | - Deterministic checks belong in scripts. |
| 16 | 3. Check every reviewed task for owner role, status, context, expected output, acceptance checks, harness, loop, evidence, and dependencies. |
| 17 | 4. Check that philosophy affects an operational artifact, harness, or loop. |
| 18 | 5. Report findings by severity and update `task.md` with follow-up tasks when needed. |
| 19 | |
| 20 | ## Findings Format |
| 21 | |
| 22 | Use this structure: |
| 23 | |
| 24 | - Severity: |
| 25 | - Location: |
| 26 | - Problem: |
| 27 | - Why it matters: |
| 28 | - Required fix: |
| 29 | |
| 30 | ## Completion |
| 31 | |
| 32 | Stop when each reviewed artifact is either accepted with evidence or has a concrete follow-up task in `task.md`. |
People who liked this also viewed
6 picksType
- requesting-code-reviewUse when completing tasks, implementing major features, or before merging to verify work meets requirementsSkillsJul 2026
- code-reviewSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- receiving-code-reviewUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performativeSkillsJul 2026
- baoyu-format-markdownFormats plain text or markdown files with frontmatter, titles, summaries, headings, bold, lists, and code blocks. Use when user asks to "format markdown", "beautify article", "add formatting", or imprSkillsJul 2026
- code-review-excellenceMaster effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing reSkillsJul 2026
- code-review-and-qualityConducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensiSkillsJul 2026
