devflow-kit 3.8.0 → 3.10.0

package/src/assets/skills/review-methodology/references/patterns.md

@@ -11,7 +11,7 @@ Correct patterns for effective code reviews.
 3. **Review by Category** - Security, architecture, performance, etc.
 4. **Classify Issues** - CRITICAL, HIGH, MEDIUM, LOW
 5. **Write Report** - Structured format with file:line references
-6. **Post Comments** - Use GitHub API for PR comments
+6. **Hand Off** - Return the report to the caller, which owns what is published
 
 ---
 

package/src/assets/skills/review-methodology/references/report-template.md

@@ -104,8 +104,7 @@ These issues exist in files you reviewed but are unrelated to your changes:
 1. {Issue in code you touched}
 
 **Future work:**
-- Create issues for pre-existing problems
-- Track technical debt separately
+- List pre-existing problems; recommend an issue only for data loss, a false pass or a broken install
 ```
 
 ## PR Line Comment Format

package/src/assets/skills/testing/SKILL.md

@@ -130,10 +130,8 @@ Quarantine flaky tests immediately — a suite that sometimes passes is worse th
 ## Quality Gates [4][8][17]
 
 - [ ] Setup <10 lines; use fakes over mocks for complex dependencies [1]
-- [ ] No spying on private methods or internal state [8]
-- [ ] Tests verify behavior, not implementation details [4]
+- [ ] Each new assertion would fail, not error, with the change reverted: its RED run counts, else a bad input or a temporary uncommitted revert of your own edit, never a stash
 - [ ] All branches covered: happy path + errors + edge cases
 - [ ] Test names describe expected behavior [4]
 - [ ] Tests follow Arrange-Act-Assert structure [17]
-- [ ] No real delays — use fake timers [19]
-- [ ] No flaky patterns (race conditions, timing dependencies) [11][18]
+- [ ] No flaky patterns [11][18]