feat: trigger ldd by hook and skill keywords #5
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.
This pull request introduces an automated detection and engagement mechanism for Go code work within the linter-driven development workflow. It adds a new hook that analyzes user prompts and project context to determine when to activate the Go linter-driven development skill, and updates documentation to clarify the auto-engagement process. The most important changes are:
Hook system integration:
UserPromptSubmithook configuration inhooks.jsonto trigger a custom shell script when a user submits a prompt.user-prompt-submit.shscript, which analyzes the user's message and project directory to detect Go-related work and signals the system to use the Go linter-driven development skill when appropriate.Documentation update:
SKILL.md) to explain the new auto-engagement behavior and instruct users on what to expect when the hook detects Go code work.