Show HN: Create Git workflows using Jev

TypeSafe AI's Jev model powers metis-workflow 0.1.0, a Python 3.10+ framework with no runtime dependencies that lets developers define Git workflows as classes with named steps, according to the project's Show HN post. The framework, which imports as metis_workflow and ships a CLI and GitHub Action, includes GitHub and Jev integrations; Jev's check() returns yes/no probabilities for a checklist and evaluate() runs Choice, Noul, and Score questions. Issue triage and PR screening are built entirely on the framework, and the archived metis-triage package now lives under legacy/.

metis-workflow is a small Python framework for workflows powered by TypeSafe AI's Jev model. Define a workflow class, use integrations where needed, and compose named steps. Python 3.10+, no runtime dependencies. | Package | Location | Purpose | |---|---|---| | metis-workflow | Repository root | Framework, CLI, GitHub Action, and integrations | | metis-triage | legacy/metis-triage/ | Archived standalone issue-triage package | The framework imports as metis workflow . Both issue triage and PR screening are examples built entirely with this framework. They do not import the legacy package. The current framework version is 0.1.0 . Guides: Migration https://github.com/Ayush0054/metis/blob/main/docs/migration.md · Custom workflows https://github.com/Ayush0054/metis/blob/main/docs/custom-workflows.md . From this checkout: python -m pip install . After publication, the distribution can be installed with pip install metis-workflow . python from metis workflow import Step, Workflow from metis workflow.integrations import Jev class SupportRouting Workflow : name = "support-routing" def build steps self : return Step "assess", self.assess , Step "route", self.route , def assess self, ctx : jev = ctx.integrations.setdefault "jev", Jev return jev.check ctx.event, { "billing": "Does this ticket concern a payment or invoice?" } def route self, ctx : value = ctx.outputs "assess" "billing" return {"queue": "billing" if value = 0.8 else "support" if value <= 0.2 else "manual-review"} workflow = SupportRouting Export the class as workflow to run it from the CLI. In application code, use SupportRouting .run event={"message": "I was charged twice"} . Workflow owns execution, skips, error handling, and the run report. Define the order in build steps and change behavior by overriding individual methods. Each step's return value is available by name in ctx.outputs . | Context field | Purpose | |---|---| | event | Input for this run | | config | Workflow defaults merged with supplied settings | | integrations | API clients shared by the steps | | state | Internal run data, omitted from the run report | | outputs | Named step results included in the run report | | dry run | Whether write steps should suppress external changes | Override default config and validate config config to define and check settings. Pass overrides to the constructor or .run config={...} . Each run gets fresh state and outputs and a copy of its configuration. Supply clients with SupportRouting integrations={"jev": Jev ... } or .run integrations={...} . Use Step "notify", self.notify, when=lambda ctx: ... for conditional steps. Call ctx.skip "reason" to stop the workflow normally. Errors stop subsequent steps. Write steps must honor ctx.dry run ; return only data suitable for the run report. Override matches event, event name=None to control event dispatch. Workflows run sequentially in one process; scheduling comes from the caller or GitHub Actions. src/metis workflow/integrations/ contains the shared clients: - GitHub repository, token=None, dry run=False reads repository API endpoints, follows paginated lists, and supports explicit writes. - Jev api key=None, model=None supplies typed judgments. check state, criteria returns yes/no probabilities for a checklist. evaluate state, questions runs Choice, Noul, and Score questions together and validates the returned answers. Question and answer shapes follow the TypeSafe API https://docs.typesafe.ai/api . GitHub credentials default to GITHUB TOKEN . Jev credentials default to TYPESAFE API KEY , and the model defaults to TYPESAFE DEFAULT MODEL or jev-latest . The workflow owns thresholds, policies, and actions; integrations own API calls. src/metis workflow/ workflow.py Workflow, Step, and Context runner.py Event dispatch integrations/ github.py GitHub API client jev.py Typed Jev judgments examples/ issue triage.py IssueTriage Workflow issue triage.json Label names and triage thresholds pr screening.py PRScreening Workflow pr screening.json PR criteria and screening policy support routing.py SupportRouting Workflow legacy/metis-triage/ Independent archived package Copy an example and its companion JSON to customize it. Both GitHub examples read defaults from the JSON next to their Python file. They use the same public framework and integrations available to any user workflow. | Example | Steps | Result | |---|---|---| | Issue triage | load → classify → label → reply | Labels issues and requests missing bug details | | PR screening | load → evidence → judge → apply | Screens external contributions and closes clear failures | | Support routing | assess → route | Chooses a support queue and priority | Issue triage classifies new issues as bug, feature, documentation, question, or other. It applies existing labels only after configured confidence and probability thresholds pass. For clear bugs, it posts a fixed template listing missing reproduction, behavior, or environment details. It skips uncertain results, bot-authored or oversized issues, changed text, conflicting category labels, previous Metis replies, and conversations a person has already joined. It does not create labels or close issues. Default label names are bug , enhancement , documentation , and question ; configure names that exist in your repository. PR screening exempts the repository owner and owning organization's members, bots, drafts, and configured author exemptions. It reads the title, body, patches, repository description, and README at the trusted base commit. The default checks are relevance, a concrete useful change, and absence of promotional spam. No linked issue is required; small fixes and documentation improvements count. Passing and uncertain PRs stay open. A criterion probability at or below 0.05 allows closure; all probabilities at least 0.8 count as passing. Missing, binary, or incomplete patches and oversized PRs need manual review. These are initial policy thresholds, not evaluated accuracy guarantees. The workflow rechecks PR state before writing, posts a configured explanation, and closes clear failures. There remains a small race between the final read and GitHub's close request. Reopened PRs are screened again; use an author exemption to exclude a contributor from future screening. metis-workflow run --workflow-file examples/support routing.py --event ticket.json metis-workflow run --workflow-file examples/issue triage.py --event issue-event.json --dry-run metis-workflow run --workflow-file examples/pr screening.py --event pr-event.json --dry-run --event supplies a JSON input object. For a single class file, --config path.json overrides its defaults. A dry run still reads GitHub and calls Jev; the examples suppress writes when dry run is true. Loading a workflow file executes trusted local Python. For several workflows, create a manifest such as .github/metis-workflows.json : { "version": 1, "workflows": {"name": "issue-triage", "file": "../examples/issue triage.py"}, { "name": "pr-screening", "file": "../examples/pr screening.py", "config": {"repository context": "We accept bug fixes, examples, and docs improvements."} } } Entries contain a unique name , a file relative to the manifest, and optional enabled and config fields. Settings override top-level defaults; a criteria object replaces the complete checklist. All workflows use this same file-based registration; the framework has no built-in use cases or legacy adapters. metis-workflow list --manifest .github/metis-workflows.json metis-workflow run --manifest .github/metis-workflows.json --workflow issue-triage --event issue-event.json The dispatcher calls each class's matches method. python -m metis workflow uses the same CLI. Copy the examples, companion JSON files, and manifest into your repository. Add the following workflow on the default branch and configure TYPESAFE API KEY as a repository secret. Pin a published commit containing this framework for reproducible use; main is the development reference. name: Metis workflows on: issues: types: opened pull request target: types: opened, reopened, synchronize, edited, ready for review permissions: contents: read issues: write pull-requests: write concurrency: group: metis-${{ github.repository }}-${{ github.event.issue.number || github.event.pull request.number }} cancel-in-progress: false jobs: run: runs-on: ubuntu-latest timeout-minutes: 5 steps: - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 v4.2.2 with: ref: ${{ github.event.pull request.base.sha || github.sha }} persist-credentials: false - uses: Ayush0054/metis@main with: manifest-path: .github/metis-workflows.json typesafe-api-key: ${{ secrets.TYPESAFE API KEY }} Use workflow to select a name from the manifest. To run one class directly, set workflow-file: examples/issue triage.py and optional config-path instead of manifest-path . dry-run: 'true' asks the workflow to evaluate without writes. The optional github-token and model inputs replace the default GitHub token and Jev model. A write error can leave a partial action; inspect or rerun the job. Only trusted base code and configuration should execute in pull request target . PR head code must never be checked out or run in this privileged job. See GitHub's trigger documentation https://docs.github.com/en/actions/reference/workflows-and-actions/events-that-trigger-workflows pull request target . Issue text, PR text, and patches are sent to TypeSafe for evaluation. legacy/metis-triage https://github.com/Ayush0054/metis/blob/main/legacy/metis-triage/README.md retains the original package at version 0.1.0 , with its own metadata, source, README, and license. It can be installed independently. It has no dependency on the new framework, and the new framework and examples have no dependency on it. New work belongs in metis-workflow and the examples. .github/workflows/publish.yml builds only the root metis-workflow distribution and publishes through PyPI Trusted Publishing. Configure the publisher for project metis-workflow , owner Ayush0054 , repository metis , workflow publish.yml , and environment pypi-workflow . A release tag must match the root package version, currently v0.1.0 . The legacy package has no automated publication in this workflow. The class API draws on Temporal workflow classes https://docs.temporal.io/develop/python/workflows/basics , step composition on Agno workflows https://docs.agno.com/workflows/overview , and explicit execution state on Prefect flows https://docs.prefect.io/v3/concepts/flows . MIT https://github.com/Ayush0054/metis/blob/main/LICENSE © 2026 Ayush Jha.