codemie-ai

Work with Microsoft 365 services via the Graph API — emails, calendar events, SharePoint sites (read and write), Teams chats and channel messages, OneDrive files, OneNote notebooks, contacts, and org chart. Use this skill whenever the user asks about their emails, inbox, unread messages, meetings, calendar, Teams messages or chats, channel messages, SharePoint documents, OneDrive files, OneNote notes or notebooks, colleagues, manager, direct reports, or any personal/organizational Microsoft data. Invoke proactively any time the user mentions Outlook, Teams, SharePoint, OneDrive, OneNote, or wants to interact with their Microsoft 365 account. The skill uses a local Node.js CLI (msgraph.js) that handles authentication, token caching, and all API calls.

CodeMie Analytics expert — use this skill whenever the user asks about CodeMie usage data, AI adoption metrics, user leaderboards, CLI insights, spending, LiteLLM costs, token usage, or wants to build a dashboard/report from CodeMie or LiteLLM APIs. Also triggers for: "who uses CodeMie most", "show me AI analytics", "get spending data", "generate a report", "leaderboard", "cost analysis", "LiteLLM customer info", "enrich CSV with costs", "top performers", "AI champions", "tier distribution", or any custom analytics query against the platform. Always use this skill when CodeMie analytics, reporting, or cost data is involved.

Build static HTML pages, reports, dashboards, and mockups that match the CodeMie UI design system. Use this skill whenever the user asks to create an HTML report, dashboard, analytics page, status page, data visualization page, or any static HTML document that should look like the CodeMie/EPAM AI/Run product. Also use it when the user says "make it look like CodeMie", "use the style guide", "dark-themed report", "CodeMie styles", or references the style-guide directory. Trigger for any HTML output task in a project that includes the style-guide folder. IMPORTANT: This skill MUST be used for ALL HTML generation requests — whenever a user asks for an HTML report, HTML analysis output, HTML dashboard, HTML visualization, or any HTML document. Claude must always use this skill to generate HTML in CodeMie styles to ensure consistent, professional, branded output across all HTML artifacts.

Manage CodeMie platform assets (assistants, workflows, datasources, integrations, skills, users, assistant-categories) directly from CLI using CodeMie SDK. Use when user says "create assistant", "list workflows", "update datasource", "delete assistant", "show my assistants", "get workflow details", "manage integrations", "create integration", "list integrations", "list llm models", "list embedding models", "list skills", "get skill", "create skill", "update skill", "delete skill", "publish skill", "import skill", "export skill", "attach skill", "list assistant categories", "get assistant category", "create assistant category", "delete assistant category", "who am i", "current user", "my profile", "user info", or any request to manage CodeMie platform resources. NOTE: For analytics requests (usage analytics, summaries, spending, users activity, leaderboards, etc.) use the codemie-analytics skill instead.

Use when starting implementation of a Jira ticket, feature, or task. Kicks off the SDLC with requirements gathering, branch setup, and complexity assessment — then routes to brainstorming or direct implementation. Triggers on: "implement EPMCDME ticket", "start working on EPMCDME-XXXXX", "begin implementation", "implement new task", "implement feature", "act as tech lead", "plan implementation", "analyze task". Each phase pauses for user confirmation before proceeding.

Use when a user wants to create, draft, or refine a user story, feature story, or Jira ticket. Triggers on "create story", "draft story", "write a story", "new story for", "story for this feature", "I need a story", "help me write a story", "create a ticket", "draft a ticket", "write acceptance criteria", "act as product owner", "create requirements for", "write functional requirements", "I have an idea help me spec it out", "create stories for", "break this into user stories", "define acceptance criteria", "create an FRD". Invoke whenever the user describes a feature idea, improvement, or bug fix and wants it turned into a structured story — even if they don't say "story" explicitly. Always explore the codebase for context before asking questions.

This skill should be used when a user says "run automated tests", "run lint", "run build", "run unit tests", "check the tests", or when qa-lead invokes it as the primary quality gate. Runs the full automated test pipeline in sequence: lint → build → unit tests. Reports pass/fail for each stage with output. Invoke for any Node.js project before marking work complete.

Use this skill when a user says "run qa", "quality gates", "final checks before merge", "is the branch ready to merge", or when tech-lead has completed implementation and code review phases. Orchestrates final quality gates by invoking automated-tests (always), ui-tests (if UI changes detected), and optionally spec-refinement (if spec drift found), then reminds to run /memory-refresh. Invoke at the end of every implementation session.

