Adnan Zahir
6a9c18f5a5
The write-guard's matcher regex never matched the actual tool names (createUserStory/createTask/createIssue, not user_story_create etc.), so the metadata guard has never actually fired. It also checked for assigned_to/milestone fields that don't exist on any create tool's schema, which would have denied every create once the matcher was fixed. Guard now validates only the tag contract (area/source/target), covers the batch-create tools per item, and SKILL.md documents the real follow-up calls (assignIssue/assignUserStoryToSprint/addIssueToSprint) needed to set owner and sprint after creation.
14 lines
400 B
JSON
14 lines
400 B
JSON
{
|
|
"hooks": {
|
|
"PreToolUse": [{
|
|
"matcher": "^mcp__taiga__(createUserStory|createTask|createIssue|batchCreateUserStories|batchCreateTasks|batchCreateIssues)$",
|
|
"hooks": [{
|
|
"type": "command",
|
|
"command": "python3 \"${CLAUDE_PLUGIN_ROOT}/hooks/taiga-write-guard.py\"",
|
|
"timeout": 3,
|
|
"statusMessage": "Checking Taiga item metadata..."
|
|
}]
|
|
}]
|
|
}
|
|
}
|