devlyn-cli 0.1.0 → 0.1.2

package/config/commands/devlyn.review.md

@@ -5,8 +5,9 @@ Perform a comprehensive post-implementation review. After receiving tool results
 2. Read all changed files in parallel (use parallel tool calls)
 3. Check each file against the review checklist below
 4. Fix issues directly—do not just suggest fixes
-5. Run test suite to verify changes don't break existing functionality
-6. If tests fail → use devlyn.resolve workflow to fix, then re-run tests
+5. Run linter (`npm run lint` or equivalent) and fix all reported lint issues
+6. Run test suite to verify changes don't break existing functionality
+7. If lint or tests fail → use devlyn.resolve workflow to fix, then re-run
 7. Generate summary report with file:line references
 8. Block approval if any CRITICAL or HIGH issues remain unfixed OR tests fail
 </procedure>
@@ -79,7 +80,10 @@ Be persistent. Complete the full review before stopping.
 
 **Approval**: [BLOCKED / APPROVED]
 
-- BLOCKED if any CRITICAL or HIGH issues remain unfixed OR tests fail
+- BLOCKED if any CRITICAL or HIGH issues remain unfixed OR lint/tests fail
+
+**Lint**: [PASS / FAIL]
+- [lint summary or issue details]
 
 **Tests**: [PASS / FAIL]
 - [test summary or failure details]

package/config/commands/devlyn.team-review.md

@@ -155,14 +155,16 @@ You are the **Test Analyst** on an Agent Team performing a code review.
 2. Find existing test files for the changed code
 3. Assess test coverage for the changes
 4. Run the full test suite and report results
-5. Identify missing test scenarios and edge cases
+5. Run the project linter (`npm run lint` or equivalent) and report any lint errors/warnings on changed files
+6. Identify missing test scenarios and edge cases
 
 **Your deliverable**: Send a message to the team lead with:
 1. Test suite results: PASS or FAIL (with failure details)
-2. Coverage gaps: what changed code lacks tests
-3. Missing edge cases that should be tested
-4. Test quality assessment
-5. Recommended tests to add
+2. Lint results: PASS or FAIL (with issue details on changed files)
+3. Coverage gaps: what changed code lacks tests
+4. Missing edge cases that should be tested
+5. Test quality assessment
+6. Recommended tests to add
 
 Read the team config at ~/.claude/teams/{team-name}/config.json to discover teammates. Share test results with other reviewers via SendMessage.
 </test_analyst_prompt>
@@ -278,14 +280,17 @@ Present the final review in this format:
 ### Review Complete
 
 **Approval**: [BLOCKED / APPROVED]
-- BLOCKED if any CRITICAL or HIGH issues remain unfixed OR tests fail
+- BLOCKED if any CRITICAL or HIGH issues remain unfixed OR lint/tests fail
 
 **Team Composition**: [N] reviewers
 - **Security Reviewer**: [N issues found / Clean]
 - **Quality Reviewer**: [N issues found / Clean]
-- **Test Analyst**: [PASS/FAIL, N coverage gaps]
+- **Test Analyst**: [Tests PASS/FAIL, Lint PASS/FAIL, N coverage gaps]
 - **[Conditional reviewers]**: [findings summary]
 
+**Lint**: [PASS / FAIL]
+- [lint summary or issue details]
+
 **Tests**: [PASS / FAIL]
 - [test summary or failure details]
 

package/config/skills/code-review-standards/SKILL.md

@@ -49,11 +49,13 @@ Severity framework and quality bar for reviewing code changes. Apply this framew
 **BLOCKED** if any of:
 - CRITICAL issues remain unfixed
 - HIGH issues remain unfixed
+- Lint fails
 - Tests fail
 
 **APPROVED** when:
 - All CRITICAL and HIGH issues are fixed
 - MEDIUM issues are fixed or have concrete justification for deferral
+- Lint passes
 - Test suite passes
 
 ## Review Process
@@ -62,8 +64,9 @@ Severity framework and quality bar for reviewing code changes. Apply this framew
 2. Check each file against the severity framework
 3. For each issue: state severity, file:line, what it is, why it matters
 4. Fix issues directly — don't just list them
-5. Run the test suite after all fixes
-6. If tests fail → use `/devlyn.resolve` or `/devlyn.team-resolve` to fix
+5. Run linter (`npm run lint` or equivalent) and fix all reported issues
+6. Run the test suite after all fixes
+7. If lint or tests fail → use `/devlyn.resolve` or `/devlyn.team-resolve` to fix
 
 ## Routing
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "devlyn-cli",
-  "version": "0.1.0",
+  "version": "0.1.2",
   "description": "Claude Code configuration toolkit for teams",
   "bin": {
     "devlyn": "bin/devlyn.js"