@mushi-mushi/mcp-ci

The Mushi Mushi GitHub Action. It calls the same API the MCP server uses, from a short CI job: fail a PR while bug reports sit untriaged, have an agent open a fix PR for one report, run the pre-release gates on a commit, or refresh the crawler’s signed-in session.

Quick start

name: Mushi gate
on: [pull_request]
jobs:
  coverage:
    runs-on: ubuntu-latest
    steps:
      - uses: kensaurus/mushi-mushi/packages/mcp-ci@master
        with:
          api-key:      ${{ secrets.MUSHI_API_KEY }}
          project-id:   ${{ secrets.MUSHI_PROJECT_ID }}
          command:      check-coverage
          min-coverage: '0.9'

check-coverage fails the step when fewer than min-coverage (default 0.8) of the project’s reports are classified. Classification runs on its own when a report arrives; trigger-judge does not classify reports.

Gates on every PR

name: Mushi gates
on: [pull_request]
jobs:
  gates:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v5
      # Gates 1 + 2 read your ESLint report (eslint-plugin-mushi-mushi rules).
      - run: npx eslint -f json -o mushi-eslint.json src/ || true
      - uses: kensaurus/mushi-mushi/packages/mcp-ci@master
        with:
          api-key:       ${{ secrets.MUSHI_API_KEY }}
          project-id:    ${{ secrets.MUSHI_PROJECT_ID }}
          command:       gates
          eslint-report: mushi-eslint.json
          commit-sha:    ${{ github.event.pull_request.head.sha }}
          pr-number:     ${{ github.event.pull_request.number }}

Commands

The action fails the step; it does not post a separate GitHub commit status. dead_handler and mock_leak judge the findings in eslint-report (an ESLint JSON report made with eslint-plugin-mushi-mushi). A run that asks for them without a report fails, so a missing lint step can never pass as “no findings”. crawl is not run by this command: start a crawl with Reconcile on the Inventory page; api_contract reads its result. A skipped gate prints its reason.

In your IDE

The same commands are exposed as MCP tools via @mushi-mushi/mcp. Cursor, Claude Code, and Copilot can run them on your behalf when the MCP server is configured. Inside the admin console you can also click Run gates / Run crawler directly on each row of the User stories page; see Admin → User stories · Inventory.

Inputs

action.yml is the source of truth; a test keeps it in step with the CLI.

Outputs

More workflow examples are in the package README .