mj-agent-flow-verify

Orchestrates local verification by auto-running read-only checks and confirming side-effecting tests.

1|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/MJ-AgentLab/mj-agent --skill mj-agent-flow-verify-mj-agentlab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mj-agent-flow-verify
Source: https://github.com/MJ-AgentLab/mj-agent/tree/main/.claude/skills/mj-agent-flow-verify
Command: npx skills add https://github.com/MJ-AgentLab/mj-agent --skill mj-agent-flow-verify-mj-agentlab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Running the right set of local checks before a commit is error-prone: developers must remember which lint, type-check, test, and doc-validation commands apply to their changed files, and which commands have side effects requiring confirmation. This Skill automates that orchestration for the mj-agent repository. ## Core Features & Use Cases - Scope Detection: Maps git diff output to change domains (agent, llm, sql, docs, infra, skills) and selects the matching command set. - Two-Level Verification: Auto-runs Level A read-only checks (ruff, mypy, pytest unit/eval, compileall, wikilink and frontmatter checks) and asks for HITL confirmation before Level B side-effecting checks (integration/smoke/contract tests, langgraph dev Studio probe, docker compose lifecycle). - Safety Guardrails: Never runs Level C destructive operations such as docker compose down -v, database writes, or secret changes. - Use Case: After modifying src/mj_agent/tools/sql/guardrail.py, ask for local verification and receive a Verify Report with ruff, mypy, and unit test results plus a confirmation prompt for integration tests. ## Quick Start Ask the assistant to run local verification on my current uncommitted changes before I commit them.

Frequently Asked Questions about mj-agent-flow-verify

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

FAQPage Schema
How do I run local verification before committing changes?▼

Trigger the skill with a request like "verify changes" or "run tests locally". It detects your changed files via git diff, auto-runs read-only checks such as ruff, mypy, and unit tests, then asks before running integration or smoke tests.

What is the difference between Level A and Level B checks?▼

Level A checks are fully read-only and run automatically, including ruff, mypy, pytest unit/eval, compileall, and doc validators. Level B checks have side effects or external dependencies, such as integration tests needing a live database or docker compose up, and require explicit user confirmation first.

Which tests run automatically without confirmation?▼

Read-only commands run automatically: ruff check, mypy on src/mj_agent, pytest tests/unit and tests/eval, python -m compileall, wikilink and frontmatter checks, and docker compose config validation. Anything touching a live database, LLM API, or Docker lifecycle asks first.

Can this skill run destructive commands like docker compose down -v?▼

No. Level C destructive operations such as deleting Docker volumes, writing to the business database, modifying secrets, or production operations are never executed by this skill. They are explicitly listed as skipped in the Verify Report.

When should I skip running local verification?▼

You may skip it for pure documentation typo fixes, single renames, or when you state you verified manually. For those cases only wikilink and frontmatter checks are relevant, and the full verification workflow is unnecessary.