@mohammadhprp/system-prompt 0.12.0 → 0.12.2

package/framework/skills/brand-guidelines/SKILL.md

@@ -1,73 +0,0 @@
----
-name: brand-guidelines
-description: Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
-license: Complete terms in LICENSE.txt
----
-
-# Anthropic Brand Styling
-
-## Overview
-
-To access Anthropic's official brand identity and style resources, use this skill.
-
-**Keywords**: branding, corporate identity, visual identity, post-processing, styling, brand colors, typography, Anthropic brand, visual formatting, visual design
-
-## Brand Guidelines
-
-### Colors
-
-**Main Colors:**
-
-- Dark: `#141413` - Primary text and dark backgrounds
-- Light: `#faf9f5` - Light backgrounds and text on dark
-- Mid Gray: `#b0aea5` - Secondary elements
-- Light Gray: `#e8e6dc` - Subtle backgrounds
-
-**Accent Colors:**
-
-- Orange: `#d97757` - Primary accent
-- Blue: `#6a9bcc` - Secondary accent
-- Green: `#788c5d` - Tertiary accent
-
-### Typography
-
-- **Headings**: Poppins (with Arial fallback)
-- **Body Text**: Lora (with Georgia fallback)
-- **Note**: Fonts should be pre-installed in your environment for best results
-
-## Features
-
-### Smart Font Application
-
-- Applies Poppins font to headings (24pt and larger)
-- Applies Lora font to body text
-- Automatically falls back to Arial/Georgia if custom fonts unavailable
-- Preserves readability across all systems
-
-### Text Styling
-
-- Headings (24pt+): Poppins font
-- Body text: Lora font
-- Smart color selection based on background
-- Preserves text hierarchy and formatting
-
-### Shape and Accent Colors
-
-- Non-text shapes use accent colors
-- Cycles through orange, blue, and green accents
-- Maintains visual interest while staying on-brand
-
-## Technical Details
-
-### Font Management
-
-- Uses system-installed Poppins and Lora fonts when available
-- Provides automatic fallback to Arial (headings) and Georgia (body)
-- No font installation required - works with existing system fonts
-- For best results, pre-install Poppins and Lora fonts in your environment
-
-### Color Application
-
-- Uses RGB color values for precise brand matching
-- Applied via python-pptx's RGBColor class
-- Maintains color fidelity across different systems

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

