@deimoscloud/coreai 0.1.19 → 0.1.20

package/skills/git/pr-create/SKILL.md

@@ -0,0 +1,195 @@
+---
+description: Use when creating a pull request, opening a PR, or when code is ready for review. Creates PR with proper format, links to Jira ticket, and automatically transitions the ticket to "In Review" status.
+argument-hint: [ticket reference or PR title]
+requires: [git]
+optional: [jira]
+---
+
+# Create Pull Request
+
+You are creating a PR for: **$ARGUMENTS**
+
+## Pre-PR Checklist
+
+Before creating a PR, verify:
+
+### 1. All Commits Pushed
+
+```bash
+git status
+```
+
+Ensure no uncommitted changes. If there are changes, use `/git-commit` first.
+
+### 2. Branch is Up-to-Date
+
+```bash
+git fetch origin main
+git log origin/main..HEAD --oneline
+```
+
+If behind main, rebase:
+```bash
+git rebase origin/main
+git push --force-with-lease
+```
+
+### 3. CI Checks Ready
+
+All local checks should have passed during `/git-commit`.
+
+## Extract Ticket Information
+
+### From Branch Name
+```bash
+git branch --show-current
+# Expected format: feature/{{JIRA_PROJECT}}-XX-description
+```
+
+### From Jira (if available)
+Use MCP to get ticket details:
+- Title
+- Description
+- Acceptance criteria
+
+## Create Pull Request
+
+### PR Title Format
+```
+[{{JIRA_PROJECT}}-XX] <Brief description>
+```
+
+**Examples:**
+- `[{{JIRA_PROJECT}}-123] Add feature state machine`
+- `[{{JIRA_PROJECT}}-456] Fix connection timeout handling`
+
+### PR Body Template
+
+```markdown
+## Summary
+
+Brief description of what this PR does.
+
+## Changes
+
+- Change 1
+- Change 2
+- Change 3
+
+## Ticket
+
+[{{JIRA_PROJECT}}-XX]({{JIRA_URL}}/browse/{{JIRA_PROJECT}}-XX)
+
+## Testing
+
+- [ ] Unit tests added/updated
+- [ ] Manual testing completed
+- [ ] Tested on [device/emulator]
+
+## Checklist
+
+- [ ] Code follows development standards
+- [ ] All quality checks pass
+- [ ] No debug code or TODOs left
+- [ ] Documentation updated (if applicable)
+```
+
+### Create PR with GitHub CLI
+
+```bash
+gh pr create \
+  --title "[{{JIRA_PROJECT}}-XX] <description>" \
+  --body "$(cat <<'EOF'
+## Summary
+
+<description>
+
+## Changes
+
+- <change 1>
+- <change 2>
+
+## Ticket
+
+[{{JIRA_PROJECT}}-XX]({{JIRA_URL}}/browse/{{JIRA_PROJECT}}-XX)
+
+## Testing
+
+- [ ] Unit tests added/updated
+- [ ] Manual testing completed
+
+## Checklist
+
+- [ ] Code follows development standards
+- [ ] All quality checks pass
+- [ ] No debug code or TODOs left
+EOF
+)"
+```
+
+## Update Jira Ticket
+
+**MANDATORY:** After PR is created, transition the Jira ticket to "In Review".
+
+### Using Atlassian MCP
+
+1. Transition ticket to "In Review" status
+2. Add comment with PR link:
+
+```
+PR created: <PR URL>
+
+Changes:
+- <summary of changes>
+
+Ready for code review.
+```
+
+### Fallback (if MCP unavailable)
+
+Report to user:
+```
+Please manually update Jira ticket {{JIRA_PROJECT}}-XX:
+- Status: In Review
+- Add comment with PR link: <URL>
+```
+
+## Request Review
+
+If you know who should review:
+```bash
+gh pr edit <PR_NUMBER> --add-reviewer <github-username>
+```
+
+## Completion
+
+After PR creation, report:
+```
+Pull Request Created
+
+PR: #<number> - [{{JIRA_PROJECT}}-XX] <title>
+URL: <github PR URL>
+Branch: feature/{{JIRA_PROJECT}}-XX-description -> main
+
+Jira Updated:
+- Ticket {{JIRA_PROJECT}}-XX transitioned to "In Review"
+- Comment added with PR link
+
+Next Steps:
+- CI checks will run automatically
+- Await code review
+- Address any feedback
+```
+
+## Error Handling
+
+**If PR creation fails:**
+- Check if branch is pushed: `git push -u origin $(git branch --show-current)`
+- Check if PR already exists: `gh pr list --head $(git branch --show-current)`
+- Check GitHub CLI auth: `gh auth status`
+
+**If Jira transition fails:**
+- Note the failure in your completion report
+- Ask user to manually update Jira
+
+Now proceed with PR creation.

