heyteam-cli 1.0.0

package/.agent/workflows/ship-code.md

@@ -0,0 +1,59 @@
+---
+description: Commit and push code to current branch - no PR, no Slack, just code push
+---
+// turbo-all
+
+# Ship Code (Commit & Push Only)
+
+Reference the project configuration from `heyteam-instructions.md`.
+
+## Prerequisites
+
+### Required MCP Servers
+This workflow requires **GitHub** and **Atlassian (Jira)** MCP servers to be configured.
+- **VSCode / VSCode Insiders:** Search `@mcp github` and `@mcp atlassian` in the chat panel
+- **IntelliJ:** Add GitHub and Atlassian MCP server configurations to your MCP settings
+
+### Repository Access Check
+Verify the authenticated user has access to `digicert/dtm`. **If access is denied, STOP execution.**
+
+## Steps
+
+1. **Check for uncommitted changes**
+```bash
+git status --porcelain
+```
+
+2. **If there are staged or unstaged changes, generate commit message and commit**
+   - Get the diff of changes:
+   ```bash
+   git diff HEAD
+   ```
+   - Generate a professional, meaningful commit message based on the changes
+   - Format: `<type>: <description>` (e.g., "feat: add user authentication", "fix: resolve null pointer in login")
+   - Commit the changes:
+   ```bash
+   # Add only tracked files (updates/deletions) - do NOT add untracked files
+   git add -u
+   git commit -m "GENERATED_MESSAGE"
+   ```
+
+3. **Push changes to remote**
+```bash
+git push origin HEAD
+```
+
+4. **Get current branch name**
+```bash
+git branch --show-current
+```
+
+5. **Add Jira Comment**
+   - Extract Jira ticket ID from the current branch name
+     - Pattern: look for `DTM-XXXX` in the branch name (e.g., `feature/DTM-2494-some-description` → `DTM-2494`)
+   - If found, add a meaningful comment summarizing the changes and commit message
+   - If no Jira ticket ID can be extracted, skip this step
+
+## Return
+
+Report the commit message generated, push status, and Jira comment status (added, skipped, or ticket not found). That's it - no PR creation.

package/.agent/workflows/ship-dev.md

@@ -0,0 +1,95 @@
+---
+description: Ship to dev environment - creates PR with dev-deploy labels, optional Slack notification
+---
+// turbo-all
+
+# Ship to Development
+
+Reference the project configuration from `heyteam-instructions.md`.
+
+## Prerequisites
+
+### Required MCP Servers
+This workflow requires **GitHub** and **Atlassian (Jira)** MCP servers to be configured.
+- **VSCode / VSCode Insiders:** Search `@mcp github` and `@mcp atlassian` in the chat panel
+- **IntelliJ:** Add GitHub and Atlassian MCP server configurations to your MCP settings
+
+### Repository Access Check
+Verify the authenticated user has access to `digicert/dtm`. **If access is denied, STOP execution.**
+
+## Steps
+
+1. **Check for uncommitted changes**
+```bash
+git status --porcelain
+```
+
+2. **If there are staged or unstaged changes, generate commit message and commit**
+   - Get the diff of changes:
+   ```bash
+   git diff HEAD
+   ```
+   - Generate a professional, meaningful commit message based on the changes
+   - Format: `<type>: <description>` (e.g., "feat: add user authentication", "fix: resolve null pointer in login")
+   - Commit the changes:
+   ```bash
+   # Add only tracked files (updates/deletions) - do NOT add untracked files
+   git add -u
+   git commit -m "GENERATED_MESSAGE"
+   ```
+
+3. **Push changes to remote**
+```bash
+git push origin HEAD
+```
+
+4. **Identify the repository**
+```bash
+git remote -v
+```
+
+5. **Get current branch**
+```bash
+git branch --show-current
+```
+
+6. **Determine target branch and label:**
+
+   **Backend (dtm-backend):**
+   - If branch starts with `deployment/dev/` → target is `{branch}-trigger`, label is `dev-deploy`
+   - Otherwise → target is `develop`, label is `dev-deploy`
+
+   **UI (dtm):**
+   - If branch starts with `deployment/dev/` → target is `{branch}-trigger`, label is `dev-deploy-user-interface`
+   - Otherwise → target is `develop`, label is `dev-deploy-user-interface`
+
+7. **Check if an open PR already exists**
+
+8. **Create or update PR with the determined target branch**
+
+9. **Add the appropriate dev label**
+
+10. **Get current GitHub username and add assignees/reviewers (filtered):**
+   - Get authenticated user's GitHub username
+   - Define team lists based on repository:
+     - **UI (dtm)**: priti-kumari-dc, surbhi-gupta-dc, shiva-burade-dc
+     - **Backend (dtm-backend)**: jaydeep-raval-dc, swaraj-dhumale-dc, sharmajetesh, shiva-burade-dc
+   - **Filter out the PR creator** from both assignees and reviewers lists
+
+11. **Add Jira Comment**
+   - Extract Jira ticket ID from the current branch name
+     - Pattern: look for `DTM-XXXX` in the branch name (e.g., `feature/DTM-2494-some-description` → `DTM-2494`)
+   - If found, add a meaningful comment summarizing the changes, PR URL, and target environment (Development)
+   - If no Jira ticket ID can be extracted, skip this step
+
+12. **[OPTIONAL] Send Slack notification (default: OFF)**
+   - Only send if explicitly requested by user
+   ```bash
+   curl -X POST -H 'Content-type: application/json' \
+     --data '{"PR_LINK": "PR_URL_HERE"}' \
+     '{{SLACK_WEBHOOK_URL}}'
+   ```
+
+## Return
+
+Report the PR URL, commit message used, target branch, label, assignees, reviewers, Jira comment status, and Slack status (sent or skipped).

