ai-tools

Use when a dependency update needs assessing before adoption. Covers a user asking whether to upgrade a package to a new version, a manual version bump, a lockfile change under review, or a bot-opened update PR (Renovate, Dependabot, or similar). Also fires on "is version X worth adopting", "what does this update change for us", or "review this dependency bump". Do NOT use to apply the update, fix a broken build, or replace an abandoned dependency.

This skill should be used when the user asks to 'read this page', 'what does this URL say', 'fetch this article', 'summarize this PDF', or 'get the transcript of this video', or when web content is needed as context for another task. Fetches web pages, PDF/Word/PowerPoint/Excel/EPUB documents, and YouTube videos as clean Markdown via PullMD. Also a fallback when the host's native web research returns poor or noisy results. Do NOT use for GitHub URLs (use gh), Reddit URLs, or JSON API endpoints.

Use when a task will be executed or reviewed through dispatched workers — before the first codex dispatch, subagent spawn, or workflow run of any implementation or review task.

Use when the user explicitly asks to set up, install, configure, wire up, or create the code-comment-writer plugin's extension for the current project. Do not activate as a side effect of a code-comment-writing task.

Use when the user explicitly asks to set up, install, configure, wire up, or create the commit-message-writer plugin's extension for the current project. Do not activate as a side effect of a commit-message-writing task.

Use when the user explicitly asks to set up, install, configure, wire up, or re-sync the subagent-orchestrator plugin's extension for the current project. Do not activate as a side effect of an orchestration task.

Use when writing or editing implementation code — any change that adds, modifies, or removes logic, signatures, or comments on the lines being written. Do NOT activate for retrospective cleanup or audits of existing comments (the code-comment-writer plugin owns those) or for test files and their fixtures (the writing-tests skill owns those).

Use when writing or editing a repository documentation surface — a README, an architecture document, a CLAUDE.md or AGENTS.md pointer file, or a surface the project has registered. Do NOT activate for code comments, commit messages, or PR descriptions.

Use when authoring, editing, or reviewing an automated test — any change to a test file or its fixtures.

Use when the user explicitly asks to set up, install, configure, wire up, re-sync, or migrate the software-writer plugin's extension for the current project. Do not activate as a side effect of a code-, test-, or docs-writing task.

Use when the user asks to generate, write, draft, or validate a commit message, squash commit, or merge commit message. Detects mode (staged, squash, rewrite) from arguments and message context. Do NOT activate during implementation work; only when the user is ready to capture a finished change or validate an existing one.

Evaluates proposed changes to LLM-targeted content (skills, agents, commands) and guides toward corrections over additions. MUST invoke when editing SKILL.md files, modifying agent markdown in agents/, updating command markdown in commands/, adding new sections or instructions, expanding skill content, user says "is this too long", "content bloat", "should I add this", or improving/enhancing skills.

Create, optimize, and debug high-performing prompts for Claude 4 models, GLM 4.7 (Z.ai), and Gemini 3 with production-ready templates and evidence-based techniques. Also optimize LLM-targeted content (skills, agents, instructions, documentation). Use this skill when the user asks to create a prompt, write a prompt, improve a prompt, build a prompt chain, design a system prompt, adapt a prompt for GLM 4.7, adapt a prompt for Gemini, create a Gemini deep research prompt, or needs prompt engineering guidance. Also handles prompt refinement and follow-up modifications.

Use when creating or optimizing a rule file for per-token behavioral steering. Rule files are instruction files that an AI coding assistant automatically loads for a matching user, project, or directory scope; they are NOT skills, agents, or commands. Trigger on "write a rule about X", "create a rules file", "optimize this rules file", "cut ballast from this rule file", or any request to author or refine an auto-loaded file whose purpose is persistent behavioral steering.

Use when the user explicitly asks to write a handoff prompt for a fresh, new, separate, or other session — for example to start a spec's implementation, apply review or report fixes, turn review findings into a change proposal, or continue work — in a session that will have none of this session's context. Invoke only on such an explicit request, never proactively. Produces a self-contained handoff prompt (every needed fact stated inline or reachable by an explicit file reference; the work type, branch, commit and verification policy, and scope deduced from context), then offers to save it to a file or copy it to the clipboard.

