ima-claude 2.18.0 → 2.25.0

package/plugins/ima-claude/skills/mcp-atlassian/references/direct-api-bulk.md

@@ -0,0 +1,149 @@
+# Atlassian Direct API — Bulk Operations
+
+MCP gap: no batch/bulk endpoints. Use these patterns for multi-issue operations.
+
+See [direct-api-auth.md](direct-api-auth.md) for auth setup.
+
+All examples use Gateway (Bearer) auth.
+
+---
+
+### Bulk Edit Issues (Jira v3)
+
+**API:** `POST /rest/api/3/issue/bulk`
+**When:** Updating the same fields on many issues at once.
+
+```bash
+curl -s -X POST \
+  -H "Authorization: Bearer $ATLASSIAN_BEARER_TOKEN" \
+  -H "Content-Type: application/json" \
+  -d '{
+    "issueUpdates": [
+      {
+        "issueIdOrKey": "PROJ-101",
+        "fields": {"priority": {"name": "High"}, "labels": ["urgent"]}
+      },
+      {
+        "issueIdOrKey": "PROJ-102",
+        "fields": {"priority": {"name": "High"}, "labels": ["urgent"]}
+      }
+    ]
+  }' \
+  "https://api.atlassian.com/ex/jira/$ATLASSIAN_CLOUD_ID/rest/api/3/issue/bulk" \
+  | jq '.errors'
+```
+
+#### Notes
+- Max ~50 issues per request (Atlassian soft limit)
+- Response includes per-issue errors — check `.errors` for partial failures
+- Each issue can have different field updates
+- This endpoint may not be available on all Jira Cloud plans
+
+---
+
+### Bulk Transition (Loop Pattern)
+
+**When:** Moving many issues through a workflow step (e.g., close all done issues).
+
+This uses the MCP `transitionJiraIssue` in a loop. No direct bulk transition API exists.
+
+**Pattern:**
+1. Find issues with JQL via MCP `searchJiraIssuesUsingJql`
+2. Get transitions for one representative issue via MCP `getTransitionsForJiraIssue`
+3. Loop `transitionJiraIssue` for each issue
+
+```
+# Step 1: Find issues
+searchJiraIssuesUsingJql
+  cloudId: "<cloudId>"
+  jql: "project = PROJ AND status = 'In Review'"
+  maxResults: 50
+  fields: ["summary", "status"]
+
+# Step 2: Get transition ID (same for all issues in the same workflow)
+getTransitionsForJiraIssue
+  cloudId: "<cloudId>"
+  issueIdOrKey: "PROJ-101"  # any issue from the results
+
+# Step 3: Transition each issue
+# Repeat for each issue key from Step 1:
+transitionJiraIssue
+  cloudId: "<cloudId>"
+  issueIdOrKey: "PROJ-101"
+  transition: {"id": "<transitionId>"}
+```
+
+#### Notes
+- Rate limit: ~100 requests/minute for Jira Cloud
+- For large batches (50+ issues), add a brief delay between calls
+- If issues span different workflows, group by issue type and get transitions per group
+
+---
+
+### Paginated JQL Fetch
+
+**When:** Fetching more results than the default page size (50).
+
+Use MCP `searchJiraIssuesUsingJql` with pagination:
+
+```
+# Page 1
+searchJiraIssuesUsingJql
+  cloudId: "<cloudId>"
+  jql: "project = PROJ AND status != Done"
+  maxResults: 50
+  startAt: 0
+  fields: ["summary", "status"]
+
+# Page 2
+searchJiraIssuesUsingJql
+  cloudId: "<cloudId>"
+  jql: "project = PROJ AND status != Done"
+  maxResults: 50
+  startAt: 50
+  fields: ["summary", "status"]
+```
+
+Or via direct API for more control:
+
+```bash
+curl -s \
+  -H "Authorization: Bearer $ATLASSIAN_BEARER_TOKEN" \
+  -H "Content-Type: application/json" \
+  -d '{
+    "jql": "project = PROJ AND status != Done ORDER BY created DESC",
+    "maxResults": 100,
+    "startAt": 0,
+    "fields": ["summary", "status", "assignee"]
+  }' \
+  "https://api.atlassian.com/ex/jira/$ATLASSIAN_CLOUD_ID/rest/api/3/search" \
+  | jq '{total: .total, count: (.issues | length), issues: [.issues[] | {key, summary: .fields.summary, status: .fields.status.name}]}'
+```
+
+#### Notes
+- MCP `searchJiraIssuesUsingJql` max is typically 50 per page
+- Direct API `POST /search` supports up to 100 per page
+- Check `.total` in response to know when to stop paginating
+- Use `POST` (not `GET`) for the search endpoint — JQL strings can exceed URL length limits
+
+---
+
+### Bulk Add Labels
+
+**When:** Tagging many issues with the same label.
+
+```bash
+# For each issue, use the update operations syntax
+for KEY in PROJ-101 PROJ-102 PROJ-103; do
+  curl -s -X PUT \
+    -H "Authorization: Bearer $ATLASSIAN_BEARER_TOKEN" \
+    -H "Content-Type: application/json" \
+    -d '{"update": {"labels": [{"add": "reviewed"}]}}' \
+    "https://api.atlassian.com/ex/jira/$ATLASSIAN_CLOUD_ID/rest/api/3/issue/$KEY"
+  echo "Labeled: $KEY"
+done
+```
+
+#### Notes
+- Uses Jira's `update` operations (add/remove/set) — more precise than replacing the entire `fields.labels` array
+- Same pattern works for `components`, `fixVersions`, and other array fields