package/.agent/workflows/ship-int.md

@@ -0,0 +1,96 @@
+---
+description: Ship to int environment - creates PR with integration labels, supports release branch lookup
+---
+// turbo-all
+
+# Ship to Integration
+
+Reference the project configuration from `heyteam-instructions.md`.
+
+## Prerequisites
+
+### Required MCP Servers
+This workflow requires **GitHub** and **Atlassian (Jira)** MCP servers to be configured.
+- **VSCode / VSCode Insiders:** Search `@mcp github` and `@mcp atlassian` in the chat panel
+- **IntelliJ:** Add GitHub and Atlassian MCP server configurations to your MCP settings
+
+### Repository Access Check
+Verify the authenticated user has access to `digicert/dtm`. **If access is denied, STOP execution.**
+
+## Steps
+
+1. **Check for uncommitted changes**
+```bash
+git status --porcelain
+```
+
+2. **If there are staged or unstaged changes, generate commit message and commit**
+   - Get the diff of changes:
+   ```bash
+   git diff HEAD
+   ```
+   - Generate a professional, meaningful commit message based on the changes
+   - Format: `<type>: <description>` (e.g., "feat: add user authentication", "fix: resolve null pointer in login")
+   - Commit the changes:
+   ```bash
+   # Add only tracked files (updates/deletions) - do NOT add untracked files
+   git add -u
+   git commit -m "GENERATED_MESSAGE"
+   ```
+
+3. **Push changes to remote**
+```bash
+git push origin HEAD
+```
+
+4. **Identify the repository**
+```bash
+git remote -v
+```
+
+5. **Get current branch**
+```bash
+git branch --show-current
+```
+
+6. **Determine target branch and label:**
+
+   **Backend (dtm-backend):**
+   - If branch starts with `deployment/int/` → target is `{branch}-trigger`, label is `integration-deploy`
+   - If "latest release" requested → use `list_branches` to find latest `release/*` branch, label is `integration-deploy`
+   - Otherwise → target is `develop`, label is `integration-deploy`
+
+   **UI (dtm):**
+   - If branch starts with `deployment/int/` → target is `{branch}-trigger`, label is `integration-deploy-user-interface`
+   - If "latest release" requested → use `list_branches` to find latest `release/*` branch, label is `integration-deploy-user-interface`
+   - Otherwise → target is `develop`, label is `integration-deploy-user-interface`
+
+7. **Check if an open PR already exists**
+
+8. **Create or update PR with the determined target branch**
+
+9. **Add the appropriate integration label**
+
+10. **Get current GitHub username and add assignees/reviewers (filtered):**
+   - Get authenticated user's GitHub username
+   - Define team lists based on repository:
+     - **UI (dtm)**: priti-kumari-dc, surbhi-gupta-dc, shiva-burade-dc
+     - **Backend (dtm-backend)**: jaydeep-raval-dc, swaraj-dhumale-dc, sharmajetesh, shiva-burade-dc
+   - **Filter out the PR creator** from both assignees and reviewers lists
+
+11. **Add Jira Comment**
+   - Extract Jira ticket ID from the current branch name
+     - Pattern: look for `DTM-XXXX` in the branch name (e.g., `feature/DTM-2494-some-description` → `DTM-2494`)
+   - If found, add a meaningful comment summarizing the changes, PR URL, and target environment (Integration)
+   - If no Jira ticket ID can be extracted, skip this step
+
+12. **Send Slack notification:**
+```bash
+curl -X POST -H 'Content-type: application/json' \
+  --data '{"PR_LINK": "PR_URL_HERE"}' \
+  '{{SLACK_WEBHOOK_URL}}'
+```
+
+## Return
+
+Report the PR URL, commit message used, target branch, label, assignees, reviewers, Jira comment status, and Slack status.

