Linking Code Commits with Work Items Using Git Hooks and CLI Tools

Background: Teams often manage requirements/defects and code separately, making it hard to trace which code fixes which issue.

Goal: Associate code commits with work items (requirements or defects) by embedding the work item ID in commit messages, enabling easier understanding and automated test selection.

Solution Evolution:

1. Manual association – developers manually add ID and link to commit messages; cumbersome and not enforced.

2. Assisted manual – a CLI tool (named fish) queries assigned work items via API, allowing developers to retrieve IDs before committing.

3. Selection association – the CLI provides an interactive ID selection (e.g., git ci replaces git commit) and automatically appends the link.

4. Branch-name association – when branch names follow a pattern like task_12345678_a, a commit‑msg hook extracts the ID from the branch, eliminating the need for manual selection.

Client Hook Generation and Activation:

Hooks reside in .git/hooks and are not shared; using Git 2.9+ we can set a custom hooksPath (e.g., .githooks) and distribute hooks via the repository.

Commands such as fish hook install create the hooks directory, and fish hook enable activates them. For automatic activation, a wrapper script can replace the system git binary, checking for a .githooks folder and invoking the appropriate hook.

Knowledge Expansion:

Further reading on git hooks, Node.js CLI development (commander, Inquirer.js, shelljs, chalk) and related resources are listed.

Conclusion: The described low‑cost approach improves team collaboration by tightly linking code with work items, and can be extended to various development domains.