@mohammadhprp/system-prompt 0.12.1 → 0.12.2

package/framework/skills/gitlab-mcp/references/issues.md

@@ -1,141 +0,0 @@
-# Issue Management
-
-## Create
-
-```
-create_issue
-  project_id: "my-group/my-project"
-  title: "Login page returns 500"
-  description: "Steps to reproduce..."
-  labels: "bug,critical"
-  assignee_ids: [123]
-  milestone_id: 5
-```
-
-## Read
-
-```
-get_issue         -> single issue details
-list_issues       -> project issues (default: created by current user)
-  scope: "all"    -> list ALL issues (not just current user's)
-  state: "opened" -> filter by state
-  labels: "bug"   -> filter by labels
-my_issues         -> issues assigned to current user across all projects
-```
-
-**Important**: `list_issues` defaults to showing only issues created by the current user.
-Pass `scope: "all"` to see all project issues.
-
-## Update
-
-```
-update_issue
-  project_id: "my-group/my-project"
-  issue_iid: 10
-  state_event: "close"    # or "reopen"
-  labels: "bug,resolved"
-  assignee_ids: [456]
-```
-
-### Patch-based description update (token-efficient)
-
-```
-update_issue_description_patch
-  project_id: "my-group/my-project"
-  issue_iid: 10
-  patch_type: "search_replace"  # or "unified_diff"
-  patch: |
-    <<<<<<< SEARCH
-    Status: In progress
-    =======
-    Status: Ready for review
-    >>>>>>> REPLACE
-  dry_run: false
-  create_note: true
-```
-
-Applies a small patch to the issue description without sending the full text.
-Reduces token usage for AI agents editing long descriptions.
-
-**Search/Replace format**:
-```
-<<<<<<< SEARCH
-text to find
-=======
-replacement text
->>>>>>> REPLACE
-```
-
-**Options**:
-- `dry_run: true` — preview changes without updating
-- `create_note: true` — add a comment summarizing the change after update
-- `allow_multiple: true` — allow multiple matches to all be replaced (search_replace only)
-
-**Error handling**:
-- Search text not found → fails with clear message
-- Multiple matches (without `allow_multiple`) → fails with count
-- Patch results in identical description → fails (no-op)
-- Unified diff doesn't match → fails
-
-## Delete
-
-```
-delete_issue   -> permanently delete (destructive, cannot be undone)
-```
-
-## Issue Links
-
-Link related issues:
-
-```
-create_issue_link
-  project_id: "my-group/my-project"
-  issue_iid: 10
-  target_project_id: "my-group/other-project"
-  target_issue_iid: 20
-  link_type: "relates_to"  # or "blocks", "is_blocked_by"
-```
-
-```
-list_issue_links   -> list all linked issues
-get_issue_link     -> get specific link details
-delete_issue_link  -> remove a link
-```
-
-## Discussions & Notes
-
-Add comments:
-
-```
-create_issue_note
-  project_id: "my-group/my-project"
-  issue_iid: 10
-  body: "Confirmed, this is a regression"
-  discussion_id: "abc123"   # optional: reply to existing thread
-```
-
-```
-update_issue_note         -> edit a comment
-list_issue_discussions    -> list all discussion threads
-```
-
-### Emoji reactions
-
-```
-list_issue_emoji_reactions       -> list reactions on an issue
-create_issue_emoji_reaction      -> add reaction to an issue
-delete_issue_emoji_reaction      -> remove reaction from an issue
-list_issue_note_emoji_reactions  -> list reactions on an issue note or thread reply
-create_issue_note_emoji_reaction -> add reaction to an issue note or thread reply
-delete_issue_note_emoji_reaction -> remove reaction from an issue note or thread reply
-```
-
-Generic note creation (works for both issues and MRs):
-
-```
-create_note
-  project_id: "my-group/my-project"
-  noteable_type: "Issue"    # or "MergeRequest"
-  noteable_iid: 10
-  body: "Note content"
-```

package/framework/skills/gitlab-mcp/references/merge-requests.md