package/skills/git/worktree-cleanup/SKILL.md

@@ -0,0 +1,168 @@
+---
+description: Use when a PR has been merged, a ticket is complete, or development work is finished. Cleans up the git worktree created for parallel agent work. Typically used by the Engineering Manager after merge.
+argument-hint: TICKET-XX or worktree path
+requires: [git]
+---
+
+# Worktree Cleanup
+
+You are cleaning up the worktree for: **$ARGUMENTS**
+
+## When to Use
+
+- PR has been merged to main
+- Ticket is marked as Done
+- Development work is complete and no longer needed
+
+## Cleanup Steps
+
+### 1. Identify Worktree to Remove
+
+List all active worktrees:
+```bash
+cd {{PROJECT_ROOT}}
+git worktree list
+```
+
+**Expected output:**
+```
+{{PROJECT_ROOT}}                                              abc1234 [main]
+{{PROJECT_ROOT}}/../{{PROJECT_NAME}}-agent1-{{JIRA_PROJECT}}-123  def5678 [feature/{{JIRA_PROJECT}}-123-description]
+{{PROJECT_ROOT}}/../{{PROJECT_NAME}}-agent2-{{JIRA_PROJECT}}-456  ghi9012 [feature/{{JIRA_PROJECT}}-456-description]
+```
+
+### 2. Verify PR is Merged
+
+Before removing, confirm the PR is merged:
+```bash
+gh pr list --state merged --search "{{JIRA_PROJECT}}-XX"
+```
+
+Or check if the branch exists on remote:
+```bash
+git ls-remote --heads origin feature/{{JIRA_PROJECT}}-XX-description
+# Empty output = branch deleted (PR merged)
+```
+
+### 3. Remove Worktree
+
+```bash
+# From the main repository
+cd {{PROJECT_ROOT}}
+
+# Remove the worktree
+git worktree remove ../{{PROJECT_NAME}}-[agent-name]-{{JIRA_PROJECT}}-XX
+```
+
+### 4. Delete Local Branch (if exists)
+
+```bash
+git branch -d feature/{{JIRA_PROJECT}}-XX-description
+```
+
+If branch wasn't merged (force delete with caution):
+```bash
+git branch -D feature/{{JIRA_PROJECT}}-XX-description
+```
+
+### 5. Prune Stale Worktrees
+
+Clean up any stale worktree references:
+```bash
+git worktree prune
+```
+
+### 6. Verify Cleanup
+
+```bash
+git worktree list
+```
+
+Confirm the worktree no longer appears.
+
+## Batch Cleanup
+
+To clean up multiple worktrees at once:
+
+```bash
+# List all worktrees
+git worktree list
+
+# Remove each one
+git worktree remove ../{{PROJECT_NAME}}-agent1-{{JIRA_PROJECT}}-XXX
+git worktree remove ../{{PROJECT_NAME}}-agent2-{{JIRA_PROJECT}}-YYY
+
+# Prune all stale references
+git worktree prune
+```
+
+## Error Handling
+
+**If worktree has uncommitted changes:**
+```
+error: '<path>' contains modified or untracked files, use --force to delete it
+```
+
+Options:
+1. **If changes are needed:** Commit and push first, then remove
+2. **If changes can be discarded:** `git worktree remove --force ../path`
+
+**If worktree directory doesn't exist but git tracks it:**
+```bash
+git worktree prune
+```
+
+**If branch is not fully merged:**
+```bash
+# Check if branch was merged
+git branch --merged main | grep feature/{{JIRA_PROJECT}}-XX
+
+# If not merged but PR is closed/merged on GitHub, force delete
+git branch -D feature/{{JIRA_PROJECT}}-XX-description
+```
+
+## Update Jira (Optional)
+
+If the ticket isn't already Done, transition it:
+- Use `/jira-transition` to move to "Done"
+- Or use Atlassian MCP directly
+
+## Completion
+
+After cleanup, report:
+```
+Worktree Cleanup Complete
+
+Removed:
+- Worktree: {{PROJECT_ROOT}}/../{{PROJECT_NAME}}-[agent-name]-{{JIRA_PROJECT}}-XX
+- Branch: feature/{{JIRA_PROJECT}}-XX-description
+
+Active Worktrees:
+<output of git worktree list>
+
+Ticket {{JIRA_PROJECT}}-XX is ready to be marked as Done (if not already).
+```
+
+## Bulk Cleanup After Sprint
+
+To clean up all worktrees from a completed sprint:
+
+```bash
+# List all worktrees
+git worktree list
+
+# Remove all agent worktrees (keep main)
+for dir in ../{{PROJECT_NAME}}-*-{{JIRA_PROJECT}}-*; do
+  if [ -d "$dir" ]; then
+    git worktree remove "$dir" --force
+  fi
+done
+
+# Prune
+git worktree prune
+
+# Clean up merged branches
+git branch --merged main | grep -E "feature/{{JIRA_PROJECT}}-" | xargs -r git branch -d
+```
+
+Now proceed with the worktree cleanup.

