@groupby/ai-dev 0.2.1 → 0.3.0

package/toolsets/toolsets/rzlv-flow/skills/jira-wrap-sync/SKILL.md

@@ -1,260 +0,0 @@
----
-name: jira-wrap-sync
-description: Wrap up your current work on a Jira ticket. Analyzes local ticket changes and code changes (git diff), drafts a comprehensive Jira comment, runs FCMP sync, and presents multi-select actions (sync fields, add comment, transition status, create PR, update Confluence). Use when you're done working on a ticket or want to sync progress.
----
-
-Wrap up work on the currently focused Jira ticket. Detects what changed (ticket fields and code), drafts a Jira comment summarizing progress, runs the FCMP protocol before syncing, and presents a multi-select action menu so you can sync fields, comment, transition status, and create a PR in one pass.
-
-## Requirements
-
-Requires: Atlassian MCP (`atlassian-rovo`). See the rzlv-flow toolset README for setup.
-Optional: GitHub MCP for Pull Request creation (action 4).
-
-## Resources to Load
-
-Before executing, read these resource files:
-
-- `docs/ai/resources/fcmp-protocol.md` — **critical** for the sync protocol before any Jira writes
-- `docs/ai/resources/sync-state-format.md` — YAML frontmatter schema for reading/updating ticket files
-
-## Process
-
-### Step 1: Identify the Ticket
-
-- Use `focused_ticket` from conversation context (set by `jira-ticket-focus`).
-- If not available, ask the user for the ticket key.
-- Locate the local ticket file at the path stored in `focused_ticket_path`, or find it using the `jira-file-structure.md` rules.
-
-### Step 2: Analyze All Changes
-
-**a) Local ticket file changes:**
-- Read the current `{TICKET-KEY}.md` file.
-- Compare the content against the last synced state stored in the `sync` frontmatter fields.
-- Detect changes to: description, story points, acceptance criteria, labels, priority.
-- Note which fields were modified locally.
-
-**b) Code changes:**
-- Run `git diff --stat` for an overview of changes.
-- Run `git diff` (or `git diff --staged` if changes are staged) for details.
-- Check recent commits on the working branch: `git log --oneline -10`.
-- Map code changes to acceptance criteria where possible.
-- Summarize: files changed, insertions, deletions.
-
-**c) Acceptance criteria progress:**
-- Read the AC list from the ticket file.
-- Based on code changes and commit messages, infer which AC items have been completed.
-- Show checkbox progress:
-  ```
-  - [x] AC 1 — Completed (matches changes in auth-controller.ts)
-  - [x] AC 2 — Completed (matches changes in rate-limiter.ts)
-  - [ ] AC 3 — Not yet addressed
-  ```
-- Note: this is a best-effort inference. The user confirms the final state.
-
-### Step 3: Draft Jira Comment
-
-Build a comprehensive comment with the standardized prefix `[rzlv-flow Update]`:
-
-```
-[rzlv-flow Update]
-
-{IF TICKET FIELD CHANGES:}
-**Ticket Updates:**
-- {field change 1}
-- {field change 2}
-
-{IF CODE CHANGES:}
-**Implementation Progress:**
-- {code change summary line 1}
-- {code change summary line 2}
-
-**Files Modified:**
-- {file1}: {brief description}
-- {file2}: {brief description}
-
-**Acceptance Criteria:**
-- [x] {completed AC 1}
-- [x] {completed AC 2}
-- [ ] {remaining AC 3}
-**Progress:** {X}/{Y} completed
-
-**Next Steps:** {suggested next action}
-
-Context: {optional PR link or Confluence doc link}
-```
-
-### Step 4: FCMP Preview (Prepare PUSH — Dry Run)
-
-Before executing any write operations, run the full FCMP cycle and present a dry-run preview:
-
-1. **FETCH** — Get the current ticket state from Jira via MCP.
-2. **COMPARE** — Check for remote changes since last sync (compare `sync.version` and `sync.remote_updated`).
-3. **MERGE** — If conflicts detected, show a diff of remote changes vs local changes and resolve with the user.
-4. **Preview** — Show a dry-run diff of what will change if the user proceeds:
-
-```
-### FCMP Preview (Dry Run)
-{IF NO REMOTE CHANGES:}
-✓ Remote is unchanged since last sync — safe to push.
-
-{IF REMOTE CHANGES DETECTED:}
-⚠️ Remote changes detected since last sync:
-- {field}: {old_value} → {new_value}
-
-**Proposed local → remote changes:**
-- Description: {diff summary}
-- Story Points: {old} → {new}
-- Status: {current} (no change)
-
-Proceed with sync? (y/n)
-```
-
-Only proceed to the action menu after the FCMP preview is confirmed.
-
-### Step 5: Present Multi-Select Action Menu
-
-Present all detected changes, the draft comment, and a multi-select numbered menu. The user picks multiple actions via comma-separated numbers.
-
-```
-### Available Actions (Multi-Select)
-
-{IF TICKET FIELD CHANGES DETECTED:}
-1. Sync ticket fields to Jira (description, points, AC)
-
-{IF CODE CHANGES OR TICKET CHANGES:}
-2. Add comment to Jira (with the draft summary above)
-
-3. Transition status (you'll specify the target status)
-
-{IF CODE CHANGES AND COMMITS EXIST:}
-4. Create Pull Request (via GitHub MCP)
-
-{IF SIGNIFICANT CHANGES:}
-5. Update Confluence technical docs
-
-6. Cancel (do nothing)
-
-**Choose actions (comma-separated):** [1,2,3,4]
-
-Examples:
-- "1,2,3,4" = Sync ticket + comment + transition + create PR
-- "2,3" = Comment + transition only
-- "6" = Cancel all actions
-```
-
-### Step 6: Execute Selected Actions
-
-Parse the comma-separated input. Execute each selected action in order:
-
-**Action 1 — Sync ticket fields:**
-- Update description, story points, AC, and any other changed fields via MCP.
-- Include the `version` field for optimistic locking per FCMP.
-- On 409 conflict, re-run FCMP from Fetch.
-
-**Action 2 — Add comment:**
-- Push the draft comment via MCP.
-- For detailed comment procedures, see the `jira-comment` skill.
-
-**Action 3 — Transition status:**
-- Fetch available transitions via MCP.
-- Present as a numbered list for the user to select target status.
-- Execute the transition via MCP.
-- For detailed transition procedures, see the `jira-status` skill.
-
-**Action 4 — Create Pull Request (via GitHub MCP):**
-1. Check for unpushed commits: `git log origin/{branch}..HEAD`
-2. If unpushed commits exist, ask: "Push commits first? (y/n)"
-3. If yes: `git push origin {branch}`
-4. Detect base branch (check git config or default to `main`).
-5. Build PR details:
-   - **Title:** `{TICKET-KEY}: {ticket summary}`
-   - **Body:**
-     ```
-     ## {TICKET-KEY}: {Ticket Summary}
-
-     **Jira:** https://{instance}/browse/{TICKET-KEY}
-     {IF CONFLUENCE DOCS:}
-     **Confluence:** {confluence_link}
-
-     ### Changes
-     {ticket updates + code changes from the draft comment}
-
-     ### Acceptance Criteria
-     - [x] {completed criterion}
-     - [ ] {remaining criterion}
-
-     ### Testing Notes
-     {Any notes from _work/ folder if they exist}
-     ```
-6. Create PR via GitHub MCP: `create_pull_request()`
-7. Return and display the PR URL.
-
-**Action 5 — Update Confluence:**
-- Prompt the user for what to update and where.
-- Follow FCMP protocol for the Confluence update.
-
-**Action 6 — Cancel:**
-- Exit without performing any actions. Ignore all other selections if "6" is included.
-
-### Step 7: Post-Execution
-
-After all selected MCP operations:
-
-1. **FETCH** the final ticket state from Jira.
-2. Update the local `{TICKET-KEY}.md` with the new sync state (version, last_synced, status).
-3. Confirm what was completed:
-   - List each action and its result.
-   - If a PR was created, display the PR URL.
-   - Suggest a next action if remaining work exists.
-
-### Error Handling
-
-- If any MCP operation fails, report which step failed and continue with remaining operations.
-- If the GitHub MCP is not configured, skip PR creation with a warning: "GitHub MCP not configured. Skipping PR creation."
-- On optimistic locking conflicts (409), re-run FCMP from Fetch and retry.
-
-## Output Format
-
-```
-## 🎬 Wrap Up: {TICKET-KEY}
-
-### Local Ticket Changes Detected
-{IF FIELD CHANGES:}
-- **Description:** {change summary or "No changes"}
-- **Story Points:** {old} → {new} (or "No change")
-- **Acceptance Criteria:** {added/removed items} (or "No changes")
-
-{IF NO CHANGES:}
-_(No local ticket changes detected)_
-
-### Code Changes Detected
-{IF GIT DIFF:}
-{n} files changed, {lines added} insertions(+), {lines deleted} deletions(-)
-
-Modified files:
-- {file1}
-- {file2}
-
-{IF NO CHANGES:}
-_(No code changes detected)_
-
-### Acceptance Criteria Status
-- [x] {Completed criterion}
-- [ ] {Remaining criterion}
-
-**Progress:** {X}/{Y} completed
-
-### Draft Comment for Jira
-{The full draft comment from Step 3}
-
----
-
-### Available Actions (Multi-Select)
-{Numbered action list from Step 5}
-```
-
-## Session Context
-
-After running, update conversational context:
-- **last_wrap_actions** — Which actions were executed
-- **pr_url** — The PR URL if one was created