@@ -1,83 +0,0 @@
----
-name: gitlab-mcp
-description: Use this skill when working with the GitLab MCP server tools for merge requests, issues, repositories, pipelines, work items, webhooks, search, and related GitLab workflows.
----
-
-# gitlab-mcp
-
-GitLab MCP server providing 173 tools: 171 tools across 16 toolsets, plus `execute_graphql` and the always-available `discover_tools` meta-tool.
-
-## Toolsets
-
-| Toolset                   | Default | Enable with                                          |
-|---------------------------|---------|------------------------------------------------------|
-| merge_requests (41 tools) | yes     | -                                                    |
-| issues (23 tools)         | yes     | -                                                    |
-| repositories (7 tools)    | yes     | -                                                    |
-| branches (6 tools)        | yes     | -                                                    |
-| projects (8 tools)        | yes     | -                                                    |
-| labels (5 tools)          | yes     | -                                                    |
-| ci (2 tools)              | yes     | -                                                    |
-| users (5 tools)           | yes     | -                                                    |
-| pipelines (19 tools)      | no      | `USE_PIPELINE=true` or `GITLAB_TOOLSETS=pipelines`   |
-| milestones (9 tools)      | no      | `USE_MILESTONE=true` or `GITLAB_TOOLSETS=milestones` |
-| wiki (10 tools)           | no      | `USE_GITLAB_WIKI=true` or `GITLAB_TOOLSETS=wiki`     |
-| releases (7 tools)        | no      | `GITLAB_TOOLSETS=releases`                           |
-| tags (5 tools)            | no      | `GITLAB_TOOLSETS=tags`                               |
-| workitems (18 tools)      | no      | `GITLAB_TOOLSETS=workitems`                          |
-| webhooks (3 tools)        | no      | `GITLAB_TOOLSETS=webhooks`                           |
-| search (3 tools)          | no      | `GITLAB_TOOLSETS=search`                             |
-
-Enable all: `GITLAB_TOOLSETS=all`. Use `GITLAB_TOOLS` to enable individual tools outside their toolset. `discover_tools` can activate opt-in categories for the current session.
-
-## Key Workflows
-
-### Code Review (see references/code-review.md)
-
-1. `list_merge_request_changed_files` - get file paths only (no diffs)
-2. `get_merge_request_file_diff` - get diffs for 3-5 files per call (batch)
-3. `create_merge_request_thread` or `create_draft_note` - leave review comments
-4. `bulk_publish_draft_notes` - publish all drafts at once
-
-### MR Lifecycle (see references/merge-requests.md)
-
-`create_merge_request` -> review -> `approve_merge_request` -> `merge_merge_request`
-
-### Issue Management (see references/issues.md)
-
-`create_issue` -> `create_issue_link` -> `create_issue_note` -> `update_issue`
-
-### Work Items (see references/work-items.md)
-
-`list_work_items` -> `get_work_item` -> `update_work_item` -> `create_work_item_note`
-
-### Webhooks & Search
-
-- Webhooks: see references/webhooks.md
-- Code search: see references/search.md
-
-### File Operations
-
-- Read: `get_file_contents`, `get_repository_tree`
-- Write: `create_or_update_file` (single file), `push_files` (multiple files in one commit)
-
-## Parameter Hints
-
-- **project_id**: numeric ID or URL-encoded path (`group/subgroup/project`)
-- **MR lookup**: provide `mergeRequestIid` OR `branchName` (not both)
-- **list_issues**: default scope = created by current user. Use `scope: "all"` for all issues
-- **list_merge_requests**: without project_id returns user's MRs across all projects
-- **emoji reactions**: merge request, issue, and work item reaction tools use GitLab emoji names like `thumbsup`, `rocket`, or `eyes`
-- **work items**: status and custom fields require GitLab Premium/Ultimate features
-- **execute_graphql**: escape double quotes in query strings
-
-## Destructive Tools (require caution)
-
-`delete_issue`, `delete_label`, `delete_wiki_page`, `delete_group_wiki_page`, `delete_milestone`, `delete_release`, `delete_tag`, `delete_merge_request_note`, `delete_merge_request_discussion_note`, `delete_draft_note`, `delete_issue_link`, `delete_merge_request_emoji_reaction`, `delete_merge_request_note_emoji_reaction`, `delete_issue_emoji_reaction`, `delete_issue_note_emoji_reaction`, `delete_work_item_emoji_reaction`, `delete_work_item_note_emoji_reaction`, `merge_merge_request`, `push_files`
-
-## Advanced
-
-- **Dynamic discovery**: `discover_tools` lists and activates opt-in toolsets at runtime
-- **GraphQL**: `execute_graphql` for queries not covered by REST tools
-- **Zoekt search**: `search_code`, `search_project_code`, `search_group_code` (requires advanced search enabled)
-- **Work Items**: GraphQL-based alternative to issues (Premium/Ultimate features)

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

