Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 23 additions & 2 deletions .claude/settings.json
Original file line number Diff line number Diff line change
Expand Up @@ -8,11 +8,32 @@
"mcpServers": {
"playwright": {
"command": "npx",
"args": ["@playwright/mcp@latest"]
"args": [
"@playwright/mcp@latest"
]
},
"azure": {
"command": "npx",
"args": ["-y", "@azure/mcp@latest", "server", "start"]
"args": [
"-y",
"@azure/mcp@latest",
"server",
"start"
]
}
},
"hooks": {
"PreToolUse": [
{
"matcher": "Bash",
"hooks": [
{
"type": "command",
"command": "npx -y aireceipts-cli@latest hook pre-push",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Constrain the receipt hook to git pushes

In Claude Code sessions for this repo, the PreToolUse group matches every Bash tool call, and because this handler has no if guard, unrelated commands such as tests, rg, or cat still spawn npx -y aireceipts-cli@latest and wait until it exits or hits the 10s timeout. Claude Code hook resolution supports narrowing Bash handlers with an if pattern to avoid this process-spawn overhead, so this should be filtered to the git-push commands the receipt hook actually needs; otherwise normal terminal work is slowed and noisy whenever npm is cold, offline, or cannot resolve the package.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Pin the hook CLI version

This committed project hook executes aireceipts-cli@latest, so every Claude Code user can run newly published hook code and receipt-generation behavior without any reviewed repo change; I checked npx --help, which describes running local or remote npm package specs as <pkg>[@<version>], and this line deliberately selects the moving latest tag. Since the commit message says the dogfood target is v0.6.0, pinning that version (or vendoring the hook) avoids future CLI releases unexpectedly changing or breaking pushes for contributors.

Useful? React with 👍 / 👎.

"timeout": 60
}
]
}
]
}
}
Loading