folio-po

Plugin folio-po from marketplace folio-ai-dev in folio-org/folio-eureka-ai-dev. Commands read from the repo's manifest — 4 days ago.

Skills (21)

• build-app-context

  Use when you need to build or refresh a context file for a FOLIO application area before writing test cases. This skill gathers live data from TestRail (existing cases), GitHub (README, docs, feature files, capability/permission definitions), and Jira (closed stories and bugs for the component), the

• code-review

  Use when the user asks to perform a code review, review code changes, analyze a diff, or audit code quality — for committed branch changes or for the current uncommitted working-tree changes before a commit.

• create-backport-tasks

  Use when someone asks to create Jira backport tasks (tickets) for a source ticket and one or more flower patches, for example "backport MODFOO-100 to Trillium CSP#1 and Sunflower CSP#12", "create backport tickets for MODFOO-100", or "plan a patch for MODFOO-100". Works from Jira alone and only creat

• create-release-tasks

  Use when someone asks to create the Jira module release ticket (task) for a module version, with or without backports, for example "create the release for folio-module-foo v4.0.5", "release ticket for folio-keycloak-plugins v26.8.2", "release ticket for MODFOO Trillium CSP#1", or "make release tasks

• document-feature

  Use when the user asks to document an implemented feature, before or after its changes are committed, in the repository's existing documentation structure or under docs/features/ when none exists.

• ecs-user-setup

  Expert guide for setting up users in Enhanced Consortia Support (ECS) tests. Use when generating or reviewing Cypress tests where ecs_enabled is true in TestRail, or when user mentions consortia/ECS/multi-tenant tests.

• fat-creator

  Use when the user asks to create a Jira review task for TestRail test cases — e.g. "create a TC review task for C514952", "make a review ticket for this test case <TestRail link>", "create review tickets for these cases", "one review ticket for all these cases", "TC review task". Creates FAT Tasks f

• implement-automated-test

  Use this skill whenever generating, editing, or reviewing Cypress E2E tests for the FOLIO library management system UI. Triggers include: any mention of 'FOLIO', 'Stripes', 'Cypress test', 'cy.js', 'page object', 'interactor', 'test fragment', or FOLIO module names (Inventory, Orders, Organizations,

• liquibase-migration

  Use when creating, editing, or reviewing Liquibase database migrations in FOLIO Spring Boot modules. Always use this skill for any db migration, schema change, changeset authoring, XML changelog creation, database migration script, or table/column/index/FK changes in a FOLIO module — even if the use

• nightly-failure-report

  Analyze a Jenkins Allure report of a FOLIO stripes-testing (Cypress) run and build an HTML fix list - for every failed test, one concrete fix: a diff in stripes-testing, a fix in the FOLIO module code (with a Jira summary), or the exact data to create or restore on the environment - each marked Read

• review-generated-automated-test

  Use this skill whenever performing a code review of Cypress E2E tests for the FOLIO Stripes framework. Triggers include: any mention of 'code review', 'review my test', 'review git diff', 'PR review', or 'check my Cypress test'. Also use when the user asks to analyze a git diff, validate test struct

• skill-feedback

  Use when a user wants to record feedback about one completed skill session while the session context is still available.

• sprint-quarter-progress

  Generate a professional 1-slide PPTX showing sprint feature progress for any Jira team — tasks grouped by UXPROD/feature filter, with progress bars, % done, and summary stats.

• test-case-updater

  Use when a phrase, term, or wording needs to be replaced across many existing TestRail test cases in a FOLIO module — a renamed UI label, a corrected term, a typo fix. Finds matching cases, previews every change, archives pre-release cases to a target section before editing them, and optionally appe

• testrail-bug-report

  Generate Jira-ready bug reports from failed FOLIO test cases. Takes TestRail test case ID, investigates failure context, and creates structured bug report with Title, Description, Environment, Steps to Reproduce, Expected Result, and Actual Result. Optionally uses Chrome DevTools MCP to investigate

• unit-testing

  Use when writing or reviewing Java unit tests. Enforces Mockito/JUnit 5 best practices - strict stubbing, no lenient mode, specific matchers, complete flow stubbing, Arrange-Act-Assert structure, and clear test naming.

• write-bug

  Use when creating, refining, or triaging a FOLIO bug report, checking whether a defect was reported or fixed before, or preparing a bug for Jira.

• write-karate-first-cases

  Use instead of write-testrail-cases for teams in the Karate-first experiment. Writes TestRail cases API-first — business rules, state changes, validation and permissions as Karate cases; only what cannot be verified via API stays as thin UI (Cypress) cases.

• write-pr-description

  Use when a pull request needs to be written or opened for the current branch — "write a PR description", "create a PR", "draft a pull request", "open a PR for this branch", "generate PR text" — and when an existing PR description needs to be rewritten to team conventions. author: folio-org version:

• write-testrail-cases

  Use when writing, generating, or adding manual test cases to TestRail. Produces structured cases with preconditions, step-by-step actions with expected results, and all required metadata fields. Also use when asked to cover a User Story with test cases, prepare cases for a new feature, or post cases

• write-user-story

  Use when creating or refining a user story, technical enabler, or discovery/policy ticket, defining acceptance criteria, or preparing scoped work for development or a decision.