package/.agent/workflows/ship-prod.md

@@ -0,0 +1,94 @@
+---
+description: Ship to prod environment - creates PR with production labels, requires multiple approvals
+---
+// turbo-all
+
+# Ship to Production
+
+⚠️ **PRODUCTION DEPLOYMENT** - Requires multiple approvals
+
+Reference the project configuration from `heyteam-instructions.md`.
+
+## Prerequisites
+
+### Required MCP Servers
+This workflow requires **GitHub** and **Atlassian (Jira)** MCP servers to be configured.
+- **VSCode / VSCode Insiders:** Search `@mcp github` and `@mcp atlassian` in the chat panel
+- **IntelliJ:** Add GitHub and Atlassian MCP server configurations to your MCP settings
+
+### Repository Access Check
+Verify the authenticated user has access to `digicert/dtm`. **If access is denied, STOP execution.**
+
+## Steps
+
+1. **Check for uncommitted changes**
+```bash
+git status --porcelain
+```
+
+2. **If there are staged or unstaged changes, generate commit message and commit**
+   - Get the diff of changes:
+   ```bash
+   git diff HEAD
+   ```
+   - Generate a professional, meaningful commit message based on the changes
+   - Format: `<type>: <description>` (e.g., "feat: add user authentication", "fix: resolve null pointer in login")
+   - Commit the changes:
+   ```bash
+   # Add only tracked files (updates/deletions) - do NOT add untracked files
+   git add -u
+   git commit -m "GENERATED_MESSAGE"
+   ```
+
+3. **Push changes to remote**
+```bash
+git push origin HEAD
+```
+
+4. **Identify the repository**
+```bash
+git remote -v
+```
+
+5. **Get current branch**
+```bash
+git branch --show-current
+```
+
+6. **Determine label:**
+   - **Backend (dtm-backend)**: `prod-deploy`
+   - **UI (dtm)**: `integration-deploy-user-interface`
+
+7. **Verify CI/CD checks have passed on source branch**
+
+8. **Check if an open PR already exists**
+
+9. **Create or update PR:**
+   - Title: "Production Release - [DATE]"
+   - Include summary of all changes
+
+10. **Add the appropriate production label**
+
+11. **Get current GitHub username and add ALL team members as assignees/reviewers (filtered):**
+   - Get authenticated user's GitHub username
+   - Define team lists based on repository:
+     - **UI (dtm)**: priti-kumari-dc, surbhi-gupta-dc, shiva-burade-dc
+     - **Backend (dtm-backend)**: jaydeep-raval-dc, swaraj-dhumale-dc, sharmajetesh, shiva-burade-dc
+   - **Filter out the PR creator** from both assignees and reviewers lists
+
+12. **Add Jira Comment**
+   - Extract Jira ticket ID from the current branch name
+     - Pattern: look for `DTM-XXXX` in the branch name (e.g., `feature/DTM-2494-some-description` → `DTM-2494`)
+   - If found, add a meaningful comment summarizing the changes, PR URL, and target environment (Production)
+   - If no Jira ticket ID can be extracted, skip this step
+
+13. **Send Slack notification:**
+```bash
+curl -X POST -H 'Content-type: application/json' \
+  --data '{"PR_LINK": "PR_URL_HERE"}' \
+  '{{SLACK_WEBHOOK_URL}}'
+```
+
+## Return
+
+Report the PR URL, commit message used, label, assignees, reviewers, Jira comment status, Slack status, and remind that multiple approvals are required.

