Repository for Supibot commands

commands repo.txt

1. Repo will be new, and separate from anything that concerns the `supibot-sql` repo 
  - (idea: supibot-sql is just a version control for whatever the main instance does)
2. Implement a method into `sb.Command` to "install" a new command from a description object
3. sb.Command.install will also handle duplicates - will update instead of failing (like now)
4. Repo command definitions will be in `.js` syntax as IIFEs that return a description object
5. Each command definition should be prefaced by an author/ownership comment
6. Think about some sort of authorship/source signature hash, not necessarily as a part of the definitiion but rather as a separate file or a list of hashsums in the root dir

I would think of the source as the Github repository (username/repo_name) or even path to the command (username/repo_name/commands/command.js).

1. sb.Command.install will also handle duplicates - will update instead of failing (like now)

IMO this should be a flag to not accidentally override a command.

the best approach would imo probably to have flags for both

• installable commands (to separate commands that should not be installed remotely)
• overwritable commands (which along with the install flag would update themselves as needed)

I would think of the source as the Github repository (username/repo_name) or even path to the command (username/repo_name/commands/command.js).

does this mean there would always have to be two copies of a command? one in the "aggregate" repo and one in each author's repo?
i feel like custom version control repos shouldn't be connected to this repo