/auto-approve

You are helping the user set up auto-approval hooks for the jira plugin to reduce the number of permission prompts during JIRA workflows.

Context

The jira plugin frequently needs to:

• Read configuration files (.claude/jira.local.md)
• Search for content patterns (Grep)
• Find files by patterns (Glob)
• Run plugin scripts from scripts/jira_client.py

Without auto-approval hooks, each of these operations may require manual approval, which significantly slows down the workflow.

Task

Step 0: Resolve Plugin Root

Extract PLUGIN_ROOT from the <jira-context> system reminder injected by the UserPromptSubmit hook. Use the value from <plugin-root>.

---

Step 1: Configure Auto-Approval

1. Ask the user whether they want to configure auto-approval:

   • Globally (in ~/.claude/settings.json) - affects all projects
   • Project-specific (in .claude/settings.local.json) - affects only this project
   • Both

2. Read the current settings file(s) to check if hooks already exist

3. Merge or create hooks configuration with these auto-approvals:

   • Bash commands containing /scripts/run.sh or /scripts/jira_client.py
   • Bash commands checking for .claude/jira.local.md configuration file
   • Bash commands with /tmp/jira-cache/ pattern (cache operations)
   • Read operations on configuration and script files (.md, .txt, .json, .py, .sh)
   • All Grep operations
   • All Glob operations

4. Write the updated settings back to the appropriate file(s)

5. Inform the user that:

   • Settings have been updated
   • They need to restart Claude Code or start a new session for the hooks to take effect
   • They can review the hooks in the /hooks menu
   • They can revert by removing the hooks from the settings file

Important Notes

• If the user already has hooks configured, merge the new hooks with existing ones (don't overwrite)
• Preserve all other settings in the file
• Use proper JSON formatting with the correct hook response schema
• The hooks will only auto-approve the specific patterns listed - other operations will still require manual approval
• Hooks read JSON input from stdin using input=$(cat)
• The response MUST be nested under hookSpecificOutput with hookEventName: "PreToolUse"

Example Hook Configuration

{
  "hooks": {
    "PreToolUse": [
      {
        "matcher": "Bash",
        "hooks": [
          {
            "type": "command",
            "command": "input=$(cat); if echo \"$input\" | grep -qE '(/scripts/run\\.sh|/scripts/jira_client\\.py|jira\\.local\\.md|/tmp/jira-cache)'; then echo '{\"hookSpecificOutput\": {\"hookEventName\": \"PreToolUse\", \"permissionDecision\": \"allow\", \"permissionDecisionReason\": \"JIRA plugin script/config auto-approved\"}}'; fi",
            "timeout": 5
          }
        ]
      },
      {
        "matcher": "Read",
        "hooks": [
          {
            "type": "command",
            "command": "input=$(cat); if echo \"$input\" | grep -qE '\\.(md|txt|json|py|sh)\"'; then echo '{\"hookSpecificOutput\": {\"hookEventName\": \"PreToolUse\", \"permissionDecision\": \"allow\", \"permissionDecisionReason\": \"Configuration/script file read auto-approved\"}}'; fi",
            "timeout": 5
          }
        ]
      },
      {
        "matcher": "Grep",
        "hooks": [
          {
            "type": "command",
            "command": "echo '{\"hookSpecificOutput\": {\"hookEventName\": \"PreToolUse\", \"permissionDecision\": \"allow\", \"permissionDecisionReason\": \"Grep operations auto-approved\"}}'",
            "timeout": 5
          }
        ]
      },
      {
        "matcher": "Glob",
        "hooks": [
          {
            "type": "command",
            "command": "echo '{\"hookSpecificOutput\": {\"hookEventName\": \"PreToolUse\", \"permissionDecision\": \"allow\", \"permissionDecisionReason\": \"Glob operations auto-approved\"}}'",
            "timeout": 5
          }
        ]
      }
    ]
  }
}

Hook Response Schema

For PreToolUse hooks, the output must be valid JSON with this exact structure:

{
  "hookSpecificOutput": {
    "hookEventName": "PreToolUse",
    "permissionDecision": "allow" | "deny" | "ask",
    "permissionDecisionReason": "Description shown to user"
  }
}

Critical Requirements:

• The response MUST be nested under hookSpecificOutput
• The hook MUST exit with code 0 for the JSON to be processed
• If the hook outputs nothing (empty), default permission logic applies
• The hookEventName must be exactly "PreToolUse"

Auto-Approved Patterns

The following patterns will be automatically approved:

Bash Commands

• Commands containing /scripts/run.sh (plugin script runner)
• Commands containing /scripts/jira_client.py (main Python script)
• Commands checking .claude/jira.local.md (configuration file)
• Commands accessing /tmp/jira-cache/ (cache directory)

Read Operations

• Reading .md, .txt, .json, .py, .sh files
• Reading configuration and documentation files

Search Operations

• All Grep operations (content search)
• All Glob operations (file pattern matching)

Security Considerations

These hooks are designed to auto-approve only:

• Operations within the jira plugin scope
• Read-only operations on configuration files
• Standard search and file-finding operations
• Cache operations in temporary directory

They will NOT auto-approve:

• Writing to arbitrary files
• Deleting files
• Network operations (these are handled by jira_client.py)
• System-level commands

Begin by asking the user which scope they prefer for the auto-approval configuration.