package/.agent/workflows/ship-release.md

@@ -0,0 +1,92 @@
+---
+description: Ship to release branch - creates PR against latest release branch with appropriate labels
+---
+// turbo-all
+
+# Ship to Release
+
+Reference the project configuration from `heyteam-instructions.md`.
+
+## Prerequisites
+
+### Required MCP Servers
+This workflow requires **GitHub** and **Atlassian (Jira)** MCP servers to be configured.
+- **VSCode / VSCode Insiders:** Search `@mcp github` and `@mcp atlassian` in the chat panel
+- **IntelliJ:** Add GitHub and Atlassian MCP server configurations to your MCP settings
+
+### Repository Access Check
+Verify the authenticated user has access to `digicert/dtm`. **If access is denied, STOP execution.**
+
+## Steps
+
+1. **Check for uncommitted changes**
+```bash
+git status --porcelain
+```
+
+2. **If there are staged or unstaged changes, generate commit message and commit**
+   - Get the diff of changes:
+   ```bash
+   git diff HEAD
+   ```
+   - Generate a professional, meaningful commit message based on the changes
+   - Format: `<type>: <description>` (e.g., "feat: add user authentication", "fix: resolve null pointer in login")
+   - Commit the changes:
+   ```bash
+   # Add only tracked files (updates/deletions) - do NOT add untracked files
+   git add -u
+   git commit -m "GENERATED_MESSAGE"
+   ```
+
+3. **Push changes to remote**
+```bash
+git push origin HEAD
+```
+
+4. **Identify the repository**
+```bash
+git remote -v
+```
+
+5. **Get current branch**
+```bash
+git branch --show-current
+```
+
+6. **Find latest release branch**
+   - Use `list_branches` to find branches matching `release/*`
+   - Sort by creation date, use the most recent
+
+7. **Determine label based on repository:**
+   - **Backend (dtm-backend)**: `integration-deploy`
+   - **UI (dtm)**: `integration-deploy-user-interface`
+
+8. **Check if an open PR already exists from current branch to the release branch**
+
+9. **Create or update PR:**
+   - Target: latest `release/*` branch found in step 6
+   - Add the appropriate label from step 7
+
+10. **Get current GitHub username and add assignees/reviewers (filtered):**
+   - Get authenticated user's GitHub username
+   - Define team lists based on repository:
+     - **UI (dtm)**: priti-kumari-dc, surbhi-gupta-dc, shiva-burade-dc
+     - **Backend (dtm-backend)**: jaydeep-raval-dc, swaraj-dhumale-dc, sharmajetesh, shiva-burade-dc
+   - **Filter out the PR creator** from both assignees and reviewers lists
+
+11. **Add Jira Comment**
+   - Extract Jira ticket ID from the current branch name
+     - Pattern: look for `DTM-XXXX` in the branch name (e.g., `feature/DTM-2494-some-description` → `DTM-2494`)
+   - If found, add a meaningful comment summarizing the changes, PR URL, and target environment (Release)
+   - If no Jira ticket ID can be extracted, skip this step
+
+12. **[MANDATORY] Send Slack notification:**
+```bash
+curl -X POST -H 'Content-type: application/json' \
+  --data '{"PR_LINK": "PR_URL_HERE"}' \
+  '{{SLACK_WEBHOOK_URL}}'
+```
+
+## Return
+
+Report the PR URL, commit message used, release branch used, label, assignees, reviewers, Jira comment status, and Slack status.

