@mohammadhprp/system-prompt 0.12.1 → 0.12.3

package/framework/agents/README.md

@@ -8,7 +8,6 @@ Subagents are focused AI agents that handle specific domains — security audits
 
 | Agent | Purpose | Permissions |
 | --- | --- | --- |
-| [Backend Architect](./backend-architect.md) | Design scalable, secure, and maintainable backend systems — APIs, databases, architecture, security, performance, DevOps. | read, bash, grep, glob, webfetch (no edit/write) |
 | [Researcher](./researcher.md) | Fetch and analyze web content from URLs — external documentation, best practices, API docs, online resources. | read, write, grep, glob, webfetch (no bash, no edit) |
 | [Reviewer](./reviewer.md) | Review code for correctness, maintainability, and best practices with focus on bugs. | read, bash, grep, glob (no edit/write) |
 | [Security Auditor](./security-auditor.md) | Conduct security audits for REST APIs — authentication, authorization, input validation, secrets, data protection, rate limiting. | read, bash, grep, glob, webfetch (no edit/write) |

package/framework/commands/README.md

@@ -14,7 +14,7 @@ Commands define repeatable workflows that agents execute on demand, triggered by
 | [`/pr`](./pr.md) | Create a GitHub PR for the current branch. | pull-requests standard |
 | [`/mr`](./mr.md) | Create a GitLab MR for the current branch. | pull-requests standard |
 | [`/release`](./release.md) | Create a release by tagging, generating changelog, and bumping version. | — |
-| [`/review`](./review.md) | Perform comprehensive code quality review. | code-review skill, naming/testing/security/performance standards |
+| [`/review`](./review.md) | Perform comprehensive code quality review. | naming/testing/security/performance standards |
 | [`/summarize-changes`](./summarize-changes.md) | Summarize uncommitted changes and flag risky patterns. | — |
 
 ## Command Entry Structure

package/framework/commands/mr.md

@@ -33,14 +33,13 @@ Create a merge request for the current branch.
    - Ask: "Shall I create this MR?"
    - Push the changes if user says Yes
 
-6. **Create upon confirmation** - Use `gitlab_create_merge_request`:
-   - `project_id`: `group/repo`
-   - `title`: Prepend "Draft: " to the formatted branch name
-   - `source_branch`: Current branch
-   - `target_branch`: `develop`
-   - `description`: Filled template content
-   - `assignee_ids`: `[1]`
-   - `squash`: `true`
-   - `remove_source_branch`: `true`
+6. **Create upon confirmation** - Use `glab mr create`:
+   - `--source-branch`: Current branch
+   - `--target-branch`: `develop`
+   - `--title`: Prepend "Draft: " to the formatted branch name
+   - `--description`: Filled template content
+   - `--assignee`: `1`
+   - `--squash`
+   - `--remove-source-branch`
 
 7. **Show the resulting URL.**

package/framework/commands/review.md

@@ -9,7 +9,7 @@ Perform comprehensive code quality review.
 
 ## Process
 
-1. **Review conversation and diff** - Read conversation history, run `git diff` for staged/unstaged changes, identify the problem being solved and the behavior being modified. Load [`skills/code-review/SKILL.md`](../skills/code-review/SKILL.md) and related standards: [`references/standards/naming.md`](../references/standards/naming.md), [`references/standards/testing.md`](../references/standards/testing.md), [`references/standards/security.md`](../references/standards/security.md), [`references/standards/performance.md`](../references/standards/performance.md).
+1. **Review conversation and diff** - Read conversation history, run `git diff` for staged/unstaged changes, identify the problem being solved and the behavior being modified. Read related standards: [`references/standards/naming.md`](../references/standards/naming.md), [`references/standards/testing.md`](../references/standards/testing.md), [`references/standards/security.md`](../references/standards/security.md), [`references/standards/performance.md`](../references/standards/performance.md).
 
 2. **Check correctness** - Edge cases, concurrency, error handling, state transitions, backward compatibility. Read contracts and interfaces before implementation.
 

package/framework/mcps/README.md

