softwareone-platform

@softwareone-platform source repo

47 skills
0 followers
17 hours ago last updated

▌
Open Pr · softwareone-platform bundle
Open a pull request (Azure DevOps or GitHub) for the current branch, giving it a title and description that follow the CALLER's own conventions — learned at runtime from their past merged PRs — with a ticket link and a description of what changed and why. Use whenever someone wants to open / raise / put up a PR, finish a branch, or send changes for review on Azure DevOps or GitHub, even if they don't say "open-pr". It always shows the title and description for confirmation first and never creates the PR without explicit approval. Trigger phrases: "open a PR", "raise a PR", "create a pull request", "put this up for review", "PR this branch", "backport this to a release line", "open-pr", "/open-pr". Do NOT trigger for: reviewing or summarizing an existing PR; triaging or replying to PR comments (that is a separate resolve-pr-comments skill); completing / merging a PR; starting a branch; or plain git operations.

0
installs
▌
Add Unit Test · softwareone-platform bundle
Generate unit tests for changed source files or a user-specified target (class, method, file, directory). Trigger phrases: "add unit tests for X", "write tests for X.cs", "create unit test for ComponentY.MethodZ". Do NOT trigger for: discussions about why a test failed, TDD philosophy, test runner configuration, mocking framework comparisons.

0
installs
▌
Scan Test Gaps · softwareone-platform bundle
Scan pending changes (or a given scope) for untested areas and stale tests, prioritise gaps, and iteratively delegate test generation/updates. Trigger phrases: "find test gaps", "which classes lack tests", "scan for untested code", "check coverage holes". Do NOT trigger for: questions about why a specific test failed, coverage tool configuration, or general TDD discussions.

0
installs
▌
Update Unit Test · softwareone-platform bundle
Audit and update unit tests for changed source signatures or a user-specified target. Two-phase: audit first, then execute automatically (no confirmation gate — actions derive from audit status; git is the rollback). Trigger phrases: "update unit tests for X", "the test for X is stale", "refresh unit tests". Do NOT trigger for: questions about how to write a unit test, refactoring discussions, or general test maintenance topics.

0
installs
▌
Resolve Pr Comments · softwareone-platform bundle
Resolve the review comments on an existing Azure DevOps or GitHub pull request: fetch the PR's comment threads, triage each one, draft the code fixes and replies, and — after a single human confirmation — commit, push, reply, and update thread status. Use whenever someone wants to address, resolve, handle, action, or reply to PR comments or review feedback, fix the comments on a PR, or "go through the comments on PR <id>", even if they don't say "resolve-pr-comments". It respects the reviewer — it triages and drafts, and never auto-dismisses a comment — and it makes no outward change without explicit confirmation. It acts on the comments; it does not merely summarize them. Do NOT trigger for: opening or creating a PR (that is open-pr); summarizing or reviewing a PR's diff; reviewing a plan or code risk; or merging / completing a PR. Trigger phrases: "resolve PR comments", "address the review comments", "fix the comments on PR 12345", "handle the PR feedback", "/resolve-pr-comments".

0
installs
▌
Review Code Risk · softwareone-platform bundle
Adversarially review an IMPLEMENTED FIX — a committed diff on a branch — against the issue it claims to resolve and the plan it was built from, BEFORE the PR is opened. Its question is intent alignment: does THIS change resolve THAT issue, per THAT plan, without regressing callers or hiding a band-aid. Use whenever someone has an implemented fix and wants it challenged before opening a PR. Trigger phrases: "challenge this fix / diff", "will this change regress anything", "red-team this implementation", "pre-mortem this diff", "review my fix before the PR", "/review-code-risk". Do NOT trigger for: reviewing a plan / spec / RFC before implementation (review-plan-risk); generic line-level bug-hunting or style / simplification cleanup (code-review / coderabbit); security-vulnerability scanning (security-review); debugging a failing test; addressing PR reviewer comments; refactoring; or confirmatory "is this correct?" checks that want validation, not adversarial enumeration.

0
installs
▌
Review Plan Risk · softwareone-platform bundle
Adversarially review a DESIGN ARTIFACT — a plan, spec, RFC, or a skill / agent / workflow definition — for design risks BEFORE implementation begins. It rates risks, verifies the plan's load-bearing premises against the codebase, and auto-fixes the ones it rates real — in the plan, never its execution. Use whenever someone wants a design pressure-tested or a definition checked for gaps. Trigger phrases: "pre-mortem this", "stress-test this design", "what could make this fail", "find the holes in this plan", "review this spec before we build", "review this skill's design", "propagate this fix to the plugin's other skills", "/review-plan-risk". Do NOT trigger for: reviewing code or diffs, debugging an existing implementation, post-implementation code review, propagating a code change across source files (refactoring, not design review), or confirmatory "is this correct?" checks that want validation rather than adversarial enumeration.

