@juspay/shelly
Advanced tools
An intelligent CLI assistant that analyzes your command-line history to provide smart, AI-powered suggestions for failed commands. Shelly helps you debug and fix errors without leaving your terminal, boosting productivity with advanced repository organiza
An intelligent CLI assistant that analyzes your command-line history to provide smart, AI-powered suggestions for failed commands. Shelly helps you debug and fix errors without leaving your terminal, boosting productivity with advanced repository organization and AI-assisted development features.
--move optionChoose your installation method based on your needs:
If you want to use Shelly as a command-line tool, install it globally:
npm install -g @juspay/shelly
📖 Next Steps: Follow the Quick Start Guide for complete setup instructions including shell integration and API configuration.
If you want to contribute to the project or run it locally for development:
# Clone and navigate to project directory
git clone https://github.com/juspay/shelly.git
📖 Next Steps: Follow the Complete Setup Guide for detailed local development instructions.
Important: Shelly uses a dual CLI architecture with two distinct usage modes:
- Error Analysis Mode:
shelly(no arguments) - Analyzes the last failed command from your shell history- Repository Management Mode:
shelly <command>- Uses specific commands likeorganize,memory,init,statusThese are handled by different internal systems, so the commands work differently.
After setup, simply run shelly after any failed command:
$ grp "hello" file.txt
grp: command not found
$ shelly
Analyzing previous command: "grp "hello" file.txt"
Maybe you meant: grep "hello" file.txt
--- Neurolink Analysis ---
The error "grp: command not found" indicates that the shell could not find the 'grp' command.
The correct command is likely 'grep' which is used for searching text patterns in files.
--------------------------
Did you mean one of these?
- grep
- git
- gcc
Transform any project into a publication-ready repository:
# Organize current project with full scaffolding
shelly organize
# Force overwrite existing files
shelly organize --force
# Only add missing files, preserve existing ones
shelly organize --update
# Move misplaced files to correct directories
shelly organize --move
# Organize a specific directory
shelly organize --directory /path/to/project
# Check repository organization status
shelly status
# Initialize a brand new project
shelly init my-new-project
shelly init my-project --template typescript --directory ~/projects
Create and maintain AI-assisted development context:
# Initialize Memory Bank for the current project
shelly memory init
# Force reinitialize existing Memory Bank
shelly memory init --force
# Check Memory Bank status and files
shelly memory status
# List all Memory Bank files with details
shelly memory list
# View specific Memory Bank file content
shelly memory show projectbrief.md
shelly memory show current/activeContext.md
# Update all Memory Bank files with latest project state
shelly memory update
# Update only a specific file
shelly memory update --file progress.md
Configure your GitHub repository with industry best practices for publishing and collaboration:
# Full GitHub setup commands
shelly github setup # Interactive setup with confirmation
shelly github setup --force # Skip confirmation prompts
shelly github setup --dry-run # Preview changes without applying
shelly github setup --directory /path # Setup specific repository
# Shortcut commands (same functionality)
shelly gh # Shortcut for github setup
shelly gh --force # Quick forced setup
shelly gh --dry-run # Quick dry run
# Complete repository setup (GitHub + organize)
shelly setup # Run both GitHub setup AND organize
shelly setup --force # Skip all confirmations
shelly setup --github-only # Only GitHub setup, skip organize
shelly setup --organize-only # Only organize, skip GitHub setup
Prerequisites:
export GITHUB_TOKEN=your_token_hererepo, admin:repo_hook, write:packages (for classic tokens)What it configures:
Enable detailed logging for troubleshooting:
SHELLY_DEBUG=true shelly
You can analyze specific commands directly:
shelly "your-failed-command"
# Or for local setup: node src/main.js "your-failed-command"
Force detection of a specific shell:
SHELL_OVERRIDE=bash shelly
Bash/Zsh: Uses the fc command with dynamic function generation for real-time history access.
Tcsh: Uses history 2 command with direct alias definition for reliable access to command history.
Fallback Mode: Reads shell history files directly from disk and uses process tree analysis to detect shell type.
--move option📚 Detailed Troubleshooting Guide: For comprehensive installation and runtime troubleshooting, including native module build issues, see the Complete Troubleshooting Guide.
This usually means the shell integration isn't set up correctly.
Solutions:
# For Bash - ensure history is enabled
echo 'HISTSIZE=1000' >> ~/.bashrc
echo 'SAVEHIST=1000' >> ~/.bashrc
# For Zsh - check history settings
echo 'HISTSIZE=1000' >> ~/.zshrc
echo 'SAVEHIST=1000' >> ~/.zshrc
# For Tcsh - ensure history is enabled
echo 'set history = 1000' >> ~/.tcshrc
echo 'set savehist = 1000' >> ~/.tcshrc
Cause: The alias wasn't set up correctly or shell config wasn't reloaded.
Solutions:
source ~/.bashrc (or equivalent for your shell)npm list -g @juspay/shellyEnsure you're running shelly immediately after the failed command. The tool analyzes the most recent command in your shell history.
Cause: The absolute path in the tcsh alias is incorrect.
Solution: Use pwd in the project directory to get the correct path and update your alias.
Enable debug mode to see detailed information about what the tool is doing:
SHELLY_DEBUG=true shelly
Error Analysis:
shelly # Analyze last failed command
shelly "command" # Analyze specific command
Repository Organization:
shelly organize # Organize repository structure
shelly organize --force # Overwrite existing files
shelly organize --update # Only add missing files
shelly status # Check organization status
GitHub Setup:
shelly gh # Quick GitHub setup (shortcut)
shelly github setup # Full GitHub setup
shelly gh --dry-run # Preview changes
Complete Setup:
shelly setup # GitHub setup + organize
shelly setup --force # Skip all confirmations
Memory Bank:
shelly memory init # Initialize project memory
shelly memory status # Check memory status
shelly memory update # Update all memory files
Project Initialization:
shelly init project-name # Create new project
Bash:
echo 'eval "$(shelly --alias)"' >> ~/.bashrc && source ~/.bashrc
Zsh:
echo 'eval "$(shelly --alias)"' >> ~/.zshrc && source ~/.zshrc
Fish:
echo 'shelly --alias | source' >> ~/.config/fish/config.fish && source ~/.config/fish/config.fish
shellyThe tool automatically detects your shell and adapts its behavior accordingly. No additional configuration is required for basic usage.
Contributions are welcome! Please feel free to submit issues and enhancement requests.
Remove the eval "$(shelly --alias)" line from your shell configuration file and reload your shell.
MIT License
FAQs
An intelligent CLI assistant that analyzes your command-line history to provide smart, AI-powered suggestions for failed commands. Shelly helps you debug and fix errors without leaving your terminal, boosting productivity with advanced repository organiza
We found that @juspay/shelly demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 7 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
November CVE publications fell 25% YoY even as 2025 totals rose, showing how a few major CNAs can swing “global” counts and skew perceived risk.
Security News
React disclosed a CVSS 10.0 RCE in React Server Components and is advising users to upgrade affected packages and frameworks to patched versions now.
Research
/Security News
We spotted a wave of auto-generated “elf-*” npm packages published every two minutes from new accounts, with simple malware variants and early takedowns underway.