volodymyrkoval
- 8 skills
- 0 followers
- 9 hours ago last updated
- ▌
- ▌ Code Comments · volodymyrkovalDecides when and how to write code comments — JSDoc/docstrings on exported symbols, module/file-level headers, and inline comments. Apply when writing or modifying functions/classes/modules; when about to add a comment; when touching code with redundant restatements, commented-out code, or stale TODOs nearby (opportunistic cleanup, change-radius only). Language-agnostic principles with concrete syntax for JS/TS, Python, and Go — extends to Rust, Java, C#, Ruby. Reviewer applies it to flag comment-quality violations during code review. Does NOT cover README/feature-doc/CLAUDE.md updates (use docs-writer), commit messages, or changelog entries.
- ▌
- ▌ Todo Tracking · volodymyrkovalUse when a `docs/plans/` file exists — the plan's checkboxes are the authoritative todo list. Governs how to pick the next item, mark it complete, and when TaskCreate is vs. isn't allowed. Use whenever dispatching dev agents against a plan, checking what's next, or archiving a finished plan.
- ▌ UI Test Rubric · volodymyrkovalApply when writing a UI integration test at a component seam, when reasoning about test scope at component boundaries, when deciding what to mock in a UI test, or when an integration test is hard to write — re-check scope. Reusable by both ui-integration-tester (writer) and future ui-integration-auditor (auditor).
- ▌
- ▌ Mutation Testing · volodymyrkovalMeasure real test quality by mutating source code and verifying that tests catch the changes. Use after significant Green phases, before /review, and when coverage looks complete but confidence is low.
- ▌