package/.github/prompts/ship-code.prompt.md

@@ -0,0 +1,76 @@
+# Ship Code (Commit & Push Only)
+
+**Context**: Read the project configuration from `heyteam-instructions.md`.
+
+## Prerequisites
+
+### Required MCP Servers
+
+This workflow requires **GitHub** and **Atlassian (Jira)** MCP servers to be configured.
+
+> [!IMPORTANT]
+> **For VSCode / VSCode Insiders:**
+> Search `@mcp github` and `@mcp atlassian` in the chat panel to configure MCP servers.
+>
+> **For IntelliJ:**
+> Add the GitHub and Atlassian MCP server configurations to your MCP settings.
+
+### Repository Access Check
+
+Before proceeding, verify that the authenticated user has access to the `digicert/dtm` repository:
+- Use GitHub MCP tools to check access to `digicert/dtm`
+- **If access is denied, STOP execution immediately** and inform the user
+
+## Task
+
+Commit and push code to current branch. No PR creation, no Slack notification.
+
+## Steps
+
+1. **Check for uncommitted changes**
+   ```bash
+   git status --porcelain
+   ```
+
+2. **If there are staged or unstaged changes, generate commit message and commit**
+   - Get the diff of changes:
+   ```bash
+   git diff HEAD
+   ```
+   - Analyze the changes and generate a professional, meaningful commit message
+   - Use conventional commit format: `<type>: <description>`
+     - Types: feat, fix, docs, style, refactor, test, chore
+     - Example: "feat: add user authentication module"
+   - Commit the changes:
+   ```bash
+   # Add only tracked files (updates/deletions) - do NOT add untracked files unless explicitly asked
+   git add -u
+   git commit -m "GENERATED_MESSAGE"
+   ```
+
+3. **Push changes to remote**
+   ```bash
+   git push origin HEAD
+   ```
+
+4. **Get current branch name**
+   ```bash
+   git branch --show-current
+   ```
+
+5. **Add Jira Comment**
+   - Extract Jira ticket ID from the current branch name
+     - Pattern: look for `DTM-XXXX` in the branch name (e.g., `feature/DTM-2494-some-description` → `DTM-2494`)
+   - If a Jira ticket ID is found, add a meaningful comment to the ticket summarizing:
+     - What changes were made (based on the diff)
+     - The commit message used
+   - If no Jira ticket ID can be extracted, skip this step
+
+## Expected Output
+
+Report back with:
+- Commit message generated (if any)
+- Push status
+- Jira comment status (added, skipped, or ticket not found)
+
+That's it - no PR, no Slack, just code push.

package/.github/prompts/ship-dev.prompt.md

