It's frequently used by software developers, web designers, writers and other specialists to avoid mundane, repetitive actions and commands such as "relaunching" tools after changing source files or configurations.

Common use cases include: an IDE replacement, web development tools, designing "smart" and "responsive" build systems/workflows, automating various project tasks and installing/monitoring various system services.

Avoiding gem/dependency problems

It's important that you always run Guard through Bundler to avoid errors.

If you're getting sick of typing bundle exec all the time, try one of the following:

(Recommended) Running bundle binstub guard will create bin/guard in your
project, which means running bin/guard (tab completion will save you a key
stroke or two) will have the exact same result as bundle exec guard.

Or, you can alias be="bundle exec" in your .bashrc or similar and the execute only be guard.
Protip: It will work for all comands executed in bundle exec context!

Or, for RubyGems >= 2.2.0 (at least, though the more recent the better),
simply set the RUBYGEMS_GEMDEPS environment variable to - (for autodetecting
the Gemfile in the current or parent directories) or set it to the path of your Gemfile.

(To upgrade RubyGems from RVM, use the rvm rubygems command).

NOTE: this Rubygems feature is still under development still lacks many features of bundler

Add Guard plugins

Guard is now ready to use and you should add some Guard plugins for your specific use. Start exploring the many Guard
plugins available by browsing the Guard organization on GitHub or by searching for guard-
on RubyGems.

When you have found a Guard plugin of your interest, add it to your Gemfile:

group:developmentdogem'<guard-plugin-name>'end

See the init section of the Guard usage below to see how to install the supplied plugin template that you can install and
to suit your needs.

Usage

Guard is run from the command line. Please open your terminal and go to your project work directory.