epam

@epam source repo

114 skills
0 followers
8 hours ago last updated

▌
Openspec Update Change · epam
Update an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the user wants to revise a change's plan, fold new decisions into it, or reconcile its artifacts after an edit. Never edits code.

0
installs
▌
Openspec Update Change 2 · epam
Update an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the user wants to revise a change's plan, fold new decisions into it, or reconcile its artifacts after an edit. Never edits code.

0
installs
▌
Nx Workspace · epam bundle
Explore and understand Nx workspaces. USE WHEN answering questions about the workspace, projects, or tasks. ALSO USE WHEN an nx command fails or you need to check available targets/configuration before running a task. EXAMPLES: 'What projects are in this workspace?', 'How is project X configured?', 'What depends on library Y?', 'What targets can I run?', 'Cannot find configuration for task', 'debug nx task failure'.

0
installs
▌
Speckit Plan · epam
Execute the implementation planning workflow using the plan template to generate design artifacts.

0
installs
▌
Speckit Tasks · epam
Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.

0
installs
▌
Speckit Analyze · epam
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

0
installs
▌
Speckit Clarify · epam
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

0
installs
▌
Speckit Specify · epam
Create or update the feature specification from a natural language feature description.

0
installs
▌
Speckit Checklist · epam
Generate a custom checklist for the current feature based on user requirements.

0
installs
▌
Speckit Implement · epam
Speckit Implement

0
installs
▌
Speckit Git Commit · epam
Auto-commit changes after a Spec Kit command completes

0
installs
▌
Speckit Git Remote · epam
Detect Git remote URL for GitHub integration

0
installs
▌
Speckit Git Feature · epam
Create a feature branch with sequential or timestamp numbering

0
installs
▌
Speckit Constitution · epam
Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.

0
installs
▌
Speckit Git Validate · epam
Validate current branch follows feature branch naming conventions

0
installs
▌
Speckit Taskstoissues · epam
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.

0
installs
▌
Speckit Git Initialize · epam
Initialize a Git repository with an initial commit

0
installs
▌
Openspec Onboard 2 · epam
Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.

0
installs
▌
Openspec Onboard 3 · epam
Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.

0
installs
▌
Openspec Ff Change 2 · epam
Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.

0
installs
▌
Openspec Ff Change 3 · epam
Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.

0
installs
▌
Openspec Sync Specs 3 · epam
Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.

0
installs
▌
Openspec Verify Change 2 · epam
Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.

0
installs
▌
Openspec Verify Change 3 · epam
Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.

0
installs
▌
Openspec Continue Change 2 · epam
Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.

0
installs
▌
Openspec Continue Change 3 · epam
Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.

0
installs
▌
Monitor CI · epam bundle
Monitor Nx Cloud CI pipeline and handle self-healing fixes. USE WHEN user says "monitor ci", "watch ci", "ci monitor", "watch ci for this branch", "track ci", "check ci status", wants to track CI status, or needs help with self-healing CI fixes. Prefer this skill over native CI provider tools (gh, glab, etc.) for CI monitoring — it integrates with Nx Cloud self-healing which those tools cannot access.

0
installs
▌
Openspec Explore 2 · epam
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.

0
installs
▌
Openspec Propose 2 · epam
Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.

0
installs
▌
Openspec Explore 3 · epam
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.

0
installs
▌
Openspec Propose 3 · epam
Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.

0
installs
▌
Openspec Sync Specs 2 · epam
Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.

0
installs
▌
Openspec Apply Change 2 · epam
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.

0
installs
▌
Openspec Apply Change 3 · epam
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.

0
installs
▌
Openspec Archive Change 2 · epam
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.

0
installs
▌
Openspec Archive Change 3 · epam
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.

0
installs
▌
Create Pr · epam
Create a GitHub pull request with Conventional Commits title and structured description. Use when creating PRs, opening pull requests, or submitting code for review.

0
installs
▌
Review Pr · epam
Review a GitHub pull request with inline comments on specific diff lines. Use when reviewing PRs, analyzing pull request changes, or providing code review feedback.

