Conversation
Three new tools power a drill-down workflow for reading git history. `git_log` searches commits by message, file paths, date range, and count. `git_show` returns the full commit message and changed-file stats (without diff content). `git_diff_commit` produces the actual diff for specified files in a commit, with optional regex grep and 500-line truncation for large outputs. A new `git-reading` skill composes all three alongside `git_diff` and documents the intended workflow: `git_log` to find commits, `git_show` to inspect metadata, and `git_diff_commit` to drill into specific files. The skill is added to both the `dev` and `stager` personas. The `stager` persona's instructions are significantly revised to actively use history context before deciding what to stage — searching for prior commits that touched the same files, and following established grouping patterns. New change-set cohesion rules cover single-sentence descriptions, tests with their implementation, and dependency updates alongside the code that introduced them. The `git-stage` skill is refactored to remove `git_diff` (now provided by `git-reading`) and its "Surgical Precision" instructions are tightened. Signed-off-by: Jean Mertz <git@jeanmertz.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Three new tools power a drill-down workflow for reading git history.
git_logsearches commits by message, file paths, date range, and count.git_showreturns the full commit message and changed-file stats (without diff content).git_diff_commitproduces the actual diff for specified files in a commit, with optional regex grep and 500-line truncation for large outputs.A new
git-readingskill composes all three alongsidegit_diffand documents the intended workflow:git_logto find commits,git_showto inspect metadata, andgit_diff_committo drill into specific files. The skill is added to both thedevandstagerpersonas.The
stagerpersona's instructions are significantly revised to actively use history context before deciding what to stage — searching for prior commits that touched the same files, and following established grouping patterns. New change-set cohesion rules cover single-sentence descriptions, tests with their implementation, and dependency updates alongside the code that introduced them.The
git-stageskill is refactored to removegit_diff(now provided bygit-reading) and its "Surgical Precision" instructions are tightened.