package/skills/git/worktree-setup/SKILL.md

@@ -0,0 +1,112 @@
+---
+description: Use when starting work on a ticket, implementing a feature, fixing a bug, or beginning any development task. Sets up an isolated git worktree for parallel agent work, preventing conflicts when multiple agents work simultaneously.
+argument-hint: TICKET-XX [short-description]
+requires: [git]
+optional: [jira]
+---
+
+# Worktree Setup for Parallel Development
+
+You are setting up an isolated git worktree to work on: **$ARGUMENTS**
+
+## Why Worktrees?
+
+Multiple agents can work on different tickets simultaneously without conflicts. Each agent gets its own working directory with its own branch, completely isolated from other agents.
+
+## Setup Steps
+
+### 1. Parse Arguments
+
+Extract from `$ARGUMENTS`:
+- **Ticket ID:** {{JIRA_PROJECT}}-XX (required)
+- **Description:** Short description for branch name (optional, derive from ticket if not provided)
+
+### 2. Determine Your Agent Name
+
+Identify which agent you are (e.g., `backend-engineer`, `frontend-engineer`). This is used in the worktree path.
+
+### 3. Fetch Latest Main
+
+```bash
+cd {{PROJECT_ROOT}}
+git fetch origin main
+```
+
+### 4. Create Worktree
+
+```bash
+# Pattern: ../{{PROJECT_NAME}}-[agent-name]-{{JIRA_PROJECT}}-XX
+git worktree add ../{{PROJECT_NAME}}-[agent-name]-{{JIRA_PROJECT}}-XX -b feature/{{JIRA_PROJECT}}-XX-[description] origin/main
+```
+
+**Example:**
+```bash
+git worktree add ../{{PROJECT_NAME}}-backend-engineer-{{JIRA_PROJECT}}-123 -b feature/{{JIRA_PROJECT}}-123-feature-name origin/main
+```
+
+### 5. Verify Worktree
+
+```bash
+git worktree list
+```
+
+Confirm your new worktree appears in the list.
+
+### 6. Set Working Directory
+
+**CRITICAL:** All subsequent work must happen in the worktree directory:
+
+```
+{{PROJECT_ROOT}}/../{{PROJECT_NAME}}-[agent-name]-{{JIRA_PROJECT}}-XX/
+```
+
+Announce to the user:
+```
+Worktree created. Working directory is now:
+{{PROJECT_ROOT}}/../{{PROJECT_NAME}}-[agent-name]-{{JIRA_PROJECT}}-XX
+
+All code changes will be made in this isolated directory.
+```
+
+### 7. Update Jira (if not already done)
+
+If the ticket is not already "In Progress":
+- Transition ticket to "In Progress"
+- Add comment: "Starting work. Branch: `feature/{{JIRA_PROJECT}}-XX-[description]`"
+
+## Important Notes
+
+- **Never work in the main repository** when a worktree is active for your ticket
+- **One worktree per ticket** - if you already have a worktree for this ticket, use it instead of creating a new one
+- **Worktree cleanup** is handled by the Engineering Manager after PR merge via `/worktree-cleanup`
+
+## Error Handling
+
+**If worktree already exists:**
+```bash
+# Check existing worktrees
+git worktree list
+
+# If your worktree exists, just use it
+cd ../{{PROJECT_NAME}}-[agent-name]-{{JIRA_PROJECT}}-XX
+```
+
+**If branch already exists:**
+```bash
+# Use existing branch in new worktree
+git worktree add ../{{PROJECT_NAME}}-[agent-name]-{{JIRA_PROJECT}}-XX feature/{{JIRA_PROJECT}}-XX-[description]
+```
+
+## Completion
+
+After setup, announce:
+```
+Worktree ready for {{JIRA_PROJECT}}-XX
+
+Directory: {{PROJECT_ROOT}}/../{{PROJECT_NAME}}-[agent-name]-{{JIRA_PROJECT}}-XX
+Branch: feature/{{JIRA_PROJECT}}-XX-[description]
+
+Ready to begin implementation.
+```
+
+Now proceed with the worktree setup.

package/skills/jira/jira-create/SKILL.md