0
installs
▌
Setup Test Context · softwareone-platform bundle
Analyse the current repo and cache its test profile as one or two convention files under `.claude/conventions/tests/`, so the plugin's other skills skip re-deriving it every run. Optional: every test skill works without it. Works for any language with a detectable test framework (C#, Python, TypeScript, Go, Java, etc.) — auto-detects language and derives every convention from the repo's own tests, never a language baseline. Re-running is the refresh: it re-analyses and rewrites every file it manages. Trigger phrases: "setup test context", "initialise test conventions", "set up the test plugin", "set up tests for my Python repo", "scaffold test conventions for a TypeScript project", "cache the test conventions for this repo", "refresh the generated test conventions".

0
installs
▌
Review Issue Fact · softwareone-platform bundle
Fact-check an ISSUE — a bug report, story, or incident description, as text or a Jira / GitHub issue link — against the codebase that is its ground truth, BEFORE any fix is planned. The issue is not a source of truth, so the question is diagnosis alignment: do its claims hold in THIS code, or is the bug misdiagnosed. Use whenever someone wants an issue or repro fact-checked before planning a fix. Trigger phrases: "fact-check this issue", "does this issue reproduce", "is the root cause right", "is this issue real / misdiagnosed", "/review-issue-fact". Do NOT trigger for: reviewing a plan / spec / RFC before implementation (review-plan-risk); reviewing an implemented fix / diff (review-code-risk); creating, editing, or transitioning a tracker issue; generic line-level bug-hunting (code-review / coderabbit) or security scanning (security-review); debugging a failing test; or confirmatory "is my understanding correct?" checks that want validation, not adversarial fact-checking.

0
installs
▌
Resolve Issue · softwareone-platform bundle
Orchestrate the whole issue-to-PR pipeline for one ticket: fact-check the issue, draft a plan, harden it, implement the fix, write tests, review the fix, and open the PR — behind a plan-approval gate, pausing again wherever a decision is yours. Use whenever someone wants an issue / bug / Jira ticket taken from diagnosis all the way to a pull request, even if they don't name the skill. Resumable across sessions. Do NOT trigger when the user wants only ONE stage — route those to the component skill directly: "just fact-check this issue" is review-issue-fact; "review this plan" is review-plan-risk; "review my fix / diff before the PR" is review-code-risk; "add tests" is test-authoring; "open / raise a PR" is open-pr; "address / resolve the PR comments" is resolve-pr-comments. Also do NOT trigger for merging / completing a PR, or plain git operations. Trigger phrases: "resolve this issue", "run the issue-to-PR pipeline", "take this Jira from diagnosis to PR", "/resolve-issue".

0
installs
▌
Add Integration Test · softwareone-platform bundle
Generate integration tests for changed source files or a user-specified target (endpoint, handler, command, service). Trigger phrases: "add integration tests for X", "create endpoint test for /foo", "write integration test for HandlerY". Do NOT trigger for: discussions about test infrastructure, container setup questions, or end-to-end test strategy.

0
installs
▌
Update Integration Test · softwareone-platform bundle
Audit and update integration tests for changed handlers/endpoints. Two-phase: audit first, then execute automatically (no confirmation gate — actions derive from audit status; git is the rollback). Trigger phrases: "update integration tests for X", "refresh endpoint test for /foo". Do NOT trigger for: integration test infrastructure questions, container/fixture refactoring, or test strategy discussions.

0
installs
▌
Resolve Issue Dashboard · softwareone-platform bundle
Open a live, read-only dashboard that visualises resolve-issue runs across all your repos — each run's pipeline step, what each component skill and subagent is doing, the running metrics, and the gate it is paused at — by tailing the Claude Code transcripts and each repo's .claude/resolve/<ticket>/state.md. One global dashboard lists every run in a left panel; pick one to watch. Use whenever someone wants to see / watch / visualise the progress of an issue-to-PR run, says "open the pipeline dashboard", "show resolve progress", "watch the resolve-issue run", "visualise what the agents are doing", or "/resolve-issue-dashboard". Do NOT trigger to RUN the pipeline — that is resolve-issue — nor for any single stage (route those to the component skill: review-issue-fact, review-plan-risk, review-code-risk, test-authoring, open-pr, resolve-pr-comments). This skill only observes; it never drives the pipeline, answers a gate, or edits anything.

