mise-contrib-overview

Document the jdx/mise codebase layout and build, test, and lint workflows.

1|1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/ray-manaloto/claude-code-marketplace --skill mise-contrib-overview
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mise-contrib-overview
Source: https://github.com/ray-manaloto/claude-code-marketplace/tree/main/mise-toolkit/skills/mise-contrib-overview
Command: npx skills add https://github.com/ray-manaloto/claude-code-marketplace --skill mise-contrib-overview

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orientation helps new and existing contributors understand the jdx/mise codebase layout, standard workflows, and required conventions so they can contribute efficiently and safely.

Core Features & Use Cases

  • Understand repository structure (mise-toolkit, plugins, tasks, and configuration files) and where to find build, test, lint commands.
  • Follow enforced conventions: conventional commits, hk pre-commit setup, and the rule that end-to-end tests must run via mise run test:e2e.
  • Quickly onboard to common contributor tasks such as creating issues, contributing code, and submitting changes that align with project standards.

Quick Start

Refer to this guide whenever you work in the jdx/mise repository to align with the repo layout, commands, and conventions in your workflow.

Frequently Asked Questions about mise-contrib-overview

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I contribute to the mise codebase and understand its repository layout?

Contributing to the mise codebase requires understanding the mise-toolkit structure, plugins, and configuration files. The project mandates specific build, test, and lint workflows defined in mise.toml and tasks.toml to ensure changes align with project standards.

What conventions are enforced for pre-commit setup and conventional commits in mise?

The mise project enforces conventional commit standards and uses the hk pre-commit setup. Contributors must follow these mandated tooling configurations to ensure code submissions pass automated linting and maintain consistent repository history.

How do I run end-to-end tests for the mise project?

End-to-end tests in the mise project must be run via the command mise run test:e2e. This rule ensures all e2e tests execute consistently within the mandated tooling environment defined by mise.toml.

Where can I find the build, test, and lint commands for contributing to mise?

Build, test, and lint commands for the mise repository are documented within the mise.toml and tasks.toml configuration files. These mandated tooling files define the standard workflows contributors must use.

Do I need mise installed locally to contribute to the jdx/mise repository?

Contributing to the jdx/mise repository requires understanding its mandated tooling, which relies on mise.toml and tasks.toml. A local mise installation is necessary to execute the standard build, test, lint, and e2e workflows.

What is the standard workflow for submitting code changes to the mise project?

The standard workflow for submitting changes to the mise project involves following conventional commits, passing the hk pre-commit setup, and running e2e tests via mise run test:e2e to ensure all contributions align with repository standards.