@@ -0,0 +1,133 @@
+# Ship to Development
+
+**Context**: Read the project configuration from `heyteam-instructions.md`.
+
+## Prerequisites
+
+### Required MCP Servers
+
+This workflow requires **GitHub** and **Atlassian (Jira)** MCP servers to be configured.
+
+> [!IMPORTANT]
+> **For VSCode / VSCode Insiders:**
+> Search `@mcp github` and `@mcp atlassian` in the chat panel to configure MCP servers.
+>
+> **For IntelliJ:**
+> Add the GitHub and Atlassian MCP server configurations to your MCP settings.
+
+### Repository Access Check
+
+Before proceeding, verify that the authenticated user has access to the `digicert/dtm` repository:
+- Use GitHub MCP tools to check access to `digicert/dtm`
+- **If access is denied, STOP execution immediately** and inform the user
+
+## Task
+
+Create a Pull Request for development deployment.
+
+## Steps
+
+1. **Check for uncommitted changes**
+   ```bash
+   git status --porcelain
+   ```
+
+2. **If there are staged or unstaged changes, generate commit message and commit**
+   - Get the diff of changes:
+   ```bash
+   git diff HEAD
+   ```
+   - Analyze the changes and generate a professional, meaningful commit message
+   - Use conventional commit format: `<type>: <description>`
+     - Types: feat, fix, docs, style, refactor, test, chore
+     - Example: "feat: add user authentication module"
+   - Commit the changes:
+   ```bash
+   # Add only tracked files (updates/deletions) - do NOT add untracked files unless explicitly asked
+   git add -u
+   git commit -m "GENERATED_MESSAGE"
+   ```
+
+3. **Push changes to remote**
+   ```bash
+   git push origin HEAD
+   ```
+
+4. **Identify repository**
+   - Check if current repo is `digicert/dtm` (UI) or `digicert/dtm-backend` (Backend)
+
+5. **Get current branch name**
+   ```bash
+   git branch --show-current
+   ```
+
+6. **Determine target branch and label**
+   
+   **If Backend repo (dtm-backend):**
+   - If branch matches `deployment/dev/**`:
+     - Target: `{current-branch}-trigger` (append `-trigger`)
+     - Label: `dev-deploy`
+   - Otherwise:
+     - Target: `develop`
+     - Label: `dev-deploy`
+   
+   **If UI repo (dtm):**
+   - If branch matches `deployment/dev/**`:
+     - Target: `{current-branch}-trigger` (append `-trigger`)
+     - Label: `dev-deploy-user-interface`
+   - Otherwise:
+     - Target: `develop`
+     - Label: `dev-deploy-user-interface`
+
+7. **Check for existing PR**
+   - Use `list_pull_requests` to check if an open PR already exists
+
+8. **Create or Update PR**
+   - Use `create_pull_request` with:
+     - `owner`: `digicert`
+     - `repo`: `dtm` or `dtm-backend`
+     - `head`: current branch
+     - `base`: determined target branch
+     - `title`: Generate from branch name
+     - `body`: Summary of changes
+
+9. **Add Label**
+   - Use `add_issue_labels` to add the appropriate dev label
+
+10. **Get current GitHub username and add Assignees/Reviewers (filtered)**
+    - Get the authenticated user's GitHub username
+    - Define team lists based on repository:
+      - **If UI repo (dtm)**: priti-kumari-dc, surbhi-gupta-dc, shiva-burade-dc
+      - **If Backend repo (dtm-backend)**: jaydeep-raval-dc, swaraj-dhumale-dc, sharmajetesh, shiva-burade-dc
+    - **Filter out the PR creator** from both assignees and reviewers lists
+    - Use `assign_issue` for assignees
+    - Use `request_pull_request_review` for reviewers
+
+11. **Add Jira Comment**
+    - Extract Jira ticket ID from the current branch name
+      - Pattern: look for `DTM-XXXX` in the branch name (e.g., `feature/DTM-2494-some-description` → `DTM-2494`)
+    - If a Jira ticket ID is found, add a meaningful comment to the ticket summarizing:
+      - What changes were made (based on the diff)
+      - The PR URL
+      - The target environment (Development)
+    - If no Jira ticket ID can be extracted, skip this step
+
+12. **[OPTIONAL] Send Slack Notification (default: OFF)**
+    - Only send if explicitly requested by user
+    ```bash
+    curl -X POST -H 'Content-type: application/json' \
+      --data '{"PR_LINK": "PR_URL_HERE"}' \
+      '{{SLACK_WEBHOOK_URL}}'
+    ```
+
+## Expected Output
+
+Report back with:
+- Commit message generated (if any)
+- PR URL
+- Target branch
+- Label added (`dev-deploy` or `dev-deploy-user-interface`)
+- Assignees added (excluding PR creator)
+- Reviewers requested (excluding PR creator)
+- Jira comment status (added, skipped, or ticket not found)
+- Slack notification status (sent or skipped)