Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
How this command is triggered — by the user, by Claude, or both
Slash command
/pantry:pantry-check <what you need, e.g. "date formatting">The summary Claude sees in its command listing — used to decide when to auto-load this command
Run a pantry check for: $ARGUMENTS Use the pantry command from your session context (or plain `pantry` if on PATH): Show the user the output verbatim, then follow it: if it recommends a file, that's what gets used in any follow-up work; if it says the pantry is empty, building new is the right call.
Run a pantry check for: $ARGUMENTS
Use the pantry command from your session context (or plain pantry if on
PATH):
<pantry-cmd> check "$ARGUMENTS"
Show the user the output verbatim, then follow it: if it recommends a file, that's what gets used in any follow-up work; if it says the pantry is empty, building new is the right call.
npx claudepluginhub 0ss/pantry --plugin pantry