package/plugins/ima-claude/skills/mcp-atlassian/references/direct-api-misc.md

@@ -0,0 +1,195 @@
+# Atlassian Direct API — Miscellaneous Operations
+
+MCP gaps: comment edit/delete, watchers, components, versions, page deletion.
+
+See [direct-api-auth.md](direct-api-auth.md) for auth setup.
+
+All examples use Gateway (Bearer) auth.
+
+---
+
+## Comments
+
+### Edit a Jira Comment
+
+**API:** `PUT /rest/api/3/issue/{issueKey}/comment/{commentId}`
+**When:** Correcting or updating an existing comment.
+
+```bash
+curl -s -X PUT \
+  -H "Authorization: Bearer $ATLASSIAN_BEARER_TOKEN" \
+  -H "Content-Type: application/json" \
+  -d '{
+    "body": {
+      "type": "doc",
+      "version": 1,
+      "content": [
+        {
+          "type": "paragraph",
+          "content": [{"type": "text", "text": "Updated comment text"}]
+        }
+      ]
+    }
+  }' \
+  "https://api.atlassian.com/ex/jira/$ATLASSIAN_CLOUD_ID/rest/api/3/issue/PROJ-123/comment/10042"
+```
+
+#### Notes
+- Comment body must be ADF (not Markdown) for the v3 API
+- Get comment IDs from `getJiraIssue` with `fields: ["comment"]`
+- Only the comment author or an admin can edit
+
+### Delete a Jira Comment
+
+**API:** `DELETE /rest/api/3/issue/{issueKey}/comment/{commentId}`
+**When:** Removing erroneous or sensitive comments.
+
+```bash
+curl -s -X DELETE \
+  -H "Authorization: Bearer $ATLASSIAN_BEARER_TOKEN" \
+  "https://api.atlassian.com/ex/jira/$ATLASSIAN_CLOUD_ID/rest/api/3/issue/PROJ-123/comment/10042"
+```
+
+#### Notes
+- Returns HTTP 204 on success (no body)
+- Only the comment author or an admin can delete
+
+---
+
+## Watchers
+
+### Get Watchers
+
+**API:** `GET /rest/api/3/issue/{issueKey}/watchers`
+**When:** Checking who is watching an issue.
+
+```bash
+curl -s \
+  -H "Authorization: Bearer $ATLASSIAN_BEARER_TOKEN" \
+  "https://api.atlassian.com/ex/jira/$ATLASSIAN_CLOUD_ID/rest/api/3/issue/PROJ-123/watchers" \
+  | jq '.watchers[] | {accountId, displayName}'
+```
+
+### Add a Watcher
+
+**API:** `POST /rest/api/3/issue/{issueKey}/watchers`
+**When:** Subscribing someone to issue notifications.
+
+```bash
+curl -s -X POST \
+  -H "Authorization: Bearer $ATLASSIAN_BEARER_TOKEN" \
+  -H "Content-Type: application/json" \
+  -d '"5b10a2844c20165700ede21g"' \
+  "https://api.atlassian.com/ex/jira/$ATLASSIAN_CLOUD_ID/rest/api/3/issue/PROJ-123/watchers"
+```
+
+#### Notes
+- Body is a **raw JSON string** (the accountId in quotes), not an object
+- Get `accountId` from MCP `lookupJiraAccountId`
+
+### Remove a Watcher
+
+**API:** `DELETE /rest/api/3/issue/{issueKey}/watchers?accountId={accountId}`
+**When:** Unsubscribing someone from issue notifications.
+
+```bash
+curl -s -X DELETE \
+  -H "Authorization: Bearer $ATLASSIAN_BEARER_TOKEN" \
+  "https://api.atlassian.com/ex/jira/$ATLASSIAN_CLOUD_ID/rest/api/3/issue/PROJ-123/watchers?accountId=5b10a2844c20165700ede21g"
+```
+
+---
+
+## Components
+
+### List Project Components
+
+**API:** `GET /rest/api/3/project/{projectKey}/components`
+**When:** Finding component IDs for issue creation or filtering.
+
+```bash
+curl -s \
+  -H "Authorization: Bearer $ATLASSIAN_BEARER_TOKEN" \
+  "https://api.atlassian.com/ex/jira/$ATLASSIAN_CLOUD_ID/rest/api/3/project/PROJ/components" \
+  | jq '.[] | {id, name, lead: .lead.displayName}'
+```
+
+### Create a Component
+
+**API:** `POST /rest/api/3/component`
+**When:** Adding a new component to a project.
+
+```bash
+curl -s -X POST \
+  -H "Authorization: Bearer $ATLASSIAN_BEARER_TOKEN" \
+  -H "Content-Type: application/json" \
+  -d '{
+    "name": "Authentication",
+    "project": "PROJ",
+    "description": "Auth and identity management",
+    "leadAccountId": "5b10a2844c20165700ede21g"
+  }' \
+  "https://api.atlassian.com/ex/jira/$ATLASSIAN_CLOUD_ID/rest/api/3/component" \
+  | jq '{id, name}'
+```
+
+---
+
+## Versions (Releases)
+
+### List Project Versions
+
+**API:** `GET /rest/api/3/project/{projectKey}/versions`
+**When:** Finding version IDs for fix-version assignment.
+
+```bash
+curl -s \
+  -H "Authorization: Bearer $ATLASSIAN_BEARER_TOKEN" \
+  "https://api.atlassian.com/ex/jira/$ATLASSIAN_CLOUD_ID/rest/api/3/project/PROJ/versions" \
+  | jq '.[] | {id, name, released, releaseDate}'
+```
+
+### Create a Version
+
+**API:** `POST /rest/api/3/version`
+**When:** Setting up a new release version.
+
+```bash
+curl -s -X POST \
+  -H "Authorization: Bearer $ATLASSIAN_BEARER_TOKEN" \
+  -H "Content-Type: application/json" \
+  -d '{
+    "name": "v2.1.0",
+    "projectId": 10001,
+    "description": "Q2 release",
+    "releaseDate": "2026-06-30",
+    "released": false
+  }' \
+  "https://api.atlassian.com/ex/jira/$ATLASSIAN_CLOUD_ID/rest/api/3/version" \
+  | jq '{id, name}'
+```
+
+#### Notes
+- Uses numeric `projectId`, not project key — get it from `getVisibleJiraProjects`
+
+---
+
+## Confluence Page Deletion
+
+### Delete a Confluence Page
+
+**API:** `DELETE /wiki/api/v2/pages/{pageId}`
+**When:** Removing outdated or draft Confluence pages.
+
+```bash
+curl -s -X DELETE \
+  -H "Authorization: Bearer $ATLASSIAN_BEARER_TOKEN" \
+  "https://api.atlassian.com/ex/confluence/$ATLASSIAN_CLOUD_ID/wiki/api/v2/pages/12345"
+```
+
+#### Notes
+- Uses Confluence **v2 API** (not v1)
+- Returns HTTP 204 on success
+- Page is moved to trash first (recoverable for 30 days)
+- Get page ID from MCP `getConfluencePage` or `searchConfluenceUsingCql`
+- Child pages become orphans — reassign or delete them first