@@ -1,31 +0,0 @@
-# GitLab MCP Examples
-
-## Example 1: Review Merge Request Diffs
-
-Review a merge request with multiple file changes. Good agent behavior:
-
-- Use `list_merge_request_changed_files` to get the list of changed files (no diff).
-- Use `get_merge_request_file_diff` with 3-5 files at a time to review diffs in batches.
-- Use `get_merge_request_approval_state` to check who has approved.
-- Use `create_merge_request_thread` to leave inline feedback on specific lines.
-- Use `approve_merge_request` and `merge_merge_request` when the review passes.
-
-## Example 2: Investigate Pipeline Failure
-
-A CI pipeline failed on the main branch. Good agent behavior:
-
-- Use `list_pipelines` to find the latest failed pipeline for the target branch.
-- Use `list_pipeline_jobs` to identify which job failed.
-- Use `get_pipeline_job_output` with pagination to read the failure logs.
-- Use `get_pipeline_job` to inspect the job's environment and timing.
-- Summarize the root cause and propose a fix based on the log output.
-
-## Example 3: Create and Manage an Issue
-
-Track a bug report discovered during development. Good agent behavior:
-
-- Use `create_issue` with project key, summary, description, and labels.
-- Use `create_issue_note` to add reproduction steps as a comment.
-- Use `update_issue` to set assignee and priority.
-- Use `create_branch` to start work from the issue branch naming convention.
-- Use `create_merge_request` when the fix is ready, linking the MR to the issue.

package/framework/skills/gitlab-mcp/references/code-review.md

@@ -1,110 +0,0 @@
-# Code Review Workflow
-
-## Overview
-
-Efficient code review uses a 2-step approach: list files first, then fetch diffs in batches.
-This avoids loading the entire diff payload at once.
-
-## Step 1: List Changed Files
-
-```
-list_merge_request_changed_files
-  project_id: "my-group/my-project"
-  mergeRequestIid: 42
-```
-
-Returns file paths with metadata:
-
-- `new_path`, `old_path` - file locations
-- `new_file`, `deleted_file`, `renamed_file` - change type flags
-
-Use `excluded_file_patterns` to skip generated files:
-
-```
-excluded_file_patterns: ["*.lock", "*.min.js", "dist/**"]
-```
-
-## Step 2: Batch Diff Retrieval
-
-```
-get_merge_request_file_diff
-  project_id: "my-group/my-project"
-  mergeRequestIid: 42
-  file_paths: ["src/api.ts", "src/utils.ts", "src/types.ts"]
-```
-
-**Batch 3-5 files per call** for optimal balance between API calls and response size.
-For large MRs (20+ files), prioritize reviewing:
-
-1. Source code files first (skip configs, lockfiles)
-2. New files before modified files
-3. Core logic before tests
-
-## Step 3: Leave Comments
-
-### Option A: Thread comments (visible immediately)
-
-```
-create_merge_request_thread
-  project_id: "my-group/my-project"
-  mergeRequestIid: 42
-  body: "Consider using a const here"
-  position:
-    new_path: "src/api.ts"
-    new_line: 15
-```
-
-Reply to existing threads:
-
-```
-create_merge_request_discussion_note
-  project_id: "my-group/my-project"
-  mergeRequestIid: 42
-  discussion_id: "abc123"
-  body: "Good point, updated"
-```
-
-### Option B: Draft notes (batch review)
-
-Create drafts, then publish all at once:
-
-```
-create_draft_note -> create_draft_note -> create_draft_note
-  ... repeat for each comment ...
-bulk_publish_draft_notes
-  project_id: "my-group/my-project"
-  mergeRequestIid: 42
-```
-
-This mimics GitHub's "pending review" pattern - all comments appear simultaneously.
-
-## Step 4: Resolve Threads
-
-```
-resolve_merge_request_thread
-  project_id: "my-group/my-project"
-  mergeRequestIid: 42
-  discussion_id: "abc123"
-  resolved: true
-```
-
-## Alternative: Full Diff Methods
-
-For small MRs where batching is unnecessary:
-
-- `get_merge_request_diffs` - all diffs at once (can be large)
-- `list_merge_request_diffs` - paginated diffs
-
-For comparing arbitrary refs:
-
-- `get_branch_diffs` - compare two branches or commits
-- `get_commit_diff` - single commit changes
-
-## Version Comparison
-
-Track review progress across force-pushes:
-
-```
-list_merge_request_versions  ->  get versions list
-get_merge_request_version    ->  get specific version details
-```

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
-```