@@ -1,120 +0,0 @@
-# Merge Request Workflow
-
-## Create
-
-```
-create_merge_request
-  project_id: "my-group/my-project"
-  title: "Add user authentication"
-  source_branch: "feature/auth"
-  target_branch: "main"
-  description: "Implements OAuth2 login flow"
-  assignee_id: 123
-  labels: "feature,auth"
-```
-
-## Read & Track
-
-```
-get_merge_request           -> full MR details (by IID or branch name)
-list_merge_requests         -> list with filters (state, labels, author, etc.)
-  - without project_id: current user's MRs across all projects
-  - with project_id: MRs in that project
-get_merge_request_conflicts -> check for merge conflicts
-list_merge_request_pipelines -> list pipelines attached to an MR
-```
-
-## Update
-
-```
-update_merge_request
-  project_id: "my-group/my-project"
-  mergeRequestIid: 42
-  title: "Updated title"
-  state_event: "close"  # or "reopen"
-  assignee_ids: [123, 456]
-  labels: "feature,reviewed"
-```
-
-## Review & Approve
-
-See [code-review.md](code-review.md) for the full diff review workflow.
-
-```
-approve_merge_request       -> approve
-unapprove_merge_request     -> retract approval
-get_merge_request_approval_state -> check who approved, rules status
-```
-
-## Merge
-
-```
-merge_merge_request
-  project_id: "my-group/my-project"
-  mergeRequestIid: 42
-  should_remove_source_branch: true
-  squash: true
-  merge_when_pipeline_succeeds: true
-```
-
-**Warning**: `merge_merge_request` is destructive - cannot be undone.
-
-## Discussion Management
-
-### Threads (inline code comments)
-
-```
-create_merge_request_thread     -> new thread on a diff line
-resolve_merge_request_thread    -> mark thread resolved
-```
-
-### Notes (general comments)
-
-```
-create_merge_request_note       -> add comment
-get_merge_request_notes         -> list all comments
-update_merge_request_note       -> edit comment
-delete_merge_request_note       -> remove comment
-```
-
-### Discussion notes (replies in threads)
-
-```
-mr_discussions                         -> list all discussions
-create_merge_request_discussion_note   -> reply to thread
-update_merge_request_discussion_note   -> edit reply
-delete_merge_request_discussion_note   -> remove reply
-```
-
-### Draft notes (pending review)
-
-```
-create_draft_note          -> create pending comment
-list_draft_notes           -> see all drafts
-update_draft_note          -> edit before publishing
-delete_draft_note          -> discard
-publish_draft_note         -> publish single draft
-bulk_publish_draft_notes   -> publish all drafts at once
-```
-
-### Emoji reactions
-
-```
-list_merge_request_emoji_reactions       -> list reactions on an MR
-create_merge_request_emoji_reaction      -> add reaction to an MR
-delete_merge_request_emoji_reaction      -> remove reaction from an MR
-list_merge_request_note_emoji_reactions  -> list reactions on an MR note or thread reply
-create_merge_request_note_emoji_reaction -> add reaction to an MR note or thread reply
-delete_merge_request_note_emoji_reaction -> remove reaction from an MR note or thread reply
-```
-
-## Branch Comparison
-
-Compare without an existing MR:
-
-```
-get_branch_diffs
-  project_id: "my-group/my-project"
-  from: "main"
-  to: "feature/auth"
-```

package/framework/skills/gitlab-mcp/references/pipelines.md

@@ -1,67 +0,0 @@
-# Pipeline Operations
-
-> **Opt-in toolset**: Enable with `USE_PIPELINE=true` or `GITLAB_TOOLSETS=pipelines`
-
-## List & Inspect
-
-```
-list_pipelines             -> list pipelines with filters (status, ref, source)
-get_pipeline               -> pipeline details (status, duration, coverage)
-list_pipeline_jobs         -> all jobs in a pipeline
-list_pipeline_trigger_jobs -> trigger/bridge jobs (downstream pipelines)
-get_pipeline_job           -> single job details
-get_pipeline_job_output    -> job log output (supports pagination for large logs)
-```
-
-## Create & Control
-
-```
-create_pipeline            -> trigger new pipeline for a branch/tag
-  project_id: "my-group/my-project"
-  ref: "main"
-  variables: [{ key: "DEPLOY_ENV", value: "staging" }]
-```
-
-```
-retry_pipeline             -> retry all failed jobs in a pipeline
-cancel_pipeline            -> cancel running pipeline
-play_pipeline_job          -> run a manual job
-retry_pipeline_job         -> retry a single failed job
-cancel_pipeline_job        -> cancel a single running job
-```
-
-## Artifacts
-
-```
-list_job_artifacts         -> list files in a job's artifact archive
-get_job_artifact_file      -> get content of a single artifact file
-download_job_artifacts     -> download full artifact archive (zip) to local_path
-```
-
-## Deployments & Environments
-
-```
-list_deployments           -> list deployments with filters
-get_deployment             -> deployment details
-list_environments          -> list project environments
-get_environment            -> environment details
-```
-
-## Common Patterns
-
-### Check why a pipeline failed
-
-1. `list_pipelines` with `status: "failed"` -> get pipeline ID
-2. `list_pipeline_jobs` -> find failed job(s)
-3. `get_pipeline_job_output` -> read error logs
-
-### Retry failed pipeline
-
-1. `retry_pipeline` -> retries all failed jobs
-   OR
-2. `retry_pipeline_job` -> retry specific job only
-
-### Download test results
-
-1. `list_job_artifacts` -> find the test report file path
-2. `get_job_artifact_file` -> read the report content