package/plugins/ima-claude/skills/mcp-atlassian/references/direct-api-sprints.md

@@ -0,0 +1,158 @@
+# Atlassian Direct API — Sprint & Board Management
+
+MCP gap: no Scrum/Kanban board or sprint tools. The Agile API uses a different base path.
+
+See [direct-api-auth.md](direct-api-auth.md) for auth setup.
+
+All examples use Gateway (Bearer) auth. The Agile API base is:
+```
+https://api.atlassian.com/ex/jira/$ATLASSIAN_CLOUD_ID/rest/agile/1.0
+```
+
+---
+
+### List Boards
+
+**API:** `GET /rest/agile/1.0/board`
+**When:** Finding the board ID for a project.
+
+```bash
+curl -s \
+  -H "Authorization: Bearer $ATLASSIAN_BEARER_TOKEN" \
+  "https://api.atlassian.com/ex/jira/$ATLASSIAN_CLOUD_ID/rest/agile/1.0/board?projectKeyOrId=PROJ" \
+  | jq '.values[] | {id, name, type}'
+```
+
+#### Notes
+- Filter by project with `projectKeyOrId` param
+- `type` is `scrum` or `kanban`
+- Board ID is needed for all subsequent sprint operations
+
+---
+
+### Get Active Sprint
+
+**API:** `GET /rest/agile/1.0/board/{boardId}/sprint?state=active`
+**When:** Finding the current sprint to add issues to.
+
+```bash
+curl -s \
+  -H "Authorization: Bearer $ATLASSIAN_BEARER_TOKEN" \
+  "https://api.atlassian.com/ex/jira/$ATLASSIAN_CLOUD_ID/rest/agile/1.0/board/42/sprint?state=active" \
+  | jq '.values[] | {id, name, state, startDate, endDate}'
+```
+
+#### Notes
+- `state` filter accepts: `future`, `active`, `closed`
+- Multiple states: `state=active,future`
+- Only Scrum boards have sprints — Kanban boards return empty
+
+---
+
+### Get Issues in a Sprint
+
+**API:** `GET /rest/agile/1.0/sprint/{sprintId}/issue`
+**When:** Reviewing what's in a sprint.
+
+```bash
+curl -s \
+  -H "Authorization: Bearer $ATLASSIAN_BEARER_TOKEN" \
+  "https://api.atlassian.com/ex/jira/$ATLASSIAN_CLOUD_ID/rest/agile/1.0/sprint/100/issue?fields=summary,status,assignee" \
+  | jq '.issues[] | {key, summary: .fields.summary, status: .fields.status.name}'
+```
+
+#### Notes
+- Use `fields` param to limit response size (same as Jira REST API v3)
+- Supports `jql` param for additional filtering within the sprint
+- Paginated: use `startAt` and `maxResults` for large sprints
+
+---
+
+### Move Issues to a Sprint
+
+**API:** `POST /rest/agile/1.0/sprint/{sprintId}/issue`
+**When:** Adding issues to a sprint (sprint planning).
+
+```bash
+curl -s -X POST \
+  -H "Authorization: Bearer $ATLASSIAN_BEARER_TOKEN" \
+  -H "Content-Type: application/json" \
+  -d '{"issues": ["PROJ-101", "PROJ-102", "PROJ-103"]}' \
+  "https://api.atlassian.com/ex/jira/$ATLASSIAN_CLOUD_ID/rest/agile/1.0/sprint/100/issue"
+```
+
+#### Notes
+- Accepts issue keys or issue IDs
+- Issues are moved from their current sprint (or backlog) to the target sprint
+- No response body on success (HTTP 204)
+- To move to backlog: use `POST /rest/agile/1.0/backlog/issue` with same body
+
+---
+
+### Create a Sprint
+
+**API:** `POST /rest/agile/1.0/sprint`
+**When:** Setting up a new sprint.
+
+```bash
+curl -s -X POST \
+  -H "Authorization: Bearer $ATLASSIAN_BEARER_TOKEN" \
+  -H "Content-Type: application/json" \
+  -d '{
+    "name": "Sprint 42",
+    "originBoardId": 42,
+    "startDate": "2026-04-06T09:00:00.000Z",
+    "endDate": "2026-04-20T17:00:00.000Z",
+    "goal": "Complete auth migration"
+  }' \
+  "https://api.atlassian.com/ex/jira/$ATLASSIAN_CLOUD_ID/rest/agile/1.0/sprint" \
+  | jq '{id, name, state}'
+```
+
+#### Notes
+- `originBoardId` is required — use the board ID from "List Boards"
+- Dates are ISO 8601
+- Sprint starts in `future` state
+
+---
+
+### Start or Close a Sprint
+
+**API:** `PUT /rest/agile/1.0/sprint/{sprintId}`
+**When:** Starting a planned sprint or closing a completed one.
+
+```bash
+# Start a sprint
+curl -s -X PUT \
+  -H "Authorization: Bearer $ATLASSIAN_BEARER_TOKEN" \
+  -H "Content-Type: application/json" \
+  -d '{"state": "active"}' \
+  "https://api.atlassian.com/ex/jira/$ATLASSIAN_CLOUD_ID/rest/agile/1.0/sprint/100"
+
+# Close a sprint (must specify where incomplete issues go)
+curl -s -X PUT \
+  -H "Authorization: Bearer $ATLASSIAN_BEARER_TOKEN" \
+  -H "Content-Type: application/json" \
+  -d '{"state": "closed"}' \
+  "https://api.atlassian.com/ex/jira/$ATLASSIAN_CLOUD_ID/rest/agile/1.0/sprint/100"
+```
+
+#### Notes
+- Only one sprint can be `active` per board at a time
+- When closing, incomplete issues move to the backlog by default
+- To move incomplete issues to a specific sprint, close the sprint via the Jira UI (API doesn't support the move-to-sprint parameter natively)
+
+---
+
+### Move Issues to Backlog
+
+**API:** `POST /rest/agile/1.0/backlog/issue`
+**When:** Removing issues from a sprint without deleting them.
+
+```bash
+curl -s -X POST \
+  -H "Authorization: Bearer $ATLASSIAN_BEARER_TOKEN" \
+  -H "Content-Type: application/json" \
+  -d '{"issues": ["PROJ-101", "PROJ-102"]}' \
+  "https://api.atlassian.com/ex/jira/$ATLASSIAN_CLOUD_ID/rest/agile/1.0/backlog/issue"
+```

package/plugins/ima-claude/skills/mcp-context7/SKILL.md

@@ -5,105 +5,73 @@ description: Use Context7 MCP for official library documentation, framework APIs
 
 # Context7 MCP - Library Documentation
 
-Use Context7 for official library documentation instead of web searching or guessing APIs.
+Use Context7 for official library docs instead of web searching or guessing APIs.
 
-## MCP Tools
+## Tool
 
 | Tool | Purpose |
 |------|---------|
-| `mcp__context7__search` | Search for libraries and get documentation |
-
-## Basic Usage
-
-Context7 combines library resolution and documentation retrieval into a single tool.
+| `mcp__context7__search` | Search libraries and retrieve documentation |
 
 ```
 mcp__context7__search
   query: "How to use QDialog component in Quasar"
 ```
 
-**Parameters**:
-- `query` (required): Your question or search query including the library name
-
-The tool will:
-1. Identify the library from your query
-2. Find the relevant documentation
-3. Return focused, relevant docs
-
 ## Query Optimization
 
-**Be specific and include**:
-- Component/function names: "QDialog component API props events slots"
-- What you want to do: "How to set up authentication with JWT"
-- Context: "React useState hook example with TypeScript"
+Include component/function name + what you want to do + context. Be specific.
 
-**Good queries**:
-| Query | Why It's Good |
-|-------|---------------|
+| Good Query | Why |
+|------------|-----|
 | "Quasar QDialog props and events" | Specific component, clear intent |
-| "React useEffect cleanup function" | Specific hook, specific aspect |
-| "Prisma findMany where clause syntax" | Specific method, specific feature |
+| "React useEffect cleanup function" | Specific hook + aspect |
+| "Prisma findMany where clause syntax" | Specific method + feature |
 | "Express middleware error handling" | Framework + feature |
 
-**Avoid vague queries**:
-- ❌ "How does Quasar work?"
-- ✅ "How to create a Quasar button with icon"
+Avoid: "How does Quasar work?" — use: "How to create a Quasar button with icon"
 
 ## Decision Logic
 
 ```
-IF question about library/framework API:
-    → Use Context7
-ELSE IF import statement detected AND user asks about that library:
-    → Use Context7
-ELSE IF general programming concept (closures, promises, etc.):
-    → Use native Claude knowledge
-ELSE IF library not found:
-    → Fallback to WebSearch or Tavily
-ELSE IF asking for "latest" or "new" features post-cutoff:
-    → Use Tavily instead
+IF library/framework API question → Context7
+IF import detected AND user asks about that library → Context7
+IF general programming concept (closures, promises) → native Claude knowledge
+IF library not found → fallback to Tavily
+IF "latest" / post-cutoff features → Tavily instead
 ```
 
 ## When NOT to Use
 
-- General programming questions (no specific library)
-- Debugging code that doesn't involve library APIs
-- Simple syntax questions Claude already knows
-- User wants current/latest info post-cutoff (use Tavily instead)
+- No specific library involved
+- Debugging business logic (no library APIs)
+- Simple syntax Claude already knows
+- Current/latest info post-cutoff → use Tavily
 
-## Common Libraries Supported
+## Supported Libraries
 
-**Frontend**: React, Vue, Quasar, Next.js, Nuxt, Svelte, Angular, Tailwind, Bootstrap
-**Backend**: Express, Fastify, Nest.js, tRPC, Prisma, Sequelize, TypeORM
-**Utilities**: Lodash, Ramda, date-fns, Zod, Yup, Joi
-**Build**: Vite, Webpack, Rollup, ESBuild
+**Frontend**: React, Vue, Quasar, Next.js, Nuxt, Svelte, Angular, Tailwind, Bootstrap  
+**Backend**: Express, Fastify, Nest.js, tRPC, Prisma, Sequelize, TypeORM  
+**Utilities**: Lodash, Ramda, date-fns, Zod, Yup, Joi  
+**Build**: Vite, Webpack, Rollup, ESBuild  
 **Testing**: Jest, Vitest, Playwright, Cypress
 
 ## Examples
 
-| User Request | Action |
-|--------------|--------|
-| "How to use QDialog in Vue?" | search(query: "QDialog component Quasar Vue") |
-| "React useState example" | search(query: "React useState hook example") |
-| "Prisma query syntax" | search(query: "Prisma findMany where query") |
-| "What's a closure?" | Native Claude (no library) |
-| "Latest React 19 features" | Use Tavily (current info needed) |
+| Request | Action |
+|---------|--------|
+| "How to use QDialog in Vue?" | `search("QDialog component Quasar Vue")` |
+| "React useState example" | `search("React useState hook example")` |
+| "Prisma query syntax" | `search("Prisma findMany where query")` |
+| "What's a closure?" | Native Claude |
+| "Latest React 19 features" | Tavily |
 
-## Multiple Queries
-
-If initial results aren't sufficient, refine your query:
-1. First attempt: "Quasar form validation"
-2. If needed: "Quasar QForm validation rules API"
-3. If needed: "Quasar field validation with Vuelidate"
+If initial results insufficient, refine: "Quasar form validation" → "Quasar QForm validation rules API"
 
 ## Setup
 
-No API key required. Install with:
 ```bash
 bun run scripts/setup-mcp.ts
-```
-
-Or manually:
-```bash
+# or manually:
 claude mcp add --scope user context7 -- npx -y @upstash/context7-mcp@latest
 ```