Add tailtest under Core Development Skills - #146
Open
shridipavansaber wants to merge 1 commit into
Open
Conversation
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.
Adds tailtest under Core Development Skills, in the same two-bullet format as the surrounding entries.
tailtest hooks PostToolUse so that every file Claude Code edits gets tested in the same turn: the edited file is queued, production-shaped scenarios are generated through a rule layer, they run against the project's existing test runner, and failures come back to Claude before it moves on. Nothing to invoke.
It sits alongside the verification-gate entries here rather than duplicating them: the gate entries check a change before it lands, tailtest exercises the code that was just written.
Repo: https://github.com/avansaber/tailtest