Could you squash this down to one commit? Commits should be standalone. In this case, there isn't a clear reasoning to divide up the commits.
Also as reminder:
Once I give the go ahead, please squash your commits. I say wait so I can see what you change as the review happens
If you use "Fixes #45" instead of "Issue #45", github will automatically close the issue
Treat commit messages like markdown, e.g. use an extra newline to separate paragraphs
For content, it is best to focus on the user-impact and any background for your change and less on recording what you changed, the diff tells you that. e.g. Maybe instead of "Added normalize_newlines adapter predicate", it would be "Add NormalizedPredicate adapter"