Menu
Run sync.sh --check and pre-commit on a named plugin to surface validation errors before committing.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Analyze conversation to improve global ~/CLAUDE.md with cross-project preferences and behavior patterns. Use this when Claude repeated a mistake it makes everywhere, when you had to re-explain a preference that should apply to all projects, or when you notice a communication or workflow pattern worth capturing globally. Trigger with "reflect globally", "update global instructions", "capture cross-project preference", or "improve global CLAUDE.md". Also use when /reflection surfaces findings that aren't project-specific.
Analyze conversation to improve the project's CLAUDE.md. Use this at the end of any session, after correcting Claude, after explaining something twice, or when you notice Claude guessing about project conventions. Trigger with "reflect", "update CLAUDE.md", "capture what we learned", or "improve project instructions". Even if the session felt smooth, there may be implicit knowledge worth documenting.
Use when you need to recall past conversations, find how a problem was solved before, look up previous decisions, search for context from earlier sessions, or when the user asks about conversation history
Use when the user asks for a summary of work activity, daily/weekly standup report, what someone worked on, activity log, or needs to see all PRs, MRs, and Jira tickets touched during a specific date range
Use when the user asks to "address PR comments", "fix review comments", "handle PR feedback", or "respond to reviewers". By default operates on the current PR (from branch or conversation context). Use with "all" argument to process all open PRs with unanswered reviewer comments.
Use when the user asks to "update PR description", "update MR description", "analyze PR/MR changes and update comment", "summarize PR", "summarize MR", "generate PR/MR body from changes", or wants to automatically update a pull request or merge request description based on its code changes
| name | validate-plugin |
| description | Run sync.sh --check and pre-commit on a named plugin to surface validation errors before committing. |
| disable-model-invocation | true |
Validate a plugin bundle (or the whole marketplace). Usage: /validate-plugin [plugin-name]
Run the drift-check gate:
./scripts/sync.sh --check
This validates all plugin structure and checks that marketplace.json and
the README catalog table are in sync with source. Exits non-zero if any
plugin fails validation or generated files are out of date.
If a specific plugin name was given in $ARGUMENTS, also report any
issues found for that plugin specifically (filter sync.sh output).
Run pre-commit on plugin files:
pre-commit run --files plugins/<name>/**
If no plugin name given, run on all files:
pre-commit run --all-files
Report results: show pass/fail per hook, and for any failures show the exact error output with file paths and line numbers.
If validation passed: confirm the plugin is ready to commit and remind the user to run the end-to-end install test:
claude plugin marketplace add /absolute/path/to/agent-skills
claude plugin install <plugin-name>@langburd