How do I install the Inv Runner skill?

Run npx skillmds@latest add majiayu000/inv-runner in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Inv Runner safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Inv Runner?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Inv Runner free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Inv Runner?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Inv Runner by majiayu000 — Agent Skill

Name: Inv Runner
Rating: 4.666666666666667 (3 reviews)
Author: majiayu000

Inv Runner

Python Invoke task automation for DTX website. This skill should be used when running repo commands, backend tests via Docker, database migrations, updating invoke tasks, Docker operations, or workflow automation. Supports dev/test/prod environments with run, exec, up, down commands. References docs/development/invoke-tasks.md for complete command reference.

majiayu000 Updated Sep 9, 2026 567 repo stars

File contents

Invoke Runner Skill

Python Invoke task automation for the DTX website project.

Documentation References (Single Source of Truth)

For complete command reference, consult these mkdocs files:

Document	Content
`docs/development/invoke-tasks.md`	Complete invoke command reference
`docs/development/backend-quickstart.md`	Backend development quickstart
`docs/development/testing.md`	Testing procedures including worktree verification

Running Invoke Commands

Method 1: PATH Prefix (Recommended for Claude)

When bash hooks block source commands, prepend the venv bin to PATH:

PATH=".venv/bin:$PATH" inv <command>

For worktrees, use the full path:

PATH="/path/to/worktree/.venv/bin:$PATH" /path/to/worktree/.venv/bin/inv <command>

Method 2: Poetry Run

poetry run inv <command>

Method 3: Activate venv

source .venv/bin/activate
inv <command>

Why PATH Matters

Invoke tasks call python manage.py or other Python commands. Without venv bin in PATH:

/bin/bash: line 1: python: command not found

PATH prefix ensures subprocess calls find the correct Python interpreter.

Key Patterns

Run vs Exec

run - One-off command in NEW container (with --rm):

inv test.run --cmd 'python manage.py test app.tests -v 2'

exec - Command in RUNNING container:

inv dev.exec backend 'python manage.py shell'

Environment-Specific Commands

All environments (dev, test, prod) support:

inv <env>.up       # Start
inv <env>.down     # Stop and remove
inv <env>.logs     # Follow logs
inv <env>.run --cmd '<cmd>'  # One-off command

Database Operations

inv db.migrate.all       # Migrations for all environments
inv db.migrate.test      # Test environment only
inv db.populate.all      # Reset and populate test DB

Testing (Docker - Recommended)

Avoid Redis hanging issues by running tests in Docker:

inv test.run --cmd 'python manage.py test app.tests -v 2'

Cypress E2E

inv test.setup           # Full setup
inv test.spec --spec navigation  # Specific spec
inv test.headless        # All tests headless

Worktree Workflow

From worktree root:

cd /path/to/worktree
PATH=".venv/bin:$PATH" inv test.down
PATH=".venv/bin:$PATH" inv test.setup
PATH=".venv/bin:$PATH" inv db.migrate.test
PATH=".venv/bin:$PATH" inv db.populate.all
PATH=".venv/bin:$PATH" inv test.up

Common Issues

Issue	Solution
`python: command not found`	Use PATH prefix method
Redis connection errors	Use Docker: `inv test.run --cmd '...'`
Tests hang on cleanup	Use Docker: `inv test.run --cmd '...'`
Module not found	Ensure correct venv is activated

When Modifying Tasks

Update these files when changing invoke tasks:

docs/development/invoke-tasks.md (primary reference)
docs/development/backend-quickstart.md (if backend-related)

---name: inv-runnerdescription: Python Invoke task automation for DTX website. This skill should be used when running repo commands, backend tests via Docker, database migrations, updating invoke tasks, Docker operations, or workflow automation. Supports dev/test/prod environments with run, exec, up, down commands. References docs/development/invoke-tasks.md for complete command reference.--- # Invoke Runner Skill Python Invoke task automation for the DTX website project. ## Documentation References (Single Source of Truth) For complete command reference, consult these mkdocs files: | Document | Content | |----------|---------| | `docs/development/invoke-tasks.md` | Complete invoke command reference | | `docs/development/backend-quickstart.md` | Backend development quickstart | | `docs/development/testing.md` | Testing procedures including worktree verification | ## Running Invoke Commands ### Method 1: PATH Prefix (Recommended for Claude) When bash hooks block `source` commands, prepend the venv bin to PATH: ```bash PATH=".venv/bin:$PATH" inv <command> ``` For worktrees, use the full path: ```bash PATH="/path/to/worktree/.venv/bin:$PATH" /path/to/worktree/.venv/bin/inv <command> ``` ### Method 2: Poetry Run ```bash poetry run inv <command> ``` ### Method 3: Activate venv ```bash source .venv/bin/activate inv <command> ``` ## Why PATH Matters Invoke tasks call `python manage.py` or other Python commands. Without venv bin in PATH: ``` /bin/bash: line 1: python: command not found ``` PATH prefix ensures subprocess calls find the correct Python interpreter. ## Key Patterns ### Run vs Exec **`run`** - One-off command in NEW container (with --rm): ```bash inv test.run --cmd 'python manage.py test app.tests -v 2' ``` **`exec`** - Command in RUNNING container: ```bash inv dev.exec backend 'python manage.py shell' ``` ### Environment-Specific Commands All environments (dev, test, prod) support: ```bash inv <env>.up # Start inv <env>.down # Stop and remove inv <env>.logs # Follow logs inv <env>.run --cmd '<cmd>' # One-off command ``` ### Database Operations ```bash inv db.migrate.all # Migrations for all environments inv db.migrate.test # Test environment only inv db.populate.all # Reset and populate test DB ``` ### Testing (Docker - Recommended) Avoid Redis hanging issues by running tests in Docker: ```bash inv test.run --cmd 'python manage.py test app.tests -v 2' ``` ### Cypress E2E ```bash inv test.setup # Full setup inv test.spec --spec navigation # Specific spec inv test.headless # All tests headless ``` ## Worktree Workflow From worktree root: ```bash cd /path/to/worktree PATH=".venv/bin:$PATH" inv test.down PATH=".venv/bin:$PATH" inv test.setup PATH=".venv/bin:$PATH" inv db.migrate.test PATH=".venv/bin:$PATH" inv db.populate.all PATH=".venv/bin:$PATH" inv test.up ``` ## Common Issues | Issue | Solution | |-------|----------| | `python: command not found` | Use PATH prefix method | | Redis connection errors | Use Docker: `inv test.run --cmd '...'` | | Tests hang on cleanup | Use Docker: `inv test.run --cmd '...'` | | Module not found | Ensure correct venv is activated | ## When Modifying Tasks Update these files when changing invoke tasks: - `docs/development/invoke-tasks.md` (primary reference) - `docs/development/backend-quickstart.md` (if backend-related)

Frequently asked questions