Changelog tools

Changelog tools — a demo bundle for the ADI Store

Two small tools an agent can reach for: one turns a commit range into release notes, the other refuses a commit subject nobody will be able to read in a year.

It is here to be read as much as to be run. It is the example of a bundle that carries tools and nothing else, and of the smallest useful thing a tool can be — a shell script with a comment at the top. Install it with a click from the ADI Store, or:

adi-mono marketplace install store/changelog-tools

What makes this a bundle

The directory names at the top level, and nothing else:

tools/
  changelog.sh      # one tool, named by its filename
  commit-lint.sh    # and another

A tool is a file an agent may run. It arrives as a tool in your store — readable, editable, and yours — and an agent only reaches it when its own definition lists it (bin_tools). Installing a tool gives it to nobody by itself.

Either one installs on its own:

adi-mono marketplace install store/changelog-tools/tools/changelog

What is in them

changelog.sh is five lines of git log. commit-lint.sh is a regex and an exit code. That is deliberate: a tool is not a program you maintain, it is the shortest thing that answers one question, and it is worth publishing exactly when the shortest thing is still not obvious.

Publishing one of your own

1. Put your elements in kind directories at the root of a repository, as above.
2. Push it, and take the commit: git rev-parse HEAD.
3. Add an entry to a marketplace manifest naming that repository and that full 40-hex commit.

The format is in docs/marketplace.md.

What it does not do

Nothing here runs on arrival, and nothing here reaches the network. Both scripts read a git repository you point them at and print to stdout.