package/framework/skills/gitlab-mcp/references/search.md

@@ -1,17 +0,0 @@
-# Code Search
-
-> **Opt-in toolset**: Enable with `GITLAB_TOOLSETS=search`
-
-Search requires GitLab advanced search or exact code search/Zoekt support on the target instance.
-
-## Scope
-
-```
-search_code          -> search code across all accessible projects
-search_project_code  -> search within one project
-search_group_code    -> search within one group
-```
-
-## Pattern
-
-Use the narrowest scope that can answer the question. Prefer `search_project_code` when the project is known, then broaden to group or instance-wide search only when needed.

package/framework/skills/gitlab-mcp/references/webhooks.md

@@ -1,32 +0,0 @@
-# Webhook Operations
-
-> **Opt-in toolset**: Enable with `GITLAB_TOOLSETS=webhooks`
-
-## List Webhooks
-
-Provide either `project_id` or `group_id`.
-
-```
-list_webhooks
-  project_id: "my-group/my-project"
-```
-
-## Inspect Recent Events
-
-GitLab exposes recent webhook events for the past 7 days.
-
-```
-list_webhook_events
-  project_id: "my-group/my-project"
-  webhook_id: 123
-  summary: true
-```
-
-Fetch full event details only after narrowing to the event ID.
-
-```
-get_webhook_event
-  project_id: "my-group/my-project"
-  webhook_id: 123
-  event_id: 456
-```

package/framework/skills/gitlab-mcp/references/work-items.md

@@ -1,50 +0,0 @@
-# Work Item Operations
-
-> **Opt-in toolset**: Enable with `GITLAB_TOOLSETS=workitems`
-
-Work items are GraphQL-based and cover issues, tasks, incidents, epics, objectives, requirements, tickets, and related hierarchy/status fields. Some status and custom field features require GitLab Premium/Ultimate.
-
-## Read
-
-```
-list_work_items              -> list work items with filters
-get_work_item                -> full details with status, hierarchy, type, labels, assignees, widgets
-list_work_item_notes         -> notes and discussions on a work item
-list_work_item_statuses      -> available statuses for a work item type
-list_custom_field_definitions -> custom field definitions for a work item type
-```
-
-## Create & Update
-
-```
-create_work_item
-  project_id: "my-group/my-project"
-  title: "Investigate checkout failure"
-  work_item_type: "issue"
-  description: "Steps to reproduce..."
-```
-
-```
-update_work_item             -> title, description, labels, assignees, state, parent, children, health, dates, custom fields
-convert_work_item_type       -> convert issue/task/incident/etc.
-move_work_item               -> move a work item to another project
-create_work_item_note        -> add a note, threaded reply, or internal note
-```
-
-## Emoji Reactions
-
-```
-list_work_item_emoji_reactions       -> list reactions on a work item
-create_work_item_emoji_reaction      -> add reaction to a work item
-delete_work_item_emoji_reaction      -> remove reaction from a work item
-list_work_item_note_emoji_reactions  -> list reactions on a work item note or thread reply
-create_work_item_note_emoji_reaction -> add reaction to a work item note or thread reply
-delete_work_item_note_emoji_reaction -> remove reaction from a work item note or thread reply
-```
-
-## Incident Timeline
-
-```
-get_timeline_events     -> list timeline events for an incident
-create_timeline_event   -> create an incident timeline event
-```

package/framework/skills/jira-mcp/SKILL.md

