This guide covers basic usage, workflows, and advanced integrations for jjConfig.
# 1. Start working
jj new
# 2. Make changes
echo "Some content" >> file.txt
# 3. Check what changed
jj st
jj d
# 4. Describe your change
jj describe -m "feat: add new feature"
# 5. Push to remote
jj pushjj init # Initialize repo (with GitMCP)
jj st # Status
jj ll # Log last 20 commits
jj d # Diff
jj ci # Commit interactively
jj push # Push bookmarks
jj sync # Sync remotesjj fzf: Launch jj-fzfjj tui: Launch lazyjjjj ui: Launch gg
GitMCP provides local AI repository context for tools—no API tokens required.
How It Works:
- Git hooks (
post-commit,post-merge,post-checkout) generate.mcp/context.json - 100% local processing
- Compatible with IDEs and desktop AIs
Setup:
cat .mcp/cursor-config.json >> ~/.cursor/mcp.json # Cursor IDE
cat .mcp/claude-config.json >> ~/Library/Application\ Support/Claude/claude_desktop_config.json # Claude DesktopMCP server URL: https://gitmcp.io/Thomo1318/jjConfig
See MCP docs for details.
Repomix consolidates your entire repository into a single AI-friendly file for context injection.
How It Works:
- Git hooks automatically generate
.repomix/repomix-latest.txtafter commits - Contains full repository content optimized for AI tools
- Includes token counts and file statistics
Generated Files in .repomix/:
context.json: Metadatarepomix-latest.txt: Symlink to latest (use this!)
Usage:
# Copy to AI tool
cat .repomix/repomix-latest.txt | pbcopy
# Check token count
repomix --token-count-tree 50 .
# Show status
jj repomix-statusWe use git-semver to automatically calculate the next version based on Conventional Commits and tags.
| Command | Description | Example Output |
|---|---|---|
jj semver |
Show current version | v1.2.0 |
jj next-patch |
Show next patch version | v1.2.1 |
jj next-minor |
Show next minor version | v1.3.0 |
jj next-major |
Show next major version | v2.0.0 |
# create a release with the correct version
gh release create $(jj next-minor) --generate-notesWe use git-semver to automatically calculate the next version based on Conventional Commits and tags.
When you run jj describe, jjConfig provides a strict template to help you follow Conventional Commits:
# <type>(<scope>): <description>
# Types: feat, fix, docs, style, refactor, perf, test, chore
| Command | Description | Example Output |
|---|---|---|
jj semver |
Show current version | v1.2.0 |
jj next-patch |
Show next patch version | v1.2.1 |
jj next-minor |
Show next minor version | v1.3.0 |
jj next-major |
Show next major version | v2.0.0 |
# create a release with the correct version
gh release create $(jj next-minor) --generate-notesSee Troubleshooting Guide for solutions to common install issues.