commit-research

To enforce report-first commits for research documentation, this Skill verifies that matching reports exist in the _report/ directory before guiding you to stage changes and compose structured commit messages derived from those reports.

Linking research journal entries to git commits requires updating _journal/ content alongside _report/ files, ensuring your commit messages directly reference the specific reports to maintain traceability and consistency across your project history.

You cannot commit research changes without a report first, as this Skill provides guardrails that check for report existence, prevent incomplete commits, and enforce a strict report-first workflow with clear fallbacks for missing documentation.

Structuring commit messages for research tasks involves updating the relevant report content first, then composing the message based on that report, ensuring reviewers can clearly trace the committed work back to specific project documentation.

Yes, this research commit workflow operates without external dependencies, applying its guided multi-step messaging and guarded checks directly to your local _report/ and _journal/ directories to automate disciplined project commits.