@@ -1,57 +0,0 @@
----
-name: jira-mcp
-description: Use this skill when working with the Jira MCP server tools for issue management, project management, comments, search, and related Jira workflows.
----
-
-# jira-mcp
-
-Jira MCP server providing 12 tools for interacting with your self-hosted Jira instance via the REST API v2.
-
-## Tools
-
-| Category           | Tools                                                                                                                                          | Default |
-|--------------------|------------------------------------------------------------------------------------------------------------------------------------------------|---------|
-| Issues (9 tools)   | `create_issue`, `get_issue`, `update_issue`, `delete_issue`, `search_issues`, `assign_issue`, `get_issue_types`, `add_comment`, `get_comments` | yes     |
-| Projects (2 tools) | `get_projects`, `get_project`                                                                                                                  | yes     |
-| Users (1 tool)     | `get_current_user`                                                                                                                             | yes     |
-
-All tools are available by default — there are no opt-in toolsets for this server.
-
-## Key Workflows
-
-### Issue Lifecycle
-
-`search_issues` → `get_issue` → `update_issue` / `assign_issue`
-
-### Create Issue (see references/issues.md)
-
-`get_project` → `get_issue_types` → `create_issue`
-
-### Comment Thread (see references/comments.md)
-
-`add_comment` → `get_comments`
-
-### Project Discovery (see references/projects.md)
-
-`get_projects` → `get_project` → `get_issue_types`
-
-## Parameter Hints
-
-- **projectKey**: uppercase project key (e.g., `PROJ`, `SCRUM`, `SUP`). Use `get_projects` to discover available keys.
-- **issueKey**: format `PROJECT-123` (e.g., `CHI-42`, `DEV-1337`)
-- **issueType**: varies by project — use `get_issue_types` to list valid types before creating. Common types: `Bug`, `Task`, `Story`, `Epic`, `Sub-task`
-- **search_issues**: uses JQL (Jira Query Language). Complex values (spaces, special chars) must be quoted: `status = "In Progress"`, `project = PROJ`
-- **Jql**: provide a raw JQL query string (not single-quoted — use double quotes inside for string values)
-- **maxResults**: `search_issues` defaults to 50. Increase for larger result sets.
-- **assignee**: Jira username (not display name or email). Use `get_current_user` to find your own username.
-- **Custom fields**: Pass custom field values directly as parameters (e.g., `customfield_10211: "Sprint 1"`). Discover field IDs via Jira REST API.
-
-## Destructive Tools
-
-`delete_issue` — permanently deletes an issue. Cannot be undone.
-
-## Advanced
-
-- **JQL Search**: full Jira Query Language support — combine operators (`AND`, `OR`, `NOT`), functions (`currentUser()`, `now()`, `startOfDay()`), and ordering (`ORDER BY created DESC`)
-- **Status transitions**: use `update_issue` with `status` to transition issues (e.g., `"In Progress"`, `"Done"`, `"Closed"`). Valid statuses depend on the project's workflow configuration.
-- **Custom fields**: map Jira custom field IDs to values via the `customFields` object or direct parameter names

package/framework/skills/jira-mcp/examples.md

@@ -1,31 +0,0 @@
-# Jira MCP Examples
-
-## Example 1: Create and Assign a Bug
-
-A production bug is discovered and needs to be tracked. Good agent behavior:
-
-- Use `jira_get_projects` to find the correct project key.
-- Use `jira_get_issue_types` to confirm valid types for the project.
-- Use `jira_create_issue` with project key, summary, description, priority, and labels.
-- Use `jira_assign_issue` to assign the bug to the responsible developer.
-- Use `jira_add_comment` to include reproduction steps and environment details.
-
-## Example 2: Find and Update Issues
-
-Search for all high-priority unresolved issues assigned to the user. Good agent behavior:
-
-- Use `jira_search_issues` with a JQL query like `assignee = currentUser() AND priority = High AND status != Done`.
-- Use `jira_get_issue` on each result to review full details.
-- Use `jira_update_issue` to transition the status to "In Progress".
-- Use `jira_add_comment` to log what work is being started.
-- Summarize the findings in a structured report grouped by status.
-
-## Example 3: Close a Sprint Task
-
-A task is complete and ready to close. Good agent behavior:
-
-- Use `jira_get_current_user` to verify authentication is working.
-- Use `jira_search_issues` to find the task by key or summary.
-- Use `jira_get_issue` to review current status, assignee, and description.
-- Use `jira_update_issue` to set status to "Done" and add a resolution note.
-- Use `jira_add_comment` to document what was completed and any follow-ups.

package/framework/skills/jira-mcp/references/comments.md

