Profile My skills Saved Collections Edit profile Submit a skill

← all publishers

folio-org

@folio-org source repo

16 published skills

  1. ▌
    Write Bug · folio-org bundle
    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.
    0
    installs
  2. ▌
    Code Review · folio-org bundle
    Use when the user asks to perform a code review, review code changes, analyze a diff, or audit code quality. Runs a structured review of git diff output covering security, correctness, performance, maintainability, and style. Produces a markdown report saved as a .md file named after the current branch.
    0
    installs
  3. ▌
    Fat Creator · folio-org
    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 for manual test case review, with the manual-tc-review and AI labels, the cases' Development Team, that team's current sprint, Relates links to every ticket in the cases' References, and no assignee. Supports one case, one ticket per case, or a single combined ticket for several cases. Does not create, modify, or delete test cases, and does not touch any other Jira ticket.
    0
    installs
  4. ▌
    Unit Testing · folio-org bundle
    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.
    0
    installs
  5. ▌
    Ecs User Setup · folio-org
    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.
    0
    installs
  6. ▌
    Skill Feedback · folio-org bundle
    Use when a user wants to record feedback about one completed skill session while the session context is still available.
    0
    installs
  7. ▌
    Document Feature · folio-org bundle
    Use when the user asks to document an implemented feature. Analyze the diff from the base branch, infer the feature boundary and name, and generate behavioral feature documentation under docs/features/.
    0
    installs
  8. ▌
    Write User Story · folio-org bundle
    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.
    0
    installs
  9. ▌
    Build App Context · folio-org
    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), then distills everything into a structured context .md file and saves it to references/context/. Run this skill once per application area, then use write-testrail-cases normally.
    0
    installs
  10. ▌
    Test Case Updater · folio-org bundle
    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 appends a Jira reference. Also use to set metadata fields — priority, release, test group, automation type — across many cases at once. Works with any FOLIO module (Bulk Edit, Lists, Users, Data Export, and others). Do NOT use for writing new test cases (use write-testrail-cases) or for editing a single known case.
    0
    installs
  11. ▌
    Liquibase Migration · folio-org
    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 user just says "add a column", "create a table", or "write a migration". Enforces FOLIO folder structure (changelog-master → changelog-vX.Y → vX.Y/ files), changeset ID naming convention (JIRA@@scope-action-target), comment tags, and FOLIO-standard column types.
    0
    installs
  12. ▌
    Testrail Bug Report · folio-org
    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 live application behavior.
    0
    installs
  13. ▌
    Write Pr Description · folio-org bundle
    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.
    0
    installs
  14. ▌
    Write Testrail Cases · folio-org bundle
    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 to a TestRail section via API.
    0
    installs
  15. ▌
    Implement Automated Test · folio-org
    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, etc.). Also use when creating test spec files, support fragments, permission assignments, or test data setup/teardown logic. Do NOT use for unit tests, backend API-only tests, non-FOLIO projects, or general Cypress tasks unrelated to the FOLIO Stripes framework.
    0
    installs
  16. ▌
    Review Generated Automated Test · folio-org
    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 structure, check for interactor usage, verify tags/permissions/cleanup hooks, or produce a code review markdown report. Do NOT use for generating new tests from scratch, non-FOLIO projects, or general code review tasks unrelated to Cypress/FOLIO.
    0
    installs