@@ -10,11 +10,7 @@ This catalog is framework-agnostic: each entry documents what the server does, w
 | --- | --- | --- |
 | [Excalidraw MCP](./excalidraw/README.md) | Stream hand-drawn Excalidraw diagrams with interactive fullscreen editing — architecture diagrams, flowcharts, wireframes. | Any project that benefits from visual diagrams, architecture visualization, or design sketching. |
 | [Figma MCP Go](./figma-mcp-go/README.md) | Full read/write access to Figma designs via plugin bridge — no API token or rate limits. | Any project that works with Figma designs. |
-| [GitLab MCP](./gitlab-mcp/README.md) | Comprehensive GitLab integration — projects, MRs, issues, pipelines, wiki, milestones, and more. | Any project hosted on GitLab (SaaS or self-hosted). |
-| [GitHub MCP](./github-mcp/README.md) | Connect AI tools to GitHub — browse repos, manage issues and PRs, monitor Actions workflows. | Any project hosted on GitHub. |
-| [Jira MCP](./jira-mcp/README.md) | Interact with self-hosted Jira instances — issues, JQL search, comments, assignments, and projects. | Any project using self-hosted Jira for issue tracking. |
 | [Laravel Boost](./laravel-boost/README.md) | Gives AI agents Laravel application context, Laravel ecosystem documentation search, and safe local inspection tools. | Laravel applications. |
-| [Notion MCP](./notion-mcp/README.md) | Search, read, and write content in a Notion workspace — pages, databases, views, comments, and more via remote HTTP MCP. | Any project that uses Notion for documentation, tracking, or collaboration. |
 | [Playwright MCP](./playwright-mcp/README.md) | Cross-browser automation via accessibility snapshots — navigate, click, type, screenshot, evaluate, network control, storage management. | Any project needing browser automation or end-to-end testing. |
 | [Supabase MCP](./supabase-mcp/README.md) | Manage Supabase projects, query databases, design schema, run migrations, deploy Edge Functions, manage Auth/Storage/Realtime, and search docs. | Any project using Supabase as backend. |
 

package/framework/plugins/ponytail/README.md

@@ -39,6 +39,5 @@ Avoid when the task explicitly needs complex scaffolding, heavy abstractions, or
 
 Relevant skills in this repository:
 
-- [`code-review`](../../skills/code-review/SKILL.md): review backend changes for correctness and maintainability, complementary to ponytail's over-engineering focus.
 - [`backend-best-practices`](../../skills/backend-best-practices/SKILL.md): backend best practices for refactoring and behavior-preserving cleanup.
 - [`pr`](../../commands/pr.md): prepare small, reviewable changes aligned with ponytail's minimal-diff philosophy.

package/framework/plugins/ponytail/capabilities.md

