mpt-extension-skills

Only triage and respond to unresolved PR review comments: decide fix versus answer per comment, apply scoped changes, and reply in the thread. Does not create the PR, commit, or push the branch.

Apply one approved dashboard-failure Jira decision: create, update, reopen, merge, or skip an MPT bug with dashboard evidence fields.

Triage MPT extension dashboard failures from App Insights or CSV: prepare a batch review of findings with proposed Jira actions, then apply approved decisions via the dashboard Jira task.

Only create the work branch when starting work: derive the branch name from the Jira issue and apply the repo naming pattern. Does not change Jira state.

When a task needs a low-level Git branch operation for an already-decided branch name — create or switch safely on the correct base. Used by branch tasks, not for deriving names from Jira.

Run the full start-of-work flow for a Jira issue, leaving a work branch created and the issue in active development. Orchestrates the branch and Jira-start tasks; use for feature, bugfix, hotfix, or backport.

Only move Jira state when starting work: transition the issue and its parent chain to In Progress, ensure active-sprint placement, and check reassignment. Does not create a branch.

Only open or update a repository-compliant pull request to publish committed work, reusing the existing PR instead of duplicating. Does not update docs, run checks, or transition Jira.

Apply dependency-policy fixes to a selected Dependabot PR or checked-out branch: sync dev dependency pins, revert opentelemetry-family bumps, and refresh the dependency lock.

Only update repository docs to match a code change set (docs/*, README.md, AGENTS.md) for unstaged, uncommitted, last-commit, or branch-diff changes. A building block: no self-check or staging.

Run the full re-review iteration on an open PR: process review comments, validate the changes, commit, and update the branch for re-review. Excludes initial PR creation and post-merge Jira steps.

Run the final post-merge step after a PR is merged: verify the merge, then hand off Jira to its correct post-merge status. End-of-flow wrapper; excludes review publication and feedback.

Process open Dependabot PRs end to end: apply the shared dependency policy, validate, and push the fixes back to the same upstream branches for review.

Create or update a reusable shared skill: classify it as tool, task, or workflow, apply shared naming and structure rules, keep it concise, add required metadata, and avoid duplicating standards.

Run the whole send-to-review flow that takes committed work to a review-ready PR and moves Jira to Code Review. Orchestrates the docs, checks, PR, and Jira tasks.

When a task needs low-level GitHub pull-request operations — read, create, update, inspect, comment on, or reply to PRs via the gh CLI. A primitive under PR workflows, not an orchestrator.

When a task needs low-level Jira work-item operations — read, create, edit, comment, assign, search, link, or transition issues (MCP-first, acli fallback). A primitive under Jira workflows.

Fix failures raised by the pre-commit hook during `git commit` (not standalone make/test runs). Reads hook output, fixes one failure at a time, reruns, and retries the commit; max 5 iterations.

Fix failures from a standalone repository validation run (`make check`/`make test`), outside the `git commit` hook. Isolates one blocker at a time, applies the smallest fix, and reruns; max 5 iterations.

Turn a TDR or epic into a backlog of user stories and then Back/Front subtasks with estimates, components, and sprint. Use to break an approved design into work items.

Only transition one issue's Jira status to its correct post-merge state (QA or Done) after merge. Resolves the target from issue and repo context; usually called by the complete-after-merge workflow.

Use when a hotfix or backport must carry an existing main PR onto the active release branch and produce a validated release PR. Orchestrates the cherry-pick, validation, release PR, and Jira updates.

Run the full documentation-update flow before committing or sending to review, leaving affected docs updated, self-checked, and staged. Orchestrates the documentation task end to end.

Run the repository-required local validation flow to verify changes are ready for commit or review. Determines the right checks for the changed scope, runs them in order, and reports failures.

Create a repository-compliant Git commit when saving completed work. Stages only the intended files, builds the message from repo rules, and commits after required validation.

Create the initial epic for a new effort - the epic plus one "Design, investigate and research" user story estimated at 3d. Use at kickoff, before detailed breakdown.

Move a Jira issue to Code Review when development is done and a PR is ready. Verifies PR context, transitions the issue, and reports blockers when the state is not ready.

Author or refresh a repository's required documentation set (README, AGENTS, docs/*) following the shared documentation guideline. Use when docs are missing, incomplete, or need a structural pass.