epam
- 114 skills
- 0 followers
- 16 hours ago last updated
- ▌ Refactoring Audit · epam bundleDeep codebase refactoring audit for AI DIAL Chat. Collects metrics, compares with prior local plans, detects dead-code candidates, and writes or updates refactoring-backend.md, refactoring-frontend.md, and refactoring.md index docs (git-excluded). Use when the user asks for a refactoring plan, tech-debt review, god-module analysis, dead/unused-code analysis, architecture audit, or updated refactoring documents.
- ▌ Responsive Design · epamResponsive (mobile + desktop) layout workflow. Use whenever a UI change must work on both phones and desktops, when implementing Figma frames that have separate mobile and desktop variants, or when reviewing a change for mobile parity.
- ▌ Openspec Sync Specs · epamSync 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.
- ▌ Openspec Apply Change · epamImplement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
- ▌ Openspec Archive Change · epamArchive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
- ▌ Code Review And Quality · epamFive-axis code review before merge, plus responsive-parity and documentation-accuracy gates. Use for quality passes after implementation, before merge, and when asked to review a diff.
- ▌ Security Monitor Triager · epamSkeptical second-opinion review of proactive-security-monitor output. For each OSV advisory it re-verifies version-match and reachability against this repo's actual code, and re-judges the news pass's RELEVANT/TANGENTIAL/IGNORE calls. Emits per-item verdicts (CONFIRMED / OVERSTATED / FALSE_POSITIVE / NEEDS_REVIEW). Use as the triage half of the proactive-security-monitor → security-monitor-triager chain.
- ▌ Proactive Security Monitor · epam bundleProactive supply-chain watch for this repo. Resolves the npm SBOM and batch-queries OSV.dev for freshly-modified advisories (committed fetch.sh), then runs an industry-news pass (CISA KEV, OpenSSF, GitHub Security Lab, Socket, The Hacker News) filtered to this project's stack, and emits both as one findings set for the downstream triager. Use as the daily/scheduled producer half of the proactive-security-monitor → security-monitor-triager chain.
- ▌ Address Current Branch Review · epam bundleRead unresolved GitHub code review threads for the pull request associated with the current branch, classify each comment, and implement and verify required code fixes. Post inline replies only when the user explicitly asks to reply after the changes have been pushed and are visible in the PR.
- ▌ Quickapps Design Review · epamUse when the user asks to review, critique, validate, or approve a design doc under docs/designs/. Appends a Review Notes block; on explicit approval, strips notes and flips Status to Approved.
- ▌ Quickapps Release Notes · epamUse 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` / `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.
- ▌ Tool Call File Parameter Formatting · epamFormats file and URL parameters for tool calls. You must analyze the target tool's parameter names and descriptions to choose the correct format (data URI, base64, text, or URL ref).
- ▌ Quickapps Create Pr · epamUse when the user asks to "create a PR", "open a pull request", "raise a PR", "ship this", or "/quickapps-create-pr" in this repo. Drives the project's end-to-end PR flow — feature branch, conventional-commit title/body, the pre-PR format+lint gate, push, and `gh pr create --base development` with the repo's PR template filled in.
- ▌ Quickapps Code Review · epam bundleUse before creating a PR or claiming a change is ready (or on explicit user invocation). Self-reviews the current diff against the patterns this team's reviewers consistently flag.