@@ -90,7 +90,7 @@ Or in `~/.config/ponytail/config.json` (`%APPDATA%\ponytail\config.json` on Wind
 - Use `/ponytail-review` after a coding session to catch over-engineering the agent missed.
 - Mark intentional shortcuts with `ponytail:` comments naming the ceiling and upgrade path.
 - Review `/ponytail-debt` regularly to track deferred improvements.
-- Pair with `code-review` and the `/pr` command for a complete quality workflow.
+- Pair with the `/pr` command for a complete quality workflow.
 
 ## Common Workflows
 

package/framework/references/standards/api.md

@@ -39,5 +39,4 @@ Define reusable backend engineering rules for API decisions across projects. Thi
 
 ## Related Skills
 
-- `skills/code-review/SKILL.md`
 - `skills/backend-best-practices/references/api-design.md`

package/framework/references/standards/architecture.md

@@ -38,5 +38,4 @@ Define reusable backend engineering rules for architecture decisions across proj
 
 ## Related Skills
 
-- `skills/code-review/SKILL.md`
 - `skills/backend-best-practices/references/architecture-review.md`

package/framework/references/standards/database.md

@@ -38,5 +38,4 @@ Define reusable backend engineering rules for database decisions across projects
 
 ## Related Skills
 
-- `skills/code-review/SKILL.md`
 - `skills/backend-best-practices/references/database-design.md`

package/framework/references/standards/debugging.md

@@ -39,5 +39,4 @@ Define reusable backend engineering rules for debugging decisions across project
 
 ## Related Skills
 
-- `skills/code-review/SKILL.md`
 - `skills/backend-best-practices/references/debugging.md`

package/framework/references/standards/documentation.md

@@ -38,4 +38,3 @@ Define reusable backend engineering rules for documentation decisions across pro
 
 ## Related Skills
 
-- `skills/code-review/SKILL.md`

package/framework/references/standards/logging.md

@@ -38,5 +38,4 @@ Define reusable backend engineering rules for logging decisions across projects.
 
 ## Related Skills
 
-- `skills/code-review/SKILL.md`
 - `skills/backend-best-practices/references/observability.md`

package/framework/references/standards/naming.md

@@ -38,5 +38,4 @@ Define reusable backend engineering rules for naming decisions across projects.
 
 ## Related Skills
 
-- `skills/code-review/SKILL.md`
 - `skills/backend-best-practices/references/refactoring.md`

package/framework/references/standards/observability.md

@@ -38,5 +38,4 @@ Define reusable backend engineering rules for observability decisions across pro
 
 ## Related Skills
 
-- `skills/code-review/SKILL.md`
 - `skills/backend-best-practices/references/observability.md`

package/framework/references/standards/performance.md

@@ -38,5 +38,4 @@ Define reusable backend engineering rules for performance decisions across proje
 
 ## Related Skills
 
-- `skills/code-review/SKILL.md`
 - `skills/backend-best-practices/references/performance.md`

package/framework/references/standards/pull-requests.md

@@ -38,5 +38,4 @@ Define reusable backend engineering rules for pull request decisions across proj
 
 ## Related Skills
 
-- `skills/code-review/SKILL.md`
 - `commands/pr.md`

package/framework/references/standards/security.md

@@ -38,5 +38,4 @@ Define reusable backend engineering rules for security decisions across projects
 
 ## Related Skills
 
-- `skills/code-review/SKILL.md`
 - `skills/backend-best-practices/references/security.md`

package/framework/references/standards/testing.md

@@ -38,5 +38,4 @@ Define reusable backend engineering rules for testing decisions across projects.
 
 ## Related Skills
 
-- `skills/code-review/SKILL.md`
 - `skills/backend-best-practices/references/testing.md`

package/framework/skills/README.md

@@ -10,33 +10,23 @@ This catalog is framework-agnostic: each skill defines when to activate, a step-
 | --- | --- | --- |
 | [agent-browser](./agent-browser/SKILL.md) | Automate browser and Electron workflows for navigation, testing, screenshots, and data extraction. | Website interaction, browser automation, exploratory testing, QA, and Electron desktop app workflows. |
 | [backend-best-practices](./backend-best-practices/SKILL.md) | Consolidated backend engineering practices for API design, architecture, data, security, testing, observability, performance, debugging, and refactoring. | Any backend task that benefits from structured domain guidance across multiple backend disciplines. |
-| [brainstorming](./brainstorming/SKILL.md) | Turn ideas into fully formed designs and specs through collaborative dialogue before any implementation. | Starting a new feature, component, or project; any work that benefits from design before code. |
-| [code-review](./code-review/SKILL.md) | Review backend changes for correctness, readability, maintainability, tests, performance, and security. | Reviewing pull requests, evaluating code quality, or mentoring. |
-| [codenavi](./codenavi/SKILL.md) | Investigate unfamiliar codebases with precision, implement surgically, and keep a `.notebook/` knowledge base that grows across sessions. | Fixing bugs, implementing features, refactoring, or investigating flows in unfamiliar territory. |
-| [create-adr](./create-adr/SKILL.md) | Create Architecture Decision Records (ADRs) that capture the context, decision, and consequences of significant architectural choices. | Documenting a finalized technical decision, or recording why a choice was made for future team members. |
-| [design-like-damien](./design/SKILL.md) | Apply premium, editorial-quality UI design philosophy and Lovable prompting system to produce interfaces that never look “AI-generated.” | Building apps, landing pages, or dashboards in Lovable; UI/UX design for premium SaaS, dark mode, typography, and scroll animations. |
 | [diagram-design](./diagram-design/SKILL.md) | Create technical and product diagrams as standalone HTML files with inline SVG and an opinionated editorial design system. | Architecture, data, process, and other diagrams that communicate more clearly than prose or tables. |
 | [docs-writer](./docs-writer/SKILL.md) | Write, review, and edit documentation files with consistent structure, tone, and technical accuracy. | Creating docs, reviewing markdown files, writing READMEs, or updating `/docs` directories. |
 | [effective-html](./effective-html/SKILL.md) | Create self-contained HTML artifacts with routed guidance for design, wireframes, prototypes, plans, and diagrams. | Standalone HTML reports, explainers, interfaces, wireframes, prototypes, plans, and diagrams. |
 | [find-skills](./find-skills/SKILL.md) | Discover, evaluate, and install skills from the open agent skills ecosystem. | Finding an installable skill for a specialized task or extending an agent's capabilities. |
 | [frontend-design](./frontend-design/SKILL.md) | Distinctive, intentional visual design for new UI or reshaping existing UI — aesthetic direction, typography, and choices that don't read as templated defaults. | Building new interfaces, reshaping existing UI, or escaping generic AI-generated design looks. |
-| [great-interface](./great-interface/SKILL.md) | Build, explain, review, and refine product interfaces across accessibility, layout, writing, typography, color, and UI polish. | Creating frontend interfaces, reviewing interface quality, explaining interface behavior, or comparing UI directions. |
-| [gitlab-mcp](./gitlab-mcp/SKILL.md) | Work with the GitLab MCP server tools for merge requests, issues, repositories, pipelines, and CI/CD workflows. | Any project hosted on GitLab (SaaS or self-hosted). |
+| [glab](./glab/SKILL.md) | Use the GitLab CLI (glab) to manage merge requests, issues, pipelines, and repositories from the command line. | Any project hosted on GitLab (SaaS or self-hosted). |
 | [humanizer](./humanizer/SKILL.md) | Remove signs of AI-generated writing from text — inflated importance, promotional language, em dash overuse, rule of three, AI vocabulary, and filler phrases. | Editing or reviewing prose to make it sound more natural and human-written. |
-| [jira-mcp](./jira-mcp/SKILL.md) | Work with the Jira MCP server tools for issue management, JQL search, comments, and project inspection. | Any project using self-hosted Jira for issue tracking. |
+| [improve](./improve/SKILL.md) | Audit repositories as a read-only senior advisor and produce prioritized implementation plans for another agent. | Repository-wide audits, improvement roadmaps, and implementation handoffs. |
+| [jira-cli](./jira-cli/SKILL.md) | Use the Jira CLI (jira) to manage issues, sprints, epics, comments, transitions, and worklogs from the command line. | Any project using Jira (Cloud or self-hosted) for issue tracking. |
 | [laravel-best-practices](./laravel-best-practices/SKILL.md) | Apply Laravel PHP patterns for Eloquent, validation, security, testing, caching, and architecture. | Writing, reviewing, or refactoring Laravel PHP code. |
-| [learning-opportunities](./learning-opportunities/SKILL.md) | Facilitate deliberate skill development during AI-assisted coding with short, optional interactive exercises. | After architectural work, schema changes, refactors, or when the user asks to understand code better. |
-| [notion-mcp](./notion-mcp/SKILL.md) | Work with the Notion MCP server tools for pages, databases, comments, search, and workspace management. | Any project that uses Notion for documentation, tracking, or collaboration. |
 | [perf-web-optimization](./perf-web-optimization/SKILL.md) | Optimize web performance: bundle size, images, caching, lazy loading, and overall page speed. | A slow site, large bundles, layout shifts, poor Time to Interactive, or low Lighthouse scores. |
 | [security-best-practices](./security-best-practices/SKILL.md) | Perform language- and framework-specific security best-practice reviews and suggest improvements, with support for Python, JavaScript/TypeScript, and Go. | Explicit security reviews or reports, secure-by-default coding, or auditing existing code for major vulnerabilities. |
 | [sentry](./sentry/SKILL.md) | Inspect Sentry issues, summarize production errors, and pull health data via the Sentry API (read-only). | Checking production errors, summarizing recent crashes, or pulling a production error report. |
 | [show-me](./show-me/SKILL.md) | Help the user understand the current topic visually with concise diagrams, code-shape sketches, and focused HTML artifacts. | Explaining logic, control flow, UI structure, file responsibility, or data flow with the smallest useful visual. |
 | [skill-creator](./skill-creator/SKILL.md) | Create new skills, modify and improve existing skills, and measure skill performance. | Designing new skills, optimizing existing skills, or running evals. |
-| [spec-driven-eval](./spec-driven-eval/SKILL.md) | Score how completely an implementation fulfills a PRD/spec, case by case, producing a single comparable final grade. | Benchmarking spec-driven implementations, grading acceptance criteria, or auditing implementation and test coverage against a spec. |
-| [technical-design-doc-creator](./technical-design-doc-creator/SKILL.md) | Create comprehensive Technical Design Documents (TDDs) with mandatory and optional sections through interactive discovery, in the user's language. | Writing a design doc, TDD, technical spec, or architecture document before implementing a significant change. |
 | [tlc-spec-driven](./tlc-spec-driven/SKILL.md) | Feature planning and implementation with adaptive phases, EARS testable requirements, atomic Conventional Commits, and independent verification. | Planning features, implementing with verification and atomic commits, or validating an implementation against a spec. |
 | [taste](./taste/SKILL.md) | Unified design-quality skill spanning anti-slop frontend design, image generation and image-to-code, brand kits, minimalist and industrial UI, redesigns, and Google Stitch design systems. | Landing pages, portfolios, redesigns, website/mobile/brand imagery, or any UI that must not look AI-generated. |
-| [web-design-guidelines](./web-design-guidelines/SKILL.md) | Review UI code for Web Interface Guidelines compliance — accessibility, focus, forms, animation, typography, and interaction patterns. | Reviewing UI, checking accessibility, auditing design or UX, or checking a site against best practices. |
 
 ## How Skills Are Organized
 
@@ -59,7 +49,7 @@ Use the skill table above to find the entry closest to the task at hand. Skills
 Before activating a skill, check:
 
 - **Fit**: does the skill's purpose match the current task?
-- **Scope**: some skills are general (CodeNavi), others are narrow (Laravel Best Practices).
+- **Scope**: some skills are general, others are narrow (Laravel Best Practices).
 - **Combination**: complex tasks may need multiple skills (e.g., API Design + Security + Testing).
 - **Sequence**: some skills are best used in order (e.g., Architecture Review before Database Design).
 

package/framework/skills/glab/SKILL.md

@@ -0,0 +1,222 @@
+---
+name: glab
+description: Expert guidance for using the GitLab CLI (glab) to manage GitLab issues, merge requests, CI/CD pipelines, repositories, and other GitLab operations from the command line. Use this skill when the user needs to interact with GitLab resources or perform GitLab workflows.
+allowed-tools: Bash, Read, Grep, Glob
+---
+
+# GitLab CLI (glab) Skill
+
+Provides guidance for using `glab`, the official GitLab CLI, to perform GitLab operations from the terminal.
+
+## When to Use This Skill
+
+Invoke when the user needs to:
+- Create, review, or manage merge requests
+- Work with GitLab issues
+- Monitor or trigger CI/CD pipelines
+- Clone or manage repositories
+- Perform any GitLab operation from the command line
+
+## Prerequisites
+
+Verify glab installation before executing commands:
+```bash
+glab --version
+```
+
+If not installed, inform the user and provide platform-specific installation guidance.
+
+## Authentication Quick Start
+
+Most glab operations require authentication:
+
+```bash
+# Interactive authentication
+glab auth login
+
+# Check authentication status
+glab auth status
+
+# For self-hosted GitLab
+glab auth login --hostname gitlab.example.org
+
+# Using environment variables
+export GITLAB_TOKEN=your-token
+export GITLAB_HOST=gitlab.example.org  # for self-hosted
+```
+
+## Core Workflows
+
+### Creating a Merge Request
+
+```bash
+# 1. Ensure branch is pushed
+git push -u origin feature-branch
+
+# 2. Create MR
+glab mr create --title "Add feature" --description "Implements X"
+
+# With reviewers and labels
+glab mr create --title "Fix bug" --reviewer=alice,bob --label="bug,urgent"
+```
+
+### Reviewing Merge Requests
+
+```bash
+# 1. List MRs awaiting your review
+glab mr list --reviewer=@me
+
+# 2. Checkout MR locally to test
+glab mr checkout <mr-number>
+
+# 3. After testing, approve
+glab mr approve <mr-number>
+
+# 4. Add review comments
+glab mr note <mr-number> -m "Please update tests"
+```
+
+### Managing Issues
+
+```bash
+# Create issue with labels
+glab issue create --title "Bug in login" --label=bug
+
+# Link MR to issue
+glab mr create --title "Fix login" --description "Closes #<issue-number>"
+
+# List your assigned issues
+glab issue list --assignee=@me
+```
+
+### Monitoring CI/CD
+
+```bash
+# Watch pipeline in progress
+glab pipeline ci view
+
+# Check pipeline status
+glab ci status
+
+# View logs if failed
+glab ci trace
+
+# Retry failed pipeline
+glab ci retry
+
+# Lint CI config before pushing
+glab ci lint
+```
+
+## Common Patterns
+
+### Working Outside Repository Context
+
+When not in a Git repository, specify the repository:
+```bash
+glab mr list -R owner/repo
+glab issue list -R owner/repo
+```
+
+### Self-Hosted GitLab
+
+Set hostname for all commands:
+```bash
+export GITLAB_HOST=gitlab.example.org
+# or per-command
+glab repo clone gitlab.example.org/owner/repo
+```
+
+### Automation and Scripting
+
+Use JSON output for parsing:
+```bash
+glab mr list --output=json | jq '.[] | .title'
+```
+
+### Using the API Command
+
+The `glab api` command provides direct GitLab API access:
+
+```bash
+# Basic API call
+glab api projects/:id/merge_requests
+
+# IMPORTANT: Pagination uses query parameters in URL, NOT flags
+# ❌ WRONG: glab api --per-page=100 projects/:id/jobs
+# ✓ CORRECT: glab api "projects/:id/jobs?per_page=100"
+
+# Auto-fetch all pages
+glab api --paginate "projects/:id/pipelines/123/jobs?per_page=100"
+
+# POST with data
+glab api --method POST projects/:id/issues --field title="Bug" --field description="Details"
+```
+
+## Best Practices
+
+1. **Verify authentication** before executing commands: `glab auth status`
+2. **Use `--help`** to explore command options: `glab <command> --help`
+3. **Link MRs to issues** using "Closes #123" in MR description
+4. **Lint CI config** before pushing: `glab ci lint`
+5. **Check repository context** when commands fail: `git remote -v`
+
+## Common Commands Quick Reference
+
+**Merge Requests:**
+- `glab mr list --assignee=@me` - Your assigned MRs
+- `glab mr list --reviewer=@me` - MRs for you to review
+- `glab mr create` - Create new MR
+- `glab mr checkout <number>` - Test MR locally
+- `glab mr approve <number>` - Approve MR
+- `glab mr merge <number>` - Merge approved MR
+
+**Issues:**
+- `glab issue list` - List all issues
+- `glab issue create` - Create new issue
+- `glab issue close <number>` - Close issue
+
+**CI/CD:**
+- `glab pipeline ci view` - Watch pipeline
+- `glab ci status` - Check status
+- `glab ci lint` - Validate .gitlab-ci.yml
+- `glab ci retry` - Retry failed pipeline
+
+**Repository:**
+- `glab repo clone owner/repo` - Clone repository
+- `glab repo view` - View repo details
+- `glab repo fork` - Fork repository
+
+## Progressive Disclosure
+
+For detailed command documentation, refer to:
+- **references/commands-detailed.md** - Comprehensive command reference with all flags and options
+- **references/quick-reference.md** - Condensed command cheat sheet
+- **references/troubleshooting.md** - Detailed error scenarios and solutions
+
+Load these references when:
+- User needs specific flag or option details
+- Troubleshooting authentication or connection issues
+- Working with advanced features (API, schedules, variables, etc.)
+
+## Common Issues Quick Fixes
+
+**"command not found: glab"** - Install glab or verify PATH
+
+**"401 Unauthorized"** - Run `glab auth login`
+
+**"404 Project Not Found"** - Verify repository name and access permissions
+
+**"not a git repository"** - Navigate to repo or use `-R owner/repo` flag
+
+**"source branch already has a merge request"** - Use `glab mr list` to find existing MR
+
+For detailed troubleshooting, load **references/troubleshooting.md**.
+
+## Notes
+
+- glab auto-detects repository context from Git remote
+- Most commands have `--web` flag to open in browser
+- Use `--output=json` for scripting and automation
+- Multiple GitLab accounts can be authenticated simultaneously
+- Commands respect Git configuration and current repository context