0
installs
▌
Create Issue · epam
GitHub Issue Creation Skill

0
installs
▌
Gflog · epam
Add or update logging statements using GFLog library. Use when creating new log statements, refactoring existing logging code (JUL/SLF4J), or when you see string concatenation in log statements.

0
installs
▌
Algo Test · epam
Write unit tests for Ember trading algorithms using the algo test framework (BaseAbstractAlgorithmTest). Use when asked to create or modify algo unit tests, add test coverage, or understand how the test framework works.

0
installs
▌
Dfp Audit · epam
Scan the codebase for DFP (Decimal64) misuse — raw Java comparison operators used on DFP-encoded long values instead of Decimal64Utils helper methods. Run periodically to catch regressions.

0
installs
▌
Cr Field · epam
Use when adding a new field to an existing Custom Resource. Guides the full workflow: API types, code generation, CRD examples, client investigation, handler mapping, and tests.

0
installs
▌
Run Tests · epam
Run tests for the edp-keycloak-operator. By default runs unit + integration tests. Use /run-tests e2e for end-to-end tests.

0
installs
▌
Generate Mocks · epam
Use when generating testify mocks for an interface. Ensures the interface is registered in .mockery.yml, runs make mocks, and verifies the output file.

0
installs
▌
Run Golangci Lint · epam
Run golangci-lint linters and fix any linting errors. Use when fixing lint issues or before committing code.

0
installs
▌
Calculator · epam bundle
TODO: # Write a 2-3 sentence description of what this skill does and when the agent should use it. # Cover: what types of calculations it handles, what operations are supported, # and what user requests should trigger this skill (e.g. calculate, compute, evaluate, solve, etc.).

0
installs
▌
Style Guide · epam bundle
TODO: Write when the agent should activate this skill. # Cover: what content types it handles and what user actions trigger it.

0
installs
▌
Ums User Management · epam
TODO: Write a concise description explaining the skill's purpose — managing users in the UMS via CRUD operations, search, web enrichment; and when to activate it

0
installs
▌
Unit Converter · epam bundle
Unit Converter

0
installs
▌
Code Review · epam
Structured CRITICAL→NIT review for diffs or paths; review-only until the user requests code changes.

0
installs
▌
Quality Gates · epam
Run the standard npm lint, test, format, and build checks expected before sharing dial-mind-map-frontend changes.

0
installs
▌
Feature Delivery · epam
End-to-end feature work across Next.js UI, Redux store, tests, and verification commands for this repo.

0
installs
▌
Match Repo Style · epam
Align new edits with neighboring files—imports, Redux epics, Next.js patterns, and Tailwind rules in dial-mind-map-frontend.

0
installs
▌
Mindmap Release Notes · epam
Use when the user asks to enhance, refine, polish, or "look at" the release notes for a tag — a fresh CI-generated pre-release (e.g. `0.13.0-rc.0`) or a stable cut. Reads the auto-generated notes off the GitHub release, tidies inconsistent phrasing and issue references, folds duplicate/hotfix entries, reclassifies misfiled security bumps, builds a `Deployment Changes` section from `README.md`'s Environment Variables table, and saves a draft to `claude/release-notes/`. Never edits GitHub directly.

0
installs
▌
Qql Generator · epam bundle
Use when generating, reviewing, repairing, explaining, or executing TimeBase QQL, including MCP-grounded query answers, and small result sets that can be returned directly. Prefer this over the Python client skill unless the user needs a Python artifact, local file export, large result extraction, or downstream Python post-processing.

0
installs
▌
Timebase Cpp Client · epam bundle
Use when the user explicitly asks for TimeBase C++ client code, for example connecting to TimeBase from C++, reading/writing streams, dxapi library acquisition and CMake/vcxproj setup, or TimeBase C++ client debugging.

0
installs
▌
Timebase Java Client · epam bundle
Use when user explicitly asks for TimeBase Java client code, for example typed stream reads/writes, stream creation, bound QQL execution from Java, client Maven/Gradle setup (Community or Enterprise Edition), or TimeBase Java client debugging.

0
installs
▌
Timebase Csharp Client · epam bundle
Use when the user explicitly asks for TimeBase C# or .NET client code, for example typed stream reads/writes, stream creation, bound QQL execution from C#, Deltix.Timebase package setup, or TimeBase .NET client debugging.

0
installs
▌
Timebase Python Client · epam bundle
Use when the user needs TimeBase Python client code, for example scripts, apps, services, local file export, large result extraction, pandas workflows, visualization prep, or downstream Python computation. Do not use for pure MCP discovery or pure QQL tasks answerable via QQL plus MCP without a Python artifact.

0
installs
▌
Git Commit · epam
Use this skill whenever the user wants to commit, push, or ship changes in a git repository. This skill is intended to run with the developer's configured default Haiku model. Triggers include: "commit changes", "push my changes", "ship it", "commit and push", "create a branch and commit", "make a PR", "open a pull request", "create draft PR", or any variation of committing/pushing work. Always use this skill when the user mentions committing — even casually — as it handles the full cycle: branch → add → commit → push → (optionally) PR, with Conventional Commits format and automatic area detection.

0
installs
▌
Release Notes · epam
Use when the user asks to enhance, refine, polish, or "look at" the release notes for a tag — typically a fresh CI-generated pre-release (e.g. `0.16.1-rc.0`) or a stable cut. Reads the auto-generated notes off the GitHub release, classifies and rewrites each bullet in this project's editorial voice, builds the `Deployment Changes` section from `docs/INFRA-CHANGELOG.md` and `docs/upgrade-plans/`, and saves a draft to `claude/release-notes/`. Never edits GitHub directly.

0
installs
▌
Spec Browser Verify · epam
Verify an OpenSpec change's browser-observable acceptance scenarios against the live local app. Reads the change's delta + affected consolidated specs, builds a VerificationRequest, spawns the spec-verification-gate sub-agent (which drives the Playwright MCP), and reports verdicts back. Additive to the OpenSpec workflow — it reads specs but never modifies opsx artifacts, config, or code, and never makes the "done" call. Use when the user wants to verify a change works in the browser, or to retest specific scenarios after a fix.

0
installs
▌
Dial Admin Reference · epam
Find the one authoritative source for a question about this repo — a capability spec, an archived change's rationale, or an ops doc. Use before answering "what is this supposed to do", "why was it built this way", or any question about env vars, theming, the navigation menu, or a version upgrade.

0
installs
▌
Uui Themes · epam
Helps work with UUI themes including generating theme tokens from Figma, working with skin packages, and connecting external themes. Use when generating theme tokens, working with loveship/electric/promo themes, or connecting external themes.

0
installs
▌
Uui Components · epam
Helps create and modify UUI (EPAM Unified UI) components following established patterns. Use when creating new components, modifying existing components, working with withMods, component props, styling, or component architecture in the UUI library.

0
installs
▌
Uui E2e Testing · epam
Helps create and maintain E2E and screenshot tests for UUI components using Playwright. Use when adding E2E tests, creating screenshot tests, updating preview configurations, or working with Property Explorer previews for testing.

0
installs
▌
Uui Data Sources · epam
Helps work with UUI DataSources (ArrayDataSource, LazyDataSource, AsyncDataSource) powering PickerInput, DataTable, FiltersPanel, and other data-driven components. Use when implementing or fixing features that load, filter, sort, or display lists of data.

0
installs
▌
Uui Unit Testing · epam
Helps write unit tests for UUI components using Jest, jsdom, and @epam/uui-test-utils. Use when writing unit tests for UUI components, updating snapshots, running Jest tests, or working with test utilities.

0
installs
▌
Uui Documentation · epam
Helps update UUI documentation, add doc examples, configure Property Explorer, and manage component API documentation. Use when adding documentation examples, updating Property Explorer configs, generating API references, working with UUI documentation site, or when adding/removing/modifying public props on component interfaces.

0
installs
▌
Uui Pr Contributing · epam
Guides the UUI pull request process including branch naming, pre-PR checklist, changelog updates, and quality requirements. Use when preparing a pull request, writing commit messages, or following UUI PR requirements.

0
installs
▌
Uui Release Workflow · epam
Guides the UUI package release process including stable and beta releases, changelog updates, and handling failed releases. Use when releasing UUI packages, updating changelog, or troubleshooting release issues. For maintainers only.

0
installs
▌
Uui Services Context · epam
Helps work with UUI services layer including ContextProvider, ApiContext, ModalContext, NotificationContext, and useUuiContext. Use when implementing features that need modals, notifications, API calls, error handling, or routing.

0
installs
▌
Uui Github Issue Workflow · epam
Fetches GitHub issues from URLs and creates implementation plans for UUI. Use when the user provides a GitHub issue link (github.com/.../issues/N), asks to plan work from an issue, or implement/fix an issue by URL.

0
installs
▌
Pr Summary · epam
Use when the user wants to generate a pull/merge request (PR/MR) summary for the changes in the current branch

0
installs
▌
Fe API Handoff · epam
Use when the user wants to hand off the current branch's changes to a frontend developer/agent — "summarize changes for the FE", "write FE handoff", "what API changes does the frontend need". Works for a raw POC branch or one or more implemented opsx changes. Diffs the current branch against `development`, and writes a single raw-HTML instruction file (wrapped in one `<important>` block, no styling) to `/tmp/fe-api-handoff/` containing the overall context plus every API contract change (endpoints, request/response DTOs, status codes & errors, enums/constants) the frontend must support. Never makes UI/UX judgments. Chat gets brief highlights + the file path only.

0
installs
▌
Openspec Onboard · epam
Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.

0
installs
▌
Openspec Ff Change · epam
Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.

0
installs
▌
Eval Release Notes · epam
Use when the user asks to enhance, refine, polish, or "look at" the release notes for a tag — typically a fresh CI-generated pre-release (e.g. `0.8.0-rc.1`) or a stable cut. Reads the auto-generated notes off the GitHub release, classifies and rewrites each bullet in this project's editorial voice, builds the `Deployment Changes` section from `README.md` / `docs/configuration.md` / PR bodies, and saves a draft to `claude/release-notes/`. When the target is a stable cut (e.g. `0.8.0`) and its `-rc.*` pre-releases already carry enhanced notes, it assembles the stable draft by merging those rc notes — reusing their approved wording — instead of re-deriving every bullet from the raw stable notes. Never edits GitHub directly.

0
installs
▌
Openspec New Change · epam
Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.

0
installs
▌
Openspec Verify Change · epam
Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.

0
installs
▌
Openspec Review Change · epam
Review an OpenSpec change bundle for quality, consistency, and implementation readiness. Use when the user wants to analyze specs before implementation, find issues across artifacts, or assess readiness for the apply step. Similar to speckit.analyze but with iterative find-and-fix capability. Trigger for phrases like "review the spec", "check the change", "is this ready to implement", "analyze artifacts", "review before implementing".

0
installs
▌
Openspec Continue Change · epam
Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.

0
installs
▌
Openspec Bulk Archive Change · epam
Archive multiple completed changes at once. Use when archiving several parallel changes.

0
installs
▌
Figma · epam
Design-to-code workflow for Figma designs. Use when the user shares a Figma URL or asks to implement a design into the codebase.

0
installs
▌
Dep Scan · epam
Runs Trivy filesystem scan against the repo root and emits structured vulnerability findings (CVE, package, versions) in the SDLC reviewer schema. Use when an agent needs to detect known CVEs in project dependencies for downstream triage or human review.

0
installs
▌
Git Ship · epam bundle
Use this skill whenever the user wants to commit, push, or ship changes in a git repository. Triggers include: "commit changes", "push my changes", "ship it", "commit and push", "create a branch and commit", "make a PR", "open a pull request", "create draft PR", or any variation of committing/pushing work. Always use this skill when the user mentions committing — even casually — as it handles the full cycle: branch → add → commit → push → (optionally) PR, with Conventional Commits format and automatic area detection.

