@codyswann/lisa 1.58.3 → 1.59.0

package/package.json

@@ -72,7 +72,7 @@
     "axios": ">=1.13.5"
   },
   "name": "@codyswann/lisa",
-  "version": "1.58.3",
+  "version": "1.59.0",
   "description": "Claude Code governance framework that applies guardrails, guidance, and automated enforcement to projects",
   "main": "dist/index.js",
   "exports": {

package/plugins/lisa/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa",
-  "version": "1.58.3",
+  "version": "1.59.0",
   "description": "Universal governance — agents, skills, commands, hooks, and rules for all projects",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-cdk/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-cdk",
-  "version": "1.58.3",
+  "version": "1.59.0",
   "description": "AWS CDK-specific plugin",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-expo/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-expo",
-  "version": "1.58.3",
+  "version": "1.59.0",
   "description": "Expo/React Native-specific skills, agents, rules, and MCP servers",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-nestjs/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-nestjs",
-  "version": "1.58.3",
+  "version": "1.59.0",
   "description": "NestJS-specific skills (GraphQL, TypeORM)",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-rails/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-rails",
-  "version": "1.58.3",
+  "version": "1.59.0",
   "description": "Ruby on Rails-specific skills, rules, and conventions",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-typescript/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-typescript",
-  "version": "1.58.3",
+  "version": "1.59.0",
   "description": "TypeScript-specific hooks — Prettier formatting, ESLint linting, and ast-grep scanning on edit",
   "author": {
     "name": "Cody Swann"

package/rails/create-only/.github/workflows/claude-nightly-jira-triage.yml

@@ -5,7 +5,7 @@ name: Claude Nightly Jira Triage
 
 on:
   schedule:
-    - cron: '0 6 * * 1-5'
+    - cron: '0 */2 * * *'
   workflow_dispatch:
     inputs:
       ticket_key:

package/typescript/copy-overwrite/.github/GITHUB_ACTIONS.md

@@ -233,6 +233,47 @@ Incrementally lowers ESLint code complexity thresholds toward target minimums:
 
 Does not modify the `maxLines` threshold. Skips if all metrics are at/below targets. Prevents duplicate PRs.
 
+### Claude Nightly Jira Triage (`claude-nightly-jira-triage.yml`)
+
+**Triggers**: Cron every 2 hours (all days), manual dispatch
+
+**Auto-enables**: When Claude and Jira credentials are configured (`CLAUDE_CODE_OAUTH_TOKEN`, `JIRA_API_TOKEN` secrets and `JIRA_BASE_URL`, `JIRA_USER_EMAIL`, `JIRA_PROJECT_KEY` repository variables). No feature flag needed.
+
+Automatically triages untriaged Jira tickets by examining them and posting actionable comments. Supports multi-repo setups where multiple repositories share a single Jira project:
+
+1. Fetches untriaged tickets via JQL using repo-scoped labels (`claude-triaged-<repo-name>`, e.g., `claude-triaged-frontend-v2`). Each repo filters by its own label so every repo triages independently
+2. **Relevance Gating**: Searches the local codebase for code related to the ticket. If no relevant code is found, adds the repo-scoped label and skips -- no noise posted to the ticket
+3. **Cross-repo Awareness**: Reads existing comments on the ticket before posting. If another repo already posted triage findings, only adds supplementary findings from this repo's perspective. All comments are prefixed with the repo name (e.g., `*[frontend-v2] Ambiguity detected*`)
+4. **Ambiguity Detection**: Flags vague language, untestable criteria, undefined terms, and missing scope. Posts a comment per ambiguity with a suggested clarifying question
+5. **Edge Case Analysis**: Searches the codebase for related files, checks git history, and identifies boundary conditions, error handling gaps, and integration risks. Posts a consolidated comment referencing only files in this repo
+6. **Verification Methodology**: For each acceptance criterion, specifies a concrete verification method scoped to what this repo can test (e.g., frontend suggests Playwright tests, backend suggests API curl commands). Posts a structured table comment
+7. Labels the ticket with the repo-scoped label (`claude-triaged-<repo-name>`) so it is not reprocessed by this repo
+
+**Manual dispatch inputs**:
+- `ticket_key`: Triage a specific ticket by key (e.g., `PROJ-123`)
+- `ticket_count`: Number of tickets to process in batch mode (default: 5)
+
+This workflow is read-only — it does not modify code or create PRs. It only reads the codebase and posts Jira comments.
+
+**How to activate**:
+
+1. Add the secrets in **Settings** > **Secrets and variables** > **Actions** > **Secrets**:
+
+   | Secret | Description | How to get |
+   |--------|-------------|------------|
+   | `CLAUDE_CODE_OAUTH_TOKEN` | OAuth token for Claude Code | See `CLAUDE_CODE_OAUTH_TOKEN` in the Core Secrets section below |
+   | `JIRA_API_TOKEN` | API token from Atlassian | [Create API token](https://id.atlassian.com/manage-profile/security/api-tokens) |
+
+2. Add repository variables in **Settings** > **Secrets and variables** > **Actions** > **Variables**:
+
+   | Variable | Description | Example |
+   |----------|-------------|---------|
+   | `JIRA_BASE_URL` | Jira instance base URL | `https://company.atlassian.net` |
+   | `JIRA_USER_EMAIL` | Email associated with the API token | `user@company.com` |
+   | `JIRA_PROJECT_KEY` | Jira project key for ticket queries | `PROJ` |
+
+3. The workflow auto-enables once all three variables and both secrets are set. No feature flag needed.
+
 ### Auto-update PR Branches (`auto-update-pr-branches.yml`)
 
 **Triggers**: Push to `main`, `staging`, or `dev`
@@ -457,8 +498,6 @@ gpg --export-secret-keys YOUR_KEY_ID | base64 > signing-key.txt
 | Secret | Description |
 |--------|-------------|
 | `JIRA_API_TOKEN` | API token from Atlassian |
-| `JIRA_BASE_URL` | Your Jira instance URL (e.g., `https://company.atlassian.net`) |
-| `JIRA_USER_EMAIL` | Email associated with the API token |
 | `JIRA_AUTOMATION_WEBHOOK` | Webhook URL for Jira automation |
 
 **How to get JIRA_API_TOKEN**:
@@ -474,6 +513,9 @@ Variables are non-sensitive configuration values. Set them in **Settings** > **S
 |----------|-------------|---------|
 | `ENABLE_CLAUDE_NIGHTLY` | Enable nightly Claude workflows | `true` |
 | `ENABLE_CLAUDE_CODE_REVIEW_RESPONSE` | Enable Claude response to CodeRabbit reviews | `true` |
+| `JIRA_BASE_URL` | Jira instance base URL (enables Jira triage workflow) | `https://company.atlassian.net` |
+| `JIRA_USER_EMAIL` | Email associated with the Jira API token | `user@company.com` |
+| `JIRA_PROJECT_KEY` | Jira project key for ticket queries | `PROJ` |
 | `SENTRY_ORG` | Sentry organization slug | `my-company` |
 | `SENTRY_PROJECT` | Sentry project slug | `frontend-app` |
 

package/typescript/create-only/.github/workflows/claude-nightly-jira-triage.yml

@@ -5,7 +5,7 @@ name: Claude Nightly Jira Triage
 
 on:
   schedule:
-    - cron: '0 6 * * 1-5'
+    - cron: '0 */2 * * *'
   workflow_dispatch:
     inputs:
       ticket_key: