jmo-development-tools

This directory contains custom slash commands for Claude Code. Slash commands let you create reusable prompts that can be invoked with `/command-name`.

Restructure project documentation for clarity and accessibility

Use jj (not git) to look at all the commits from main onwards, see their diffs, and give the commit a good description. Use conventional commit convention. A workflow like the following:

Analyze all active juggler balls and create a comprehensive execution plan

Optimize documentation for conciseness and clarity by strengthening vague instructions and removing redundancy

Stage all changes, create commit, and push to remote (use with caution)

Implement pre-commit hooks and GitHub Actions for quality assurance

Add or remove MCP servers to the current project's .mcp.json

Assess the current repo and recommend which plugins to enable at the project level

splits up the plan to execute with subagents

Increase test coverage by targeting untested branches and edge cases

This directory contains custom agent definitions for Claude Code. Agents are specialized sub-agents with specific expertise and behaviors.

Reviews code changes for quality, best practices, security issues, and potential improvements. Use after completing coding tasks or when todos are finished.

Maintains documentation quality, consistency, and organization. Use when creating, updating, or auditing documentation files.

Use this agent for source control tasks including jj (Jujutsu) operations, Docker/container registry management, image tagging and publishing to Gitea, git remote operations, and version control workflows. This agent works with ALREADY-BUILT images - the main Claude handles building. Examples: <example>Context: Docker image is already built and needs to be pushed to registry. user: 'Tag and push the audioseek image to my Gitea registry' assistant: 'I'll use the source-control-expert agent to tag and push the already-built image to your Gitea container registry' <commentary>The image is already built, so use source-control-expert to handle tagging and pushing to the Gitea registry.</commentary></example> <example>Context: User needs to work with jj commits. user: 'Create a good commit message for my changes' assistant: 'Let me use the source-control-expert agent to analyze your changes and create a proper conventional commit message' <commentary>This involves jj operations which the source-control-expert specializes in.</commentary></example>

Consolidate multiple PR branches onto a target branch using jj multi-parent rebase with intelligent AI-powered conflict resolution

Use when managing project dependencies with Devbox. Devbox is the preferred dependency manager for new projects - covers package installation, environment variables, and shell configuration.

Use when checking Docker image versions or working with container registries. Skopeo is the required tool for registry queries - never parse Docker Hub web pages.

Use when working with Elm projects. Requires running elm-test and elm-review for quality assurance.

Use when finishing a task that changed code, config, scripts, prompts, or documentation. Runs the final build/test/lint/review loop, fixes reasonable issues, and reports remaining findings or skipped checks before the final answer.

Use when working with version control. jj (Jujutsu) is the preferred VCS - never use git commands directly when jj can do the job. Covers mental model, workflows, and Nix integration.

Use when working with NixOS configurations, Home Manager setups, Nix flakes, services, or troubleshooting Nix builds. Covers creating new configurations, modifying existing ones, adding packages, setting up services, writing modules, and debugging build failures.

Analyze codebases to generate optimal Claude Code Sandbox configurations. Use this skill when users need to set up sandbox security settings for their projects. This skill should be triggered when users ask about sandbox configuration, security settings, or when setting up Claude Code for a new project. It analyzes the codebase stack (Node.js, Python, Rust, Go, PHP, etc.), detects dependencies, and generates appropriate sandbox and permission settings through an interactive Q&A process.

4 hooks across 4 events