mcpField
S
show-env-status

show-env-status

github.com/terrylicaDevelopment291 installsUpdated today
Repository

About show-env-status

A skill that reports the current repository's mise environment, including installed tools, filtered environment variables, tasks, release readiness, and active configuration files. It organizes tasks by namespace for inspection.

Key features

  1. 01Show mise version and installed tools
  2. 02List non-sensitive environment variables
  3. 03Group tasks by namespace
  4. 04Check release task and config readiness
  5. 05List active mise configuration files

Use cases

  1. 01Inspect tools installed for the current repository
  2. 02Review available tasks by namespace
  3. 03Check release setup before a release

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/terrylica/cc-skills --skill show-env-status

After installing, type/show-env-statusin Claude Code to confirm it loaded.

Bundled filesreferences/evolution-log.md

Details

From the project README

/mise:show-env-status

Show a comprehensive overview of the current repo's mise environment.

Self-Evolving Skill: This skill improves through use. If instructions are wrong, parameters drifted, or a workaround was needed — fix this file immediately, don't defer. Only update for real, reproducible issues.

Output Sections

Run these commands and present the results in a formatted summary:

1. mise Version
mise --version
2. Installed Tools
mise ls --current 2>/dev/null
3. Environment Variables (Non-Sensitive)
# Show env vars, filtering out secrets
mise env 2>/dev/null | grep -v -i "TOKEN\|KEY\|SECRET\|PASSWORD\|CREDENTIAL" | sort
4. Available Tasks (Grouped)
mise tasks ls 2>/dev/null

Group the output by colon-namespace prefix (e.g., release:, test:, cache:).

5. Release Readiness

Check if the repo has release tasks configured:

# Check for release:full task
mise tasks ls 2>/dev/null | grep -q "release:full" && echo "✓ Release tasks configured" || echo "✗ No release tasks — run /mise:run-full-release to scaffold"

# Check for semantic-release config (any cosmiconfig-discovered form)
ls release.config.cjs release.config.js .releaserc.yml .releaserc.json .releaserc 2>/dev/null && echo "✓ semantic-release configured" || echo "✗ No semantic-release config"

# Check GH_ACCOUNT
echo "GH_ACCOUNT: ${GH_ACCOUNT:-not set}"
6. Configuration Files
# Show which mise config files are active
ls .mise.toml mise.toml tasks/ 2>/dev/null

Example Output Format

═══════════════════════════════════════════
  mise Environment Status: cc-skills
═══════════════════════════════════════════

Tools: node 25.0.0, bun 1.3.0, python 3.14
Account: terrylica

Tasks (32 total):
  release: full, dry, status, preflight, version, sync, verify, clean, hooks
  dev: lint, format, test

Release: ✓ Configured (release:full + release.config.cjs)
Config: .mise.toml (42 lines)
═══════════════════════════════════════════

Post-Execution Reflection

After this skill completes, check before closing:

  1. Did the command succeed? — If not, fix the instruction or error table that caused the failure.
  2. Did parameters or output change? — If the underlying tool's interface drifted, update Usage examples and Parameters table to match.
  3. Was a workaround needed? — If you had to improvise (different flags, extra steps), update this SKILL.md so the next invocation doesn't need the same workaround.

Only update if the issue is real and reproducible — not speculative.

Comments

Markdown supported