@codyswann/lisa 1.28.0 → 1.29.1

package/all/copy-overwrite/.claude/skills/plan-implement/SKILL.md

@@ -22,8 +22,4 @@ If no argument provided, search for plan files in the `plans/` directory and pre
 
 ## Agent Team Composition
 
-Use the specialized agents listed in the `plan.md` rule (Implementation Team Guidance section). The **team lead** handles git operations (commits, pushes, PR management) -- teammates focus on their specialized work.
-
-## Execution
-
-Read the plan and begin implementation now.
+Use the specialized agents listed in $ARGUMENTS and the @.claude/rules/plan.md rule (Implementation Team Guidance section). The **team lead** handles git operations (commits, pushes, PR management) -- teammates focus on their specialized work.

package/nestjs/copy-overwrite/knip.json

@@ -24,6 +24,7 @@
     "@aws-sdk/client-cloudwatch",
     "@aws-sdk/client-dynamodb",
     "@aws-sdk/client-lambda",
+    "@aws-sdk/credential-provider-sso",
     "@aws-sdk/lib-dynamodb",
     "@aws-sdk/rds-signer",
     "@graphql-tools/utils",

package/package.json

@@ -88,7 +88,7 @@
     "@isaacs/brace-expansion": "^5.0.1"
   },
   "name": "@codyswann/lisa",
-  "version": "1.28.0",
+  "version": "1.29.1",
   "description": "Claude Code governance framework that applies guardrails, guidance, and automated enforcement to projects",
   "main": "dist/index.js",
   "bin": {

package/nestjs/copy-overwrite/.claude/commands/security/zap-scan.md

@@ -1,6 +0,0 @@
----
-description: "Run an OWASP ZAP baseline security scan locally using Docker"
-allowed-tools: ["Skill"]
----
-
-Use the /security-zap-scan skill to run an OWASP ZAP baseline security scan.

package/typescript/copy-overwrite/.claude/commands/security/zap-scan.md

@@ -1,12 +0,0 @@
-Run an OWASP ZAP baseline security scan locally using Docker.
-
-Steps:
-1. Check if Docker is installed and running: `docker info`
-2. Check if `scripts/zap-baseline.sh` exists in the project
-3. If it exists, run: `bash scripts/zap-baseline.sh`
-4. If it does not exist, inform the user that this project does not have a ZAP baseline scan configured
-5. After the scan completes, read `zap-report.html` (or `zap-report.md` for text) and summarize:
-   - Total number of alerts by risk level (High, Medium, Low, Informational)
-   - List each Medium+ finding with its rule ID, name, and recommended fix
-   - Categorize findings as "infrastructure-level" (fix at CDN/proxy) vs "application-level" (fix in code)
-6. If the scan failed, explain what failed and suggest concrete remediation steps