@tonycasey/lisa 2.2.0 → 2.11.5

package/dist/project/.lisa/skills/github/SKILL.md

@@ -0,0 +1,415 @@
+---
+name: github
+description: "GitHub Issues and Projects v2 management via gh CLI; triggers on 'github', 'create issue', 'list issues', 'github project', 'project board', 'sync tasks'."
+---
+
+## Purpose
+
+Model-neutral helper to interact with GitHub Issues and Projects v2 using the gh CLI. Supports creating, listing, viewing, closing, and managing issues, managing GitHub Projects v2 boards, and bidirectional sync between Lisa tasks and GitHub Issues.
+
+## Triggers
+
+Use when the user says:
+- "create a github issue", "create issue", "new issue"
+- "list github issues", "show issues", "open issues"
+- "close issue", "reopen issue", "assign issue"
+- "github project", "project board", "kanban"
+- "add to project", "update project field", "move to column"
+- "sync tasks with github", "import github issues", "export tasks to github"
+
+## Configuration
+
+Uses existing `gh` CLI authentication. Verify with:
+```bash
+gh auth status
+```
+
+Alternatively, set `GITHUB_TOKEN` environment variable for CI/headless environments.
+
+## How to use
+
+### Issues
+
+#### List Issues
+```bash
+# List open issues
+lisa github issues list --repo owner/repo
+
+# List with filters
+lisa github issues list --repo owner/repo --state open --labels bug,urgent --assignee @me --limit 20
+
+# List all issues (including closed)
+lisa github issues list --repo owner/repo --state all
+```
+
+#### Create Issue
+```bash
+# Basic issue
+lisa github issues create --repo owner/repo --title "Bug: Login fails"
+
+# With body and labels
+lisa github issues create --repo owner/repo --title "Feature: Dark mode" --body "Add dark mode support" --labels enhancement,ui
+
+# With assignee
+lisa github issues create --repo owner/repo --title "Task" --assignee username
+```
+
+#### View Issue
+```bash
+lisa github issues view --repo owner/repo 123
+```
+
+#### Close/Reopen Issue
+```bash
+# Close as completed
+lisa github issues close --repo owner/repo 123
+
+# Close as not planned
+lisa github issues close --repo owner/repo 123 --reason not_planned
+
+# Reopen
+lisa github issues reopen --repo owner/repo 123
+```
+
+#### Assign Issue
+```bash
+lisa github issues assign --repo owner/repo 123 --to username
+lisa github issues assign --repo owner/repo 123 --to user1,user2
+```
+
+#### Label Issue
+```bash
+# Add labels
+lisa github issues label --repo owner/repo 123 --add bug,priority-high
+
+# Remove labels
+lisa github issues label --repo owner/repo 123 --remove wontfix
+
+# Add and remove
+lisa github issues label --repo owner/repo 123 --add in-progress --remove backlog
+```
+
+### Projects v2
+
+#### List Projects
+```bash
+lisa github projects list --repo owner/repo
+lisa github projects list --repo owner/repo --limit 10
+```
+
+#### View Project
+```bash
+lisa github projects view --repo owner/repo 1
+```
+
+#### List Project Items
+```bash
+lisa github projects items --repo owner/repo 1
+lisa github projects items --repo owner/repo 1 --limit 50
+```
+
+#### List Project Fields
+```bash
+# Get available fields and their options (useful for set-field)
+lisa github projects fields --repo owner/repo 1
+```
+
+#### Add Issue to Project
+```bash
+# Add issue #123 to project #1
+lisa github projects add --repo owner/repo 1 123
+```
+
+#### Update Project Field
+```bash
+# Set status field (e.g., move to "In Progress" column)
+lisa github projects set-field --repo owner/repo 1 ITEM_ID --field Status --value "In Progress"
+
+# Set priority
+lisa github projects set-field --repo owner/repo 1 ITEM_ID --field Priority --value "High"
+```
+
+**Note:** Use `projects fields` to get valid field names and options, and `projects items` to get item IDs.
+
+### Sync (Bidirectional Task Sync)
+
+Sync Lisa tasks with GitHub Issues. Supports import, export, or bidirectional sync.
+
+#### Import GitHub Issues as Lisa Tasks
+```bash
+# Import all open issues from repo
+lisa github sync --repo owner/repo --import
+
+# Import issues with specific labels
+lisa github sync --repo owner/repo --import --labels task,feature
+
+# Preview import without making changes
+lisa github sync --repo owner/repo --import --dry-run
+
+# Specify group ID for Lisa tasks (default: owner-repo)
+lisa github sync --repo owner/repo --import --group my-project
+```
+
+#### Export Lisa Tasks to GitHub Issues
+```bash
+# Export unlinked tasks as new GitHub issues
+lisa github sync --repo owner/repo --export
+
+# Preview export
+lisa github sync --repo owner/repo --export --dry-run
+```
+
+#### Bidirectional Sync
+```bash
+# Full two-way sync (import + export + status updates)
+lisa github sync --repo owner/repo
+
+# Preview all changes
+lisa github sync --repo owner/repo --dry-run
+```
+
+#### Status Mapping
+
+| Lisa Status | GitHub State | GitHub Labels |
+|-------------|--------------|---------------|
+| `ready`/`todo` | open | (none) |
+| `in-progress` | open | `in-progress` |
+| `blocked` | open | `blocked` |
+| `done` | closed | (none) |
+
+**Conflict Resolution:** When both Lisa and GitHub have changes, last-write-wins based on timestamps.
+
+## I/O Contract (examples)
+
+### Create Issue
+```json
+{
+  "status": "ok",
+  "action": "create",
+  "issue": {
+    "number": 123,
+    "url": "https://github.com/owner/repo/issues/123",
+    "title": "Bug: Login fails"
+  }
+}
+```
+
+### List Issues
+```json
+{
+  "status": "ok",
+  "action": "list",
+  "issues": [
+    {
+      "number": 123,
+      "title": "Bug: Login fails",
+      "state": "open",
+      "labels": ["bug"],
+      "assignees": ["username"],
+      "url": "https://github.com/owner/repo/issues/123",
+      "createdAt": "2026-01-22T10:00:00Z",
+      "updatedAt": "2026-01-22T10:00:00Z"
+    }
+  ],
+  "total": 1
+}
+```
+
+### View Issue
+```json
+{
+  "status": "ok",
+  "action": "view",
+  "issue": {
+    "number": 123,
+    "title": "Bug: Login fails",
+    "body": "Steps to reproduce...",
+    "state": "open",
+    "labels": ["bug"],
+    "assignees": ["username"],
+    "url": "https://github.com/owner/repo/issues/123",
+    "createdAt": "2026-01-22T10:00:00Z",
+    "updatedAt": "2026-01-22T10:00:00Z",
+    "author": "reporter",
+    "milestone": "v1.0"
+  }
+}
+```
+
+### List Projects
+```json
+{
+  "status": "ok",
+  "action": "list",
+  "projects": [
+    {
+      "id": "PVT_kwDOABC123",
+      "number": 1,
+      "title": "Sprint Board",
+      "url": "https://github.com/orgs/owner/projects/1",
+      "closed": false,
+      "shortDescription": "Current sprint tasks"
+    }
+  ],
+  "total": 1
+}
+```
+
+### Project Items
+```json
+{
+  "status": "ok",
+  "action": "items",
+  "items": [
+    {
+      "id": "PVTI_abc123",
+      "type": "ISSUE",
+      "content": {
+        "number": 123,
+        "title": "Bug: Login fails",
+        "url": "https://github.com/owner/repo/issues/123",
+        "state": "OPEN"
+      },
+      "fieldValues": {
+        "Status": "In Progress",
+        "Priority": "High"
+      }
+    }
+  ],
+  "total": 1
+}
+```
+
+### Project Fields
+```json
+{
+  "status": "ok",
+  "action": "fields",
+  "fields": [
+    {
+      "id": "PVTF_abc123",
+      "name": "Status",
+      "dataType": "SINGLE_SELECT",
+      "options": [
+        { "id": "opt_1", "name": "Todo" },
+        { "id": "opt_2", "name": "In Progress" },
+        { "id": "opt_3", "name": "Done" }
+      ]
+    },
+    {
+      "id": "PVTF_def456",
+      "name": "Priority",
+      "dataType": "SINGLE_SELECT",
+      "options": [
+        { "id": "opt_a", "name": "Low" },
+        { "id": "opt_b", "name": "Medium" },
+        { "id": "opt_c", "name": "High" }
+      ]
+    }
+  ]
+}
+```
+
+### Sync Result
+```json
+{
+  "status": "ok",
+  "action": "sync",
+  "direction": "bidirectional",
+  "dryRun": false,
+  "summary": {
+    "imported": 3,
+    "exported": 2,
+    "updated": 1,
+    "skipped": 5,
+    "conflicts": 1
+  },
+  "imported": [
+    { "title": "Bug: Login fails", "issueNumber": 123, "issueUrl": "https://github.com/owner/repo/issues/123" }
+  ],
+  "exported": [
+    { "title": "Refactor auth module", "taskUuid": "abc123", "issueNumber": 456, "issueUrl": "https://github.com/owner/repo/issues/456" }
+  ],
+  "updated": [
+    { "title": "Update docs", "taskUuid": "def789", "issueNumber": 101, "issueUrl": "https://github.com/owner/repo/issues/101" }
+  ],
+  "conflicts": [
+    {
+      "taskUuid": "ghi012",
+      "taskTitle": "Fix tests",
+      "issueNumber": 102,
+      "reason": "Status mismatch: Lisa=\"in-progress\", GitHub=\"closed\"",
+      "resolution": "remote",
+      "localUpdatedAt": "2026-01-22T10:00:00Z",
+      "remoteUpdatedAt": "2026-01-22T11:00:00Z"
+    }
+  ]
+}
+```
+
+### Error
+```json
+{
+  "status": "error",
+  "error": "Not authenticated. Run: gh auth login"
+}
+```
+
+## Workflow Examples
+
+### Bug Triage Workflow
+```bash
+# 1. Create issue
+lisa github issues create --repo owner/repo --title "Bug: Login fails" --labels bug,triage
+
+# 2. Add to project board
+lisa github projects add --repo owner/repo 1 123
+
+# 3. Set initial status
+lisa github projects set-field --repo owner/repo 1 ITEM_ID --field Status --value "Triage"
+
+# 4. After investigation, update priority and move to backlog
+lisa github issues label --repo owner/repo 123 --add priority-high --remove triage
+lisa github projects set-field --repo owner/repo 1 ITEM_ID --field Status --value "Backlog"
+```
+
+### Sprint Planning Workflow
+```bash
+# List items in backlog
+lisa github projects items --repo owner/repo 1 --limit 50
+
+# Move selected items to sprint
+lisa github projects set-field --repo owner/repo 1 ITEM_ID --field Status --value "Todo"
+lisa github issues assign --repo owner/repo 123 --to developer
+```
+
+### Task Sync Workflow
+```bash
+# 1. Start of day: Import any new GitHub issues as Lisa tasks
+lisa github sync --repo owner/repo --import
+
+# 2. Work on tasks in Lisa (status updates tracked automatically)
+lisa tasks update "Fix login bug" --status in-progress
+
+# 3. End of day: Export new tasks and sync status changes
+lisa github sync --repo owner/repo
+
+# 4. Check what would sync before running
+lisa github sync --repo owner/repo --dry-run
+```
+
+## Cross-model checklist
+- Claude: Use JSON output for parsing; concise instructions
+- Gemini: Explicit commands; minimal formatting
+- All models: Always include --repo flag; parse JSON responses
+
+## Notes
+- Requires `gh` CLI v2.0+ or `GITHUB_TOKEN` environment variable
+- Projects v2 uses GraphQL API (requires appropriate permissions)
+- Rate limits apply per GitHub API policies
+- `--repo` flag is always required (no auto-detection)
+
+## See Also
+- `/git` skill for PR creation, CI triggers, version bumping
+- `/jira` skill for Jira integration (similar command structure)
+- `/tasks` skill for Lisa's internal task management

