vikenpatel14
- 11 skills
- 0 followers
- 12 hours ago last updated
- ▌ Install Apk · vikenpatel14Install APK builds to a connected Android device via adb. Scans the local builds folder for RC, Preview, and Feature Branch APKs. Can also fetch build links from Slack release channels. Use when the user wants to install an APK, sideload an app, install a build, push an APK to a device, mentions RC/Preview/feature branch builds, uses shorthand like "26.21 R W" or "26.21 P C", provides a .apk filename, or asks for builds from Slack (e.g. "26.21 slack").
- ▌ Bug Creation · vikenpatel14Create EXAMPLE-PROJ JIRA bugs in the user's exact format. Use when the user says create bug, file bug, log bug, report bug, raise bug, open bug, write bug, new bug, create issue, file issue, log issue, report issue, raise issue, create defect, file defect, log defect, raise a ticket, create a ticket, or any variation of wanting to create a bug or issue in JIRA.
- ▌ Jira Teamwork · vikenpatel14Manage JIRA issues, sprints, and boards using the Atlassian MCP server for QA testing workflows. Use when the user mentions JIRA, tickets, issues, sprints, backlog, board, standup, bugs, testing, QA, regression, defects, or wants to create, update, search, or track work items.
- ▌ Bug Origin Checker · vikenpatel14Determine if a bug found during feature branch testing is pre-existing or introduced by the branch. Analyzes PR code changes and compares against the bug area. Use when the user finds a bug on a feature branch build and wants to know if it was already there or introduced by the branch.
- ▌ Jira Story Context · vikenpatel14Fetch and internalize JIRA story/bug details for context-driven follow-up. Use ONLY when the user mentions a EXAMPLE-PROJ JIRA ticket, story, bug, card, or issue key (e.g., EXAMPLE-PROJ-123), or asks to look at, check, or review a EXAMPLE-PROJ JIRA item.
- ▌ Root Cause Analysis · vikenpatel14Perform root cause analysis for bugs found in RC builds. Guides through build comparison, PR identification, and generates a shareable RCA document. Use when the user mentions root cause analysis, RCA, what caused a bug, why a bug happened, find the root cause, regression analysis, or wants to trace a bug back to its origin.
- ▌ Story Refinement QA · vikenpatel14Fetch unrefined EXAMPLE-PROJ JIRA stories and prepare QA-focused refinement notes. Use when the user mentions refinement, unrefined stories, unpointed stories, refinement prep, sprint refinement, grooming, or wants to prepare for a refinement meeting.
- ▌ Github Auth Recovery · vikenpatel14Automatically recover from GitHub CLI authentication failures. Use when any gh command fails with 401, SAML enforcement, token invalid, or authentication-related errors.
- ▌ Duplicate Bug Checker · vikenpatel14Search JIRA for duplicate bugs and stories before filing a new issue. Searches across all projects, not just EXAMPLE-PROJ. Use when the user describes a bug they found, asks if a bug already exists, mentions duplicate check, or wants to check before filing a bug.
- ▌ Rc Revalidation Cards · vikenpatel14Find JIRA cards the user tested in a given fix version for RC revalidation. Checks changelogs to identify cards where the user made status transitions, uploaded attachments, or assigned themselves. Use when the user mentions RC revalidation, RC cards, recheck cards, what cards did I work on, my RC list, what do I need to revalidate, or any variation of finding their tested cards for a release candidate build.
- ▌ Sprint Confluence Doc · vikenpatel14Generate sprint documentation tables on Confluence pages by pulling JIRA sprint data and formatting with proper JIRA macros. Use when the user mentions sprint doc, sprint documentation, Confluence sprint page, sprint table, or wants to document a sprint on Confluence.