@@ -1,27 +0,0 @@
-# Comments
-
-## Add Comment
-
-```
-add_comment
-  issueKey: "PROJ-123"
-  comment: "Fixed in latest deployment (v2.4.1)"
-```
-
-Adds a text comment to a Jira issue. No support for rich text or attachments via this server.
-
-## Read Comments
-
-```
-get_comments
-  issueKey: "PROJ-123"
-```
-
-Returns all comments on an issue, ordered by creation date (ascending). Each comment includes `body`, `author`, `created`, and `updated` timestamps.
-
-## Limitations
-
-- **No edit/update** — the current Jira MCP server does not provide an edit-comment tool
-- **No delete** — comments cannot be removed via this server
-- **No threading/replies** — comments are flat (Jira Cloud's threading is not exposed via this API)
-- **No rich text** — plain text only; HTML/markdown in bodies may be rendered by Jira's API

package/framework/skills/jira-mcp/references/issues.md

@@ -1,97 +0,0 @@
-# Issue Management
-
-## Create
-
-```
-create_issue
-  projectKey: "PROJ"
-  summary: "Login page returns 500"
-  issueType: "Bug"
-  description: "Steps to reproduce..."
-  priority: "High"
-  labels: ["bug", "critical"]
-  assignee: "john.doe"
-  components: ["frontend"]
-  customfield_10211: "Sprint 1"    # optional custom fields
-```
-
-Always verify project and issue types first:
-
-1. `get_projects` → find project key
-2. `get_issue_types` with `projectKey: "PROJ"` → find valid types
-3. `create_issue` with valid `projectKey` and `issueType`
-
-## Read
-
-```
-get_issue
-  issueKey: "PROJ-123"
-```
-
-Returns full issue details: summary, description, status, priority, assignee, reporter, labels, components, custom fields, timestamps.
-
-## Search (JQL)
-
-```
-search_issues
-  jql: "project = PROJ AND status = Open"
-  maxResults: 50
-```
-
-### Common JQL Patterns
-
-| Purpose | JQL |
-| ------- | --- |
-| My open issues | `assignee = currentUser() AND status != Done` |
-| High priority recent | `priority = High AND created >= -7d` |
-| By status | `status IN (Open, "In Progress", "Reopened")` |
-| By label | `labels = "bug" OR labels = "critical"` |
-| By reporter | `reporter = john.doe AND status NOT IN (Closed, Done)` |
-| Unassigned | `assignee IS NULL AND status NOT IN (Closed, Done, Resolved)` |
-| Sprints (custom field) | `cf[10211] = "Sprint 1"` |
-| Date range | `created >= "2025-01-01" AND created <= "2025-06-01"` |
-| Order by | `project = PROJ ORDER BY priority DESC, created ASC` |
-| Text search | `text ~ "error message"` |
-| Across all projects | `status = Open AND assignee = currentUser()` |
-
-`search_issues` defaults to showing issues across **all projects** the user has access to. Scope to a specific project with `project = KEY`.
-
-## Update
-
-```
-update_issue
-  issueKey: "PROJ-123"
-  summary: "Updated title"
-  description: "New description"
-  priority: "Low"
-  assignee: "jane.doe"
-  labels: ["bug", "resolved"]
-  status: "In Progress"           # transition to new status
-  customfield_10211: "Sprint 2"
-```
-
-### Status Transitions
-
-- Issue workflow statuses depend on the project's configuration
-- Common transitions: `Open → "In Progress" → "In Review" → "Done" | "Closed"`
-- Use `get_issue` to check current status and `update_issue` with `status` to transition
-- Invalid transitions return an error — check the project's available workflow transitions in Jira
-
-## Assign
-
-```
-assign_issue
-  issueKey: "PROJ-123"
-  assignee: "john.doe"
-```
-
-`assign_issue` is a dedicated tool. You can also assign via `update_issue` with `assignee`.
-
-## Delete
-
-```
-delete_issue
-  issueKey: "PROJ-123"
-```
-
-**Warning**: `delete_issue` is destructive — permanently deletes the issue. Cannot be undone.

package/framework/skills/jira-mcp/references/projects.md

@@ -1,39 +0,0 @@
-# Project Management
-
-## List Projects
-
-```
-get_projects
-```
-
-Returns all Jira projects the authenticated user can access. Each entry includes `key`, `name`, `projectTypeKey`, `lead`, and `avatarUrls`.
-
-Use this to discover available `projectKey` values for issue operations.
-
-## Project Details
-
-```
-get_project
-  projectKey: "PROJ"
-```
-
-Returns detailed information: name, key, description, lead, components, versions (releases), project type, and category.
-
-Verify a project exists and inspect its components/versions before creating issues:
-
-1. `get_project` → check components, versions
-2. `get_issue_types` → check valid issue types
-3. `create_issue` with verified data
-
-## Issue Types
-
-```
-get_issue_types
-  projectKey: "PROJ"
-```
-
-Returns available issue types for a project. Each type includes `name`, `id`, `description`, `iconUrl`, and `subtask` flag.
-
-Common types across most projects: `Bug`, `Task`, `Story`, `Epic`, `Sub-task`, `Improvement`, `New Feature`.
-
-Always call this **before** creating an issue to ensure the `issueType` value is valid for the target project.