@codyswann/lisa 1.39.2 → 1.40.0

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.
@@ -0,0 +1,7 @@
1
+ ---
2
+ description: "Create conventional commits for current changes and submits the current branch as a PR for code review. Then follows the pr to make sure all checks pass and comments are resolved."
3
+ allowed-tools: ["Skill"]
4
+ argument-hint: "[commit-message-hint]"
5
+ ---
6
+
7
+ Use the /git-commit-submit-pr-and-verify skill on $ARGUMENTS
@@ -0,0 +1,7 @@
1
+ ---
2
+ description: "Create conventional commits for current changes and submits the current branch as a PR for code review. Then follows the pr to make sure all checks pass and comments are resolved. And then makes sure the resultant deploy is successful."
3
+ allowed-tools: ["Skill"]
4
+ argument-hint: "[commit-message-hint]"
5
+ ---
6
+
7
+ Use the /git-commit-submit-pr-deploy-and-verify skill on $ARGUMENTS
@@ -0,0 +1,7 @@
1
+ ---
2
+ name: git-commit-submit-pr-and-verify
3
+ description: This skill should be used when creating conventional commits for current changes and then submitting the current branch as a pull request for code review. And then verifying the pull request was approved.
4
+ allowed-tools: ["Bash"]
5
+ ---
6
+
7
+ Run the /git-commit-and-submit-pr with $ARGUMENTS and set the PR to auto-merge. Fix any pre-commit or pre-push issues and then follow the pr, make sure all checks pass and comments are resolved or addressed. Fix anything that is broken and repeat.
@@ -0,0 +1,7 @@
1
+ ---
2
+ name: git-commit-submit-pr-deploy-and-verify
3
+ description: This skill should be used when creating conventional commits for current changes and then submitting the current branch as a pull request for code review. And then verifying the pull request was approved. As well as making sure the resutling deploy succeeds.
4
+ allowed-tools: ["Bash"]
5
+ ---
6
+
7
+ Run the /git-commit-submit-pr-and-verify with $ARGUMENTS. Once the merge is complete, follow the resulting deploy and fix anything that breaks with the deploy and then follow this process again with a new PR until the deploy succeeds.
package/package.json CHANGED
@@ -89,7 +89,7 @@
89
89
  "@isaacs/brace-expansion": "^5.0.1"
90
90
  },
91
91
  "name": "@codyswann/lisa",
92
- "version": "1.39.2",
92
+ "version": "1.40.0",
93
93
  "description": "Claude Code governance framework that applies guardrails, guidance, and automated enforcement to projects",
94
94
  "main": "dist/index.js",
95
95
  "bin": {