Skip to content

ag21o9/jarvis_cli_github_tool

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

10 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Jarvis CLI — Your Personal Dev Assistant

Jarvis is a powerful, interactive CLI tool that helps developers quickly scaffold projects, automate setup tasks, and create GitHub repositories — all from the terminal with a single command.

It is designed to save time during hackathons, rapid prototyping, and daily development.


Features

Smart Project Generators

  • jarvis create backend

    • Express server setup
    • Prisma + CORS + Axios + Dotenv installed
    • Folder structure created
    • .env + .gitignore configured
  • jarvis create frontend

    • Choose:

      • 🌐 Website → React + Vite + Tailwind
      • 📱 Android → React Native (Expo)
    • Fully auto-configured

GitHub Automation

  • jarvis create repo <name>

    • Creates repo in your GitHub account
    • Pushes current code automatically

Utility Commands

  • jarvis tell date
  • jarvis tell time

Secure Login System

First-time setup stores:

  • Username
  • Email
  • Password (local only)
  • GitHub Token

Installation

Install globally using npm:

npm i jarvis_github_cli@1.0.0

After installing, you can run from anywhere:

jarvis

🔑 First-Time Setup

When you run Jarvis for the first time:

jarvis

It will ask for:

  • Username
  • Email
  • Password
  • GitHub Personal Access Token

This information is stored locally on your system.


How to Get a GitHub Token (Important)

Jarvis needs a GitHub token to create repositories automatically.

Step-by-step:

  1. Go to:

    https://github.com/settings/tokens
    
  2. Click:

    Generate new token (classic)
    
  3. Select scopes:

    • ✅ repo
    • ✅ workflow (optional but recommended)
  4. Click:

    Generate token
    
  5. Copy the token immediately (GitHub will not show it again)

  6. Paste it into Jarvis when asked.


Security Note

  • Your token is stored locally only
  • Never upload your token to GitHub
  • Never share it publicly

If compromised:

  • Delete it from GitHub
  • Generate a new one

Usage Guide

Create Backend

jarvis create backend

Creates:

  • Express project
  • Prisma installed
  • Config folders
  • .env + .gitignore
  • Starter server file

Create Frontend

jarvis create frontend

Then choose:

  • Website (React + Vite + Tailwind)
  • Android App (React Native + Expo)

Jarvis will:

  • Ask project name
  • Install dependencies
  • Configure everything automatically

Create GitHub Repo

Inside your project folder:

jarvis create repo my-project-name

Jarvis will:

  • Create a repo on GitHub
  • Initialize git
  • Push your code

📅 Utility Commands

jarvis tell date
jarvis tell time

🔓 Logout

jarvis logout

Clears stored user credentials.


📁 Example Workflow

mkdir myApp
cd myApp

jarvis create backend
jarvis create frontend
jarvis create repo myApp

In minutes you have:

  • Backend
  • Frontend
  • GitHub repo

Why Jarvis?

Jarvis removes repetitive setup tasks like:

  • Creating folders
  • Installing packages
  • Configuring Tailwind
  • Setting up Express
  • Initializing Git
  • Creating repositories

Perfect for:

  • Hackathons
  • Students
  • Freelancers
  • Rapid MVP building

🤝 Contributing

Contributions are welcome and appreciated. If you would like to improve the Jarvis CLI GitHub Tool, please follow the workflow below to keep the project clean and easy to maintain.

📌 How to Contribute

  1. Fork this repository to your GitHub account.

  2. Clone your fork locally:

    git clone https://github.com/your-username/jarvis_cli_github_tool.git
  3. Navigate into the project directory:

    cd jarvis_cli_github_tool
  4. Make sure your local main branch is up to date:

    git switch main
    git pull origin main
  5. Create a new branch for your changes:

    git switch -c docs/your-change-name

    (Use prefixes like feat/, fix/, or docs/ based on your contribution.)

  6. Make your updates and test the CLI locally before committing.

  7. Stage and commit your changes:

    git add .
    git commit -m "update project files"
  8. Push your branch to your fork:

    git push origin docs/your-change-name
  9. Go to GitHub and open a Pull Request from your branch to the main repository. Provide a clear description of what you changed and why.


🧩 Contribution Guidelines

  • Keep pull requests small and focused.
  • Follow the existing project structure and naming conventions.
  • Write clear commit messages.
  • Update documentation if your change affects CLI usage or commands.

🐞 Reporting Issues

If you find a bug or want to suggest a feature:

  • Open an Issue in the repository.
  • Provide clear steps to reproduce.
  • Include screenshots or terminal logs when possible.

Author

Its me Abhijeet Gupta Built with ❤️ to make development faster and more enjoyable.


Future Updates

Planned features:

  • Fullstack generator
  • Auth-ready backend templates
  • AI-based project creation
  • Deployment automation
  • Theme customization
  • Voice commands

⭐ Support

If you find this helpful:

  • Star the repository
  • Share with friends
  • Contribute ideas

Happy Building

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors