@codyswann/lisa 1.78.5 → 1.78.7
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/package.json +1 -1
- package/plugins/lisa/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa/skills/nightly-lower-code-complexity/SKILL.md +4 -3
- package/plugins/lisa-cdk/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-expo/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-nestjs/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-rails/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-typescript/.claude-plugin/plugin.json +1 -1
- package/plugins/src/base/skills/nightly-lower-code-complexity/SKILL.md +4 -3
package/package.json
CHANGED
|
@@ -76,7 +76,7 @@
|
|
|
76
76
|
"lodash": ">=4.18.1"
|
|
77
77
|
},
|
|
78
78
|
"name": "@codyswann/lisa",
|
|
79
|
-
"version": "1.78.
|
|
79
|
+
"version": "1.78.7",
|
|
80
80
|
"description": "Claude Code governance framework that applies guardrails, guidance, and automated enforcement to projects",
|
|
81
81
|
"main": "dist/index.js",
|
|
82
82
|
"exports": {
|
|
@@ -23,6 +23,7 @@ The caller provides pre-computed context:
|
|
|
23
23
|
7. For max-lines-per-function violations: split large functions, extract helper functions, separate concerns
|
|
24
24
|
8. After each file edit, run the project's formatter (e.g., `bun run format` or `npx prettier --write <file>`) to ensure line counts reflect the final formatted state before moving on
|
|
25
25
|
9. Re-run the lint script with the provided package manager to verify all violations are resolved (both the target metric AND max-lines)
|
|
26
|
-
10. Run the
|
|
27
|
-
11.
|
|
28
|
-
12.
|
|
26
|
+
10. Run the TypeScript compiler to catch type errors early: `npx tsc --noEmit 2>&1 | head -30`. If there are type errors, fix them now — do NOT wait until the commit step. Pre-commit hooks run type checking, and discovering errors at commit time wastes turns.
|
|
27
|
+
11. Run the project's test script with the provided package manager (e.g., `npm run test`, `yarn test`, or `bun run test`) to verify no tests are broken by the refactoring
|
|
28
|
+
12. Commit all changes (refactored code + updated eslint.thresholds.json) with conventional commit messages
|
|
29
|
+
13. Create a PR with `gh pr create` with a title like "refactor: reduce code complexity: [metrics being reduced]" summarizing the changes
|
|
@@ -23,6 +23,7 @@ The caller provides pre-computed context:
|
|
|
23
23
|
7. For max-lines-per-function violations: split large functions, extract helper functions, separate concerns
|
|
24
24
|
8. After each file edit, run the project's formatter (e.g., `bun run format` or `npx prettier --write <file>`) to ensure line counts reflect the final formatted state before moving on
|
|
25
25
|
9. Re-run the lint script with the provided package manager to verify all violations are resolved (both the target metric AND max-lines)
|
|
26
|
-
10. Run the
|
|
27
|
-
11.
|
|
28
|
-
12.
|
|
26
|
+
10. Run the TypeScript compiler to catch type errors early: `npx tsc --noEmit 2>&1 | head -30`. If there are type errors, fix them now — do NOT wait until the commit step. Pre-commit hooks run type checking, and discovering errors at commit time wastes turns.
|
|
27
|
+
11. Run the project's test script with the provided package manager (e.g., `npm run test`, `yarn test`, or `bun run test`) to verify no tests are broken by the refactoring
|
|
28
|
+
12. Commit all changes (refactored code + updated eslint.thresholds.json) with conventional commit messages
|
|
29
|
+
13. Create a PR with `gh pr create` with a title like "refactor: reduce code complexity: [metrics being reduced]" summarizing the changes
|