0
installs
▌
Resolve Issue Learnings · softwareone-platform bundle
Harvest the generic, cross-repo learnings that resolve-issue captured during its runs and turn the real ones into honored conventions — verifying each candidate against the current resolve-issue skill as ground truth, then writing the survivors to a user-global conventions file that resolve-issue reads on its next run, or proposing them as edits to its own SKILL.md when invoked inside the editable plugin source. Use whenever someone wants to distil / harvest / review / apply the learnings resolve-issue has accumulated. Do NOT trigger to RUN the issue-to-PR pipeline (that is resolve-issue) or to watch a run (resolve-issue-dashboard); this skill neither drives a run nor reads a single run's state.md — it processes the accumulated learning store. Trigger phrases: "harvest resolve-issue learnings", "distil the resolve-issue runs", "update my resolve-issue conventions", "apply what resolve-issue learned", "/resolve-issue-learnings".

0
installs
▌
Mpt Ext Tool Gh Pr Ops · softwareone-platform bundle
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.

0
installs
▌
Mpt Ext Task Commit Changes · softwareone-platform bundle
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.

0
installs
▌
Mpt Ext Tool Git Branch Ops · softwareone-platform bundle
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.

0
installs
▌
Mpt Ext Workflow Start Work · softwareone-platform bundle
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.

0
installs
▌
Mpt Ext Task Move Jira To QA · softwareone-platform bundle
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.

0
installs
▌
Mpt Ext Task Start Jira Work · softwareone-platform bundle
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.

0
installs
▌
Mpt Ext Task Open Pull Request · softwareone-platform bundle
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.

0
installs
▌
Mpt Ext Tool Jira Workitem Ops · softwareone-platform bundle
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.

0
installs
▌
Mpt Ext Workflow Decompose Tdr · softwareone-platform bundle
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.

0
installs
▌
Mpt Ext Task Create Work Branch · softwareone-platform bundle
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.

0
installs
▌
Mpt Ext Task Handle Pr Comments · softwareone-platform bundle
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.

0
installs
▌
Mpt Ext Tool Teams Send Message · softwareone-platform bundle
When a task needs to post a message into a Microsoft Teams chat through an incoming "workflow webhook" URL, with an adaptive card or plain text. A primitive under notification workflows, not an orchestrator.

0
installs
▌
Mpt Ext Workflow Send To Review · softwareone-platform bundle
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.

0
installs
▌
Mpt Ext Task Create Initial Epic · softwareone-platform bundle
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.

0
installs
▌
Mpt Ext Task Write Documentation · softwareone-platform bundle
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.

0
installs
▌
Mpt Ext Workflow Hotfix Backport · softwareone-platform bundle
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.

0
installs
▌
Mpt Ext Workflow Notify Pr Ready · softwareone-platform bundle
Run the on-demand flow that notifies a Microsoft Teams chat when a reviewed PR is green — all checks pass and CodeRabbit approved. Evaluates once and stops; it does not wait for review.

0
installs
▌
Mpt Ext Workflow Skill Authoring · softwareone-platform bundle
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.

0
installs
▌
Mpt Ext Task Ensure Active Sprint · softwareone-platform bundle
Only place a Jira issue in its board's active sprint: classify the Sprint field and, when absent, resolve and apply placement (on the direct parent for subtasks).

0
installs
▌
Mpt Ext Task Run Repository Checks · softwareone-platform bundle
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.

0
installs
▌
Mpt Ext Task Write Python Unittests · softwareone-platform bundle
Author or update Python (backend) unit tests for a change set to conform to the shared Python unit-testing standard. Use when backend code needs tests or existing tests break the standard.

0
installs
▌
Mpt Ext Workflow Fix Dependabot Prs · softwareone-platform bundle
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.

0
installs
▌
Mpt Ext Task Fix Pre Commit Failures · softwareone-platform bundle
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.

0
installs
▌
Mpt Ext Task Dependabot Pr Policy Fix · softwareone-platform bundle
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.

0
installs
▌
Mpt Ext Task Move Jira To Code Review · softwareone-platform bundle
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.

0
installs
▌
Mpt Ext Task Notify Pr Ready In Teams · softwareone-platform bundle
When a reviewed PR is green — all checks pass and CodeRabbit approved — post its details to a Microsoft Teams chat. Evaluates the gate once; it does not wait or poll.

0
installs
▌
Mpt Ext Task Update Docs From Changes · softwareone-platform bundle
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.

0
installs
▌
Mpt Ext Workflow Complete After Merge · softwareone-platform bundle
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.

0
installs
▌
Mpt Ext Workflow Update Documentation · softwareone-platform bundle
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.

0
installs
▌
Mpt Ext Workflow Address Review Feedback · softwareone-platform bundle
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.

0
installs
▌
Mpt Ext Workflow Dashboard Failure Triage · softwareone-platform bundle
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.

0
installs
▌
Mpt Ext Task Apply Dashboard Jira Decision · softwareone-platform bundle
Apply one approved dashboard-failure Jira decision: create, update, reopen, merge, or skip an MPT bug with dashboard evidence fields.

0
installs
▌
Mpt Ext Task Fix Repository Check Failures · softwareone-platform bundle
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.

0
installs

47 published skills