Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By jeprecated
Custom commands, agents, and skills for NixOS, Jujutsu, and documentation workflows
npx claudepluginhub jeprecated/claude-setup --plugin jmo-development-toolsThis directory contains custom slash commands for Claude Code. Slash commands let you create reusable prompts that can be invoked with `/command-name`.
Assess the current repo and recommend which plugins to enable at the project level
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
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.
Executes bash commands
Hook triggers when Bash tool is used
Uses power tools
Uses Bash, Write, or Edit tools
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Ubuntu changes since training cutoff (latest: 25.10) โ sudo-rs, rust-coreutils, APT 3.1, OpenSSH 10.0, OpenSSL 3.5 post-quantum crypto, Chrony NTS, Wayland-only GNOME. Load before working with Ubuntu.
Bootstrap - Developer onboarding accelerator. Analyzes project requirements, detects missing dependencies, generates Docker/docker-compose configs, creates .env templates, sets up pre-commit hooks, configures IDE settings (VSCode/Cursor), and troubleshoots 'it works on my machine' issues. Gets developers productive in minutes, not hours.
Custom commands, skills, agents, rules, hooks, and output styles for Claude Code - session continuity and modern CLI tooling for real-world development workflows
Infrastructure management discipline: Ansible automation, container orchestration, Proxmox virtualization, Unraid NAS, and network architecture
Structured operational documentation and runbook patterns for human operators. Helps create clear, actionable runbooks for troubleshooting, incident response, and maintenance.
Nix language server
File-based task queue for agent loops with slash commands for queue management
Serve markdown prompt files as @ mention resources in Claude Code
A centralized collection of custom configurations, agents, commands, templates, and documentation for working with Claude Code.
agents/)Specialized sub-agents with specific expertise:
commands/)Reusable prompts for common workflows:
hooks/)Executable shell hooks wired via hooks/hooks.json (follows the Hookify convention โ hooks live at <plugin-root>/hooks/hooks.json, not .claude-plugin/hooks/):
grep/find in favor of rg/fdPrompt-injection "hooks" (markdown instructions loaded per session) live in hooks-docs/:
final-review gate on top of skill evaluationskills/)Interactive workflows for complex multi-step processes:
codex review, and Codex can call claude -ptemplates/)Starter templates for project documentation:
Learn more about templates โ
mcp-servers/)Catalog of Model Context Protocol servers:
Learn more about MCP servers โ
docs/)Comprehensive guides and learnings:
Step 1: Install via Plugin Marketplace
In Claude Code, run the /plugin command and enter the repository path:
/plugin
> /home/jmo/Development/claude-setup
This installs all agents, commands, and templates automatically.
Step 2: Install Dependencies (includes contextbricks status line)
Navigate to the repository and install npm dependencies:
cd ~/Development/claude-setup
npm install
This will automatically install and configure:
Step 3: Symlink Global Instructions
Link the global instructions to your Claude Code config:
ln -sf ~/Development/claude-setup/docs/global-instructions.md ~/.claude/CLAUDE.md
Your existing ~/.claude/CLAUDE.md will be backed up to ~/.claude/CLAUDE.md.backup.
Step 4: Install Hooks (Recommended)
Install the combined hook to improve skill activation reliability and automatically require end-of-task review:
mkdir -p ~/.claude/hooks
ln -sf ~/Development/active/agentic/claude-setup/hooks-docs/forced-eval-with-final-review.md ~/.claude/hooks/user-prompt-submit.md
If you only want the original startup behavior, use hooks-docs/forced-eval-skill.md instead.
Step 5: Configure MCP Server Paths
โ ๏ธ Important: Update the filesystem MCP server path to match your system:
# Edit .mcp.json and update the filesystem path
# Replace /home/jmo/Development with your actual development directory
Files to update:
.mcp.json - Line 19: Update filesystem args pathmcp-servers/filesystem.json - Line 7: Update filesystem args pathStep 6: Restart Claude Code
Restart Claude Code to load all components.