0
installs
▌
Nx Import · epam bundle
Import, merge, or combine repositories into an Nx workspace using nx import. USE WHEN the user asks to adopt Nx across repos, move projects into a monorepo, or bring code/history from another repository.

0
installs
▌
Dial Docs · epam
On-demand index of the AI DIAL Chat design docs in docs/. Use when you need ground-truth on how the app works or is built — overall architecture, technical/product requirements, the authentication subsystem (login, logout, OIDC, session cookies, encrypted session, transparent token refresh, BFF auth flow, SessionGuard), theme customization and color tokens, embedding the chat through the overlay, the Responses API integration, or environment-variable migration. Resolves to the one relevant doc; do not preload all of them.

0
installs
▌
Nx Plugins · epam
Find and add Nx plugins. USE WHEN user wants to discover available plugins, install a new plugin, or add support for a specific framework or technology to the workspace.

0
installs
▌
API Design · epam
Design, review, or change HTTP API contracts for AI DIAL Chat. Use when adding or modifying REST endpoints, request/response DTOs, status codes, pagination, filtering, API versioning, auth requirements, rate limits, cache behavior, OpenAPI/Swagger docs, or frontend server-api clients.

0
installs
▌
Dep Triage · epam
Reviews dependency-scan findings against repo source to mark each as confirmed (real risk) or false_positive (not exploitable in this codebase context). Use after /dep-scan emits CVE findings; reduces reviewer noise before human review.

0
installs
▌
Snyk Triage · epam bundle
Validate Snyk SAST / Code findings against repo evidence; emits per-finding verdicts (CONFIRMED / FALSE_POSITIVE / NEEDS_REVIEW / DUPLICATE / NOT_APPLICABLE). Use when a Snyk or Jira-exported scanner report is provided.

0
installs
▌
Create Ticket · epam bundle
Interactively create OR update GitHub issues (Bug, Feature, Task) for the current repository. Create from a discussion, from an openspec change (current branch or a specific change path), or update an existing issue with new details. Use for "create ticket/issue", "generate issue from spec", "document this feature as a ticket", or "update ticket/issue". Infrastructure changes are Tasks auto-labeled `infra-task`. Asks targeted questions, assigns labels, and runs the gh CLI.

0
installs
▌
Chat Release Notes · epam
Use when the user asks to enhance, refine, polish, or "look at" the release notes for a tag — typically a fresh CI-generated pre-release (e.g. `0.45.0-rc.55`) or a stable cut. Reads the auto-generated notes off the GitHub release, classifies and rewrites each bullet in this project's editorial voice, builds the `Deployment Changes` section from `apps/chat-api`'s config registry / env-var source / PR bodies, and saves a draft to `claude/release-notes/`. Never edits GitHub directly.

0
installs
▌
Snyk Scan Stub · epam
Synthetic Snyk Code SARIF 2.1.0 producer for SDLC chain validation. Emits a fixed, realistically-shaped Snyk Code SARIF report under payload.sarif so a downstream triage agent has deterministic, real-format input. NOT a real scanner — replace with stage-snyk.yml when the real Snyk pipeline lands.

0
installs
▌
Openspec Explore · epam
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.

0
installs
▌
Openspec Propose · epam
Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.

0
installs
▌
Snyk Jira Ingest · epam bundle
Pull REAL Snyk SAST findings from EPAM Jira (Data Center) via the search-export API using a Personal Access Token, and emit them as a stage-output.json artifact for a downstream triage stage. Use when you want the actual Jira-tracked Snyk findings (the same set a human gets by clicking Export on the security filter) rather than a synthetic fixture.

0
installs
▌
Lean Verification · epam
Run build/lint/test/typecheck verification during implementation or before merge while minimizing token spend. Use instead of raw Nx or Vitest commands, especially during an OpenSpec task slice.

0
installs

114 published skills · page 1 of 2