@@ -0,0 +1,201 @@
+---
+description: Use when creating a Jira ticket, adding a new task to backlog, reporting a bug, or creating a feature request. Ensures tickets have all required fields and follow the standard template.
+argument-hint: <type> <title> [description]
+requires: [jira]
+---
+
+# Create Jira Ticket
+
+You are creating a Jira ticket for: **$ARGUMENTS**
+
+## Ticket Types
+
+| Type | Use For |
+|------|---------|
+| **Story** | New user-facing features |
+| **Task** | Technical work, refactoring, infrastructure |
+| **Bug** | Defects, issues, broken functionality |
+| **Spike** | Research, investigation, prototyping |
+| **Improvement** | Enhancements to existing features |
+
+## Required Fields
+
+Every ticket MUST have:
+
+1. **Summary** - Clear, concise title
+2. **Type** - Story, Task, Bug, Spike, or Improvement
+3. **Description** - What needs to be done and why
+4. **Acceptance Criteria** - Definition of done (checklist)
+5. **Priority** - P0 (Critical), P1 (High), P2 (Medium), P3 (Low)
+6. **Labels** - Relevant labels
+
+## Create Ticket via Atlassian MCP
+
+### Using MCP
+
+```
+mcp__atlassian__createJiraIssue
+
+Project: {{JIRA_PROJECT}}
+Issue Type: <Story|Task|Bug|Spike|Improvement>
+Summary: <Clear title>
+Description: <Detailed description>
+Priority: <P0|P1|P2|P3>
+Labels: <comma-separated labels>
+```
+
+### Description Template
+
+```markdown
+## Overview
+[Brief description of what needs to be done]
+
+## Background
+[Why this is needed, context, related tickets]
+
+## Requirements
+- [Requirement 1]
+- [Requirement 2]
+
+## Acceptance Criteria
+- [ ] [Criterion 1]
+- [ ] [Criterion 2]
+- [ ] [Criterion 3]
+- [ ] Unit tests written and passing
+- [ ] Code reviewed and approved
+
+## Technical Notes
+[Any technical considerations, constraints, or suggestions]
+
+## References
+- [Links to PRD, design docs, related tickets]
+```
+
+## Ticket Templates by Type
+
+### Story Template
+
+```markdown
+## User Story
+As a [user type], I want [functionality] so that [benefit].
+
+## Background
+[Context and motivation]
+
+## Acceptance Criteria
+- [ ] [User-visible outcome 1]
+- [ ] [User-visible outcome 2]
+- [ ] Unit tests written
+- [ ] Manual testing completed
+
+## Design
+[Link to UI mockups if applicable]
+```
+
+### Bug Template
+
+```markdown
+## Bug Description
+[Clear description of the bug]
+
+## Steps to Reproduce
+1. [Step 1]
+2. [Step 2]
+3. [Step 3]
+
+## Expected Behavior
+[What should happen]
+
+## Actual Behavior
+[What actually happens]
+
+## Environment
+- Device: [e.g., device type]
+- OS Version: [e.g., version]
+- App Version: [e.g., 1.0.0]
+
+## Acceptance Criteria
+- [ ] Bug is fixed
+- [ ] Regression test added
+- [ ] Verified on affected device
+```
+
+### Task Template
+
+```markdown
+## Task Description
+[What needs to be done]
+
+## Background
+[Why this task is needed]
+
+## Scope
+- [Item 1]
+- [Item 2]
+
+## Out of Scope
+- [Item that is NOT part of this task]
+
+## Acceptance Criteria
+- [ ] [Deliverable 1]
+- [ ] [Deliverable 2]
+- [ ] Documentation updated (if applicable)
+```
+
+## Priority Guidelines
+
+| Priority | Criteria | Response |
+|----------|----------|----------|
+| **P0** | Production down, data loss, security issue | Immediate |
+| **P1** | Major feature broken, blocking release | This sprint |
+| **P2** | Important but not blocking | Next sprint |
+| **P3** | Nice to have, minor improvements | Backlog |
+
+## Local Fallback
+
+If Atlassian MCP is unavailable, create a local ticket file:
+
+**Path:** `/KnowledgeLibrary/tickets/backlog/{{JIRA_PROJECT}}-XXX-[short-description].md`
+
+```markdown
+# [{{JIRA_PROJECT}}-XXX] [Title]
+
+## Metadata
+- **Status:** Backlog
+- **Priority:** [P0|P1|P2|P3]
+- **Type:** [Story|Task|Bug|Spike|Improvement]
+- **Created By:** [agent-name]
+- **Created Date:** [YYYY-MM-DD]
+- **Labels:** [comma-separated]
+
+## Description
+[Full description]
+
+## Acceptance Criteria
+- [ ] [Criterion 1]
+- [ ] [Criterion 2]
+
+## References
+- [Links]
+```
+
+## Completion
+
+After ticket creation, report:
+```
+Jira Ticket Created
+
+Ticket: {{JIRA_PROJECT}}-XXX
+Title: [Summary]
+Type: [Type]
+Priority: [Priority]
+Status: Backlog
+
+URL: {{JIRA_URL}}/browse/{{JIRA_PROJECT}}-XXX
+
+Next Steps:
+- Ticket is in Backlog, ready for sprint planning
+- Use /delegate to assign when ready
+```
+
+Now proceed with ticket creation.