Use when the user explicitly asks to write feedback, a report, or a note for another session — typically the upstream session that defined the work this session just executed (it wrote the spec, performed the review, or made the plan), so that session can confirm the work was done correctly and calibrate its future specs and reviews. Invoke only on such an explicit request, never proactively. Produces a calibration note addressed to that session, anchored to the concrete change (branch, commit(s), verification state), then offers to save it to a file or copy it to the clipboard.

Use when the user asks to review, clean up, condense, or improve code comments — in files, a directory, or git changes (a commit, range, branch, or working tree). Detects read-only mode from "check", "analyze", or "audit" verbs. Do NOT activate during implementation work; only when the user wants to clean up or audit comments on existing or changed code.

Write a summary post about repository changes since a given date for Discord and Slack. Analyzes commits on main, groups by conventional-commit scope, and produces separate platform-formatted posts.

Use when reviewing an implementation plan critically before executing it, especially when the user has not read the plan and needs a surface of inconsistencies, rule violations, documentation drift, and questionable scope or guardrail claims. Triggers between writing-plans and executing-plans, or when the user says "review this plan", "audit this plan before I execute it", or "find flaws in this plan".

Configure the native-tools-enforcer plugin on this machine. Detects OS, package manager, and whether bfs/ugrep are installed. Offers to install missing binaries (brew on macOS; prints the sudo install command on Linux). Persists a setting so the plugin always enforces native tools, on request. Use when the user says "set up native-tools-enforcer", "install bfs ugrep", "configure native tools enforcer", or "why is native-tools-enforcer not blocking find/grep".

MUST invoke before any mcp__plugin_reddit-research_reddit-buddy__* tool call, when the user asks to research, search, or investigate anything on Reddit (phrases like "reddit research", "check reddit", "reddit says"), when reddit-buddy results already appear in the conversation, or when web research is prompted (skill asks once whether to include Reddit). Provides the structured scoping / search / drill / synthesis workflow — a 3–6 call budget and truncation-aware interpretation are non-optional; reddit-buddy primitives without this workflow produce noisy, over-truncated, or misattributed findings.

This skill should be used when the user asks to "diagnose this output", "debug this behavior", "analyze what went wrong", "perform root cause analysis", "why did the agent do this", mentions unexpected AI tooling output, or needs to understand why a skill, agent, or command deviated from its intended behavior. Provides gap analysis and targeted introspection questions against source instructions.

Consult OpenAI Codex for fresh analytical perspective. Use when: - Stuck after 3 failed attempts with identical errors (auto-escalation) - Want a second opinion on a problem or approach - Need web research on unfamiliar errors or technologies <example> Context: Claude has tried 3 different approaches to fix a TypeError but the same error persists user: "I've been trying to fix this null pointer error for a while now" assistant: "I've attempted three different fixes but the same error persists. Let me consult Codex for a fresh perspective." <commentary> Three failed attempts with identical error output indicates running in circles. Fresh analytical perspective from a different model may reveal blind spots. </commentary> </example> <example> Context: User wants a second opinion from a different model user: "Ask Codex what it thinks about this approach" assistant: "I'll consult Codex for an independent analysis of this approach." <commentary> User explicitly requests Codex consultation. No failure threshold ne

This skill should be used when the user pastes diagnostic questions, says "introspect", "answer these questions about your behavior", "explain why you did this", "reflect on your behavior", or provides questions generated by the diagnosing skill. Answers introspection questions about session behavior with complete honesty for behavior diagnostics workflows.

Determines project type from context to configure analysis thresholds. Checks prompt, scans documents, or asks user if type cannot be inferred. Outputs project_type for use by python-plan-optimization skill.

6-phase read-only analysis workflow for Python code in markdown documents. Detects design principle violations, code smells, and suggests modern Python improvements. Applies project-type-aware thresholds (POC, MVP, Private, Enterprise, Open Source). Processes one or more documents, generating per-document analysis with summary.