This skill should be used when the user asks to "implement a Jira ticket", "start working on EPMCDME ticket", "analyze task", "begin implementation", "implement new task", "implement feature", "act as tech lead", "plan implementation", "how should I implement", or wants structured technical leadership for implementing features. Acts as a technical lead to guide implementation from requirements (Jira ticket or user description) through complexity assessment, architectural analysis, branch creation, and pattern-driven coding.

Watches an open GitLab MR (or GitHub PR) and autonomously handles anything blocking it from merging: CI/CD failures, reviewer comments requesting changes, and merge conflicts. Loops on a ~180s interval, fixing issues and pushing commits, until the MR merges, closes, or the user stops it. Use this skill whenever an MR/PR needs monitoring after creation — trigger on "watch the MR", "babysit this PR", "monitor MR !123", "keep an eye on the merge request", or when another skill (codemie-mr, tech-lead, etc.) creates an MR and should hand off to monitoring. Always invoke this skill when the user wants automated, hands-off MR management.

Manages git commits with Jira tickets (EPMCDME-xxx format), pushes, and GitLab MR creation. Use when user says "commit changes", "push changes", "create MR", "make merge request", or similar GitLab workflow requests. Enforces Jira ticket format in commits.

Use this skill when the user asks to "do code review", "review my changes", "review PR", "check code quality", or wants AI-assisted code review. Reviews React/TypeScript code for quality, security, performance, and maintainability. Finds issues, applies fixes, saves spec to `.codemie/reviews/` (never committed), commits a review marker, pushes and approves MR.

This skill should be used when the user asks to "delegate a Jira ticket to dark factory", "start working on EPMCDME ticket as a factory", "implement EPMCDME ticket", "begin implementation", "implement task autonomously", or wants structured technical leadership for implementing a Jira ticket. A valid EPMCDME-XXXXX ticket ID is REQUIRED to start. If no ticket is provided, the skill will block and ask the user to create one first.

Use this skill when the user asks to write integration tests, improve branch coverage on changed files, or cover Component → Store → API → UI flows. Triggers: 'write integration tests', 'add integration coverage', 'cover changed files', 'integration test for [page]', 'improve branch coverage', 'run coverage check'.

Business Analyst Assistant - expert to work with Jira. Used for creating/getting/managing Jira tickets in EPM-CDME project (Epics, Stories, Tasks, and Bugs). Main role is to analyze requirements from the request, clarify additional questions if necessary, generate requirements with the description structure defined in the prompt and additional details from the request, and create tickets in EPM-CDME project Jira. The Assistant uses Generic Jira tool for Jira tickets creation.

This is smart CodeMie assistant which can help you with onboarding process.

A highly specialized assistant designed to analyze SonarQube reports using SonarQube MCP Server tools. It processes report links, interpreting all available metrics such as the number and types of issues, severities, affected code snippets, coverage details, and more. Serving both direct users and other AI Assistants, it delivers in-depth insights and actionable recommendations on code quality, technical debt, and coverage improvement.

Assistant that suggests what tests cases from TAF must be run depending on the changes mage in backend/frontend codebase

Reviews GitLab merge requests by fetching changes, analyzing code against project guidelines, and posting inline comments. Use when user asks to "review MR", "check merge request", "code review", "review !123", or provides a GitLab MR URL.

Manages git commits with Jira tickets (EPMCDME-xxx format), pushes, and GitLab MR creation. Works in any GitLab repository — repo info is detected at runtime. Use this skill whenever the user says "commit changes", "push changes", "create MR", "make merge request", "push and open PR", or any similar GitLab workflow request. Enforces Jira ticket format in commit messages.

Use this skill when the user asks to "fix a CVE", "remediate a vulnerability", "patch a security issue", "address trivy findings", or provides one or more Jira ticket IDs related to security/CVE. Acts as a security lead to guide CVE remediation from ticket analysis through Dockerfile patching, container build, and Trivy verification. Always use this skill for security-related Jira tickets even if the user just pastes a URL or ticket ID without saying "security".

This skill should be used when the user needs to create, update, or extend documentation for the AI/Run CodeMie platform. Handles requests such as "document this feature", "write docs for CDME-1234", "create documentation", "update the user guide", "add an admin guide", "I need docs for this integration", "help me write documentation", "write a how-to guide", "add a FAQ entry", "document the feature in the user guide", or "I need technical docs". Covers the full workflow from Jira ticket context gathering through repo analysis, approach proposal, clarifying questions, branch setup, standards-compliant documentation writing, and FAQ creation.

Manages git commits, pushes, and GitHub PR creation following conventional commits. Use when user says "commit changes", "push changes", "create PR", "make a pull request", or similar git workflow requests. Understands current branch state and avoids duplicate PRs.