Olmo's workflow

Find an issue.
git fetch mootools ¹ to get any new changes to master
git checkout -b [action]-[issue#]-[description-delimited-by-dash] e.g. git checkout -b fix-1000-ie-button-type-throws
repeat 2-3 for any submodules
if necessary, add specs to reproduce failure
work on the fix ²
run the specs ³ until all browsers pass
git add [files] or git commit -a if modified already present files
write a good commit message ⁴
git push [your-git-repo] [action]-[issue#]-[description-delimited-by-dash] (tip: use tab completion for topic branch)
go to your github repo page
select your topic branch
send pull request. optionally modify subject and description of pull request.
done, or start over at 1.

Use ./developers.sh to get your favorite MooTools developers added to your known git remote repos.

Stick to what you need to fix. If you find something else that needs to be fixed or cleaned, create an issue or create another topic branch.
If you're going to fix it with something controversial or something you're unsure of, then commit early and send a pull request with description and with @requests to notify developers.

General pattern

<action>
<empty line>
<description>
<empty line>
<spec results>

Use active voice to explain what you did. Examples: Fixes, Improves, Removes. Include issue # if appropriate. Fixes #2100.

Add as much relevant information as necessary: what, why, how, where.

General pattern

<RESULT>: <browser> <browser-version>; ...
...

Example: PASSED: Ffx 3-5, 8, 10; IE6-9, Safari 5

Provide feedback