Thanks for your post.
Unfortunately you cannot easily commit custom scripts on their own with SQL Source Control.
We have a facility called "Migration Scripts" which lets you add your own scripts (see here
) but these are created at the point you commit other changes (you can't create them on an ad-hoc basis)
You also cannot really control the ordering of the scripts. A migration script will cover changes between a pair of revisions of changes; so a script covering an earlier set of revisions would usually get run before a script covering later revisions, however the only way to ensure everything was run in a specific order would be to have one script containing everything.