package/dist/project/.lisa/skills/lisa/SKILL.md

@@ -112,6 +112,28 @@ When user asks for a retrospective, follow these steps:
   - `👧 lisa-> ` for conversational responses
 - For memory and task queries, include the storage mode at the end in parentheses:
   - Example: `👧 lisa-> Tasks: (neo4j)` or `👧 lisa-> Recent Memories: (zep-cloud)`
+
+### Task Display Rules
+- **ALWAYS sort tasks by `created_at` descending** (newest first)
+- Show the most recent tasks at the top of each section
+- Include the date for each task (format: "Jan 23" or "Jan 23, 2026")
+- Group by status (Active/In Progress, Pending/Todo, Completed/Done) but sort within each group by date
+- Example format:
+  ```
+  👧 lisa-> Tasks: (neo4j)
+  
+  Active (3):
+  1. 📋 Newest task here (Jan 23)
+  2. 📋 Second newest (Jan 22)
+  3. 📋 Third newest (Jan 20)
+  
+  Completed (2):
+  1. ✅ Recently completed (Jan 22)
+  2. ✅ Older completed (Jan 15)
+  ```
+
+### Memory Display Rules
+- Sort memories by `created_at` descending (newest first)
 - Example format:
   ```
   👧 lisa-> Recent Memories: (neo4j)

package/dist/project/.lisa/skills/memory/SKILL.md

@@ -31,12 +31,13 @@ Organize facts into these categories (skip empty categories):
 6. **Open Items** - Pending tasks, known issues
 
 ### How to Summarize
+- **ALWAYS sort memories by `created_at` descending** (newest first)
 - Group related facts together
 - Use bullet points for clarity
 - Include specific file names and paths when relevant
-- Mention dates/timeframes if available
+- Include the date for each memory (format: "Jan 23" or "Jan 23, 2026")
 - Filter out expired or superseded facts (check `expired_at` field)
-- Prioritize recent facts over older ones
+- Prioritize recent facts over older ones - show newest at top of each section
 - Extract the `fact` field from each item - that's the human-readable content
 
 ### Example Output Format