Explore skills
Showing 33331–33360 of 77085 skills
Discover and run the linters and format checks relevant to changed code. Use after code edits or when the user asks for lint, formatting, or static-analysis validation.
aspiers/ai-config
Stars: 14Claude CodeCodexReview changed code for correctness, security, maintainability, and verification gaps. Use when code is ready for independent review or before handoff, staging, or merge.
aspiers/ai-config
Stars: 14Claude CodeCodexCapture durable project or workflow knowledge discovered during work. Use when a mistake, hidden constraint, repeated question, or changed behavior reveals a documentation gap. To root-cause one specific mistake the agent just made and let the user pick fixes, use `learn` (`/learn`) instead.
aspiers/ai-config
Stars: 14Claude CodeCodexReview staged changes and create atomic Git commits whose messages match repository conventions. Use when a tested change is ready to commit, without waiting to be asked, or when the user asks to commit, write a commit message, or finalize already staged work.
aspiers/ai-config
Stars: 14Claude CodeCodexCorrects output that refers to entities by bare identifier, restating it with a human-readable label beside every ID, and keeps that rule for the rest of the conversation. Use when the user invokes `/ids` or `$ids`, or complains that bead IDs, PR numbers, commit SHAs, or ticket keys were given without titles.
aspiers/ai-config
Stars: 14Claude CodeCodexPlan dependency-aware atomic commits for changes that span multiple logical concerns. Use when a refactor, feature, or API change would benefit from reviewable, independently meaningful commit boundaries. To triage an already-dirty working tree and propose commits for existing uncommitted changes, use `planning-commits` instead.
aspiers/ai-config
Stars: 14Claude CodeCodexAudits, installs, pins, approves, updates and removes third-party Orca plugins (orca-plugin.json, the Orca plugin catalog, Git URL installs and development folders), including trusted-worker plugins that reach Orca's runtime socket. Use before installing, enabling, approving or updating any Orca plugin, when asked whether an Orca plugin is safe, and when reviewing Orca plugin updates. For writing an Orca plugin, use Orca's own orca-plugin-authoring guide instead.
aspiers/ai-config
Stars: 14Claude CodeCodexResearches and compares alternatives in a ranked, source-linked HTML matrix with separate criteria, traffic-light cells and multiple feature filters. Use when comparing options, approaches, services, tools, organisations, policies or other alternatives, or requesting a comparison matrix. For FOSS projects, combine with comparing-open-source-projects for its research requirements.
aspiers/ai-config
Stars: 14Claude CodeCodexTriages an already-dirty Git working tree: breaks down every uncommitted change hunk by hunk, separates deliberate edits from tool-written churn, possibly accidental reversions, misplaced scope, and sensitive content, asks the user about the ambiguous cases, and proposes an ordered set of commits plus a list of hunks to hold back. Use when the user invokes `/pc` or `$pc`, asks what they should commit, wants their uncommitted changes broken down, or wants commits proposed for a dirty working tree or pile of accumulated local modifications. To plan commit boundaries for a change before or while implementing it, use `incremental-commits` instead.
aspiers/ai-config
Stars: 14Claude CodeCodexBuilds a clickable before/after screenshot gallery of web UI work, at desktop and phone widths in light and dark, where clicking any screenshot opens the actual page it came from, with a full-length screenshot one link away. Use when showing the user screenshots or previews of UI changes for review, comparing pages before and after a change, or when screenshots handed over were cropped to the first screen. For a single image or page, open it directly as orca-cli-local or open-in-user-browser describes.
aspiers/ai-config
Stars: 14Claude CodeCodexPuts the agent into a cautious production mode for live systems: read-only inspection may proceed, but credentials and out-of-scope personal data need permission first, every state-changing action needs explicit per-action approval with its resource risks and rollback stated, and anything unexpected halts work until the user decides. Use when the user invokes `/prod` or `$prod`, or says they are working on production, a live or customer-facing server, a mail server, or a production database, or asks for care on a system where mistakes affect real users.
aspiers/ai-config
Stars: 14Claude CodeCodexEstablish concise, cross-agent project instructions from repository evidence. Use when initializing or repairing AGENTS.md, CLAUDE.md, related discovery links, or project-specific agent guidance.
aspiers/ai-config
Stars: 14Claude CodeCodexGenerate a Product Requirements Prompt (PRP) from a feature description. Use when starting work on a new feature.
aspiers/ai-config
Stars: 14Claude CodeCodexPrepare and publish upstream issues, feature requests, discussions, pull or merge requests, and patch submissions in the channel the canonical project expects. Use when reporting a problem upstream, requesting a feature, contributing a change, or asking to submit upstream.
aspiers/ai-config
Stars: 14Claude CodeCodexImplements one numbered sub-task from a task list at .ai/[feature]/tasks.md, running linters and tests, without staging, committing, or marking the task complete. Use when asked to carry out a specific sub-task by number, or as the inner step of a larger loop that handles commits separately. For the full loop including commits, use task-orchestration.
aspiers/ai-config
Stars: 14Claude CodeCodexRuns the full implement-and-commit loop over a task list — selects the next incomplete sub-task, implements it, runs linters and tests, marks it done, commits, and repeats until the list is finished. Use when asked to work through a feature's task list at .ai/[feature]/tasks.md unattended, or to keep going until every sub-task is complete. For a single sub-task with no commit, use task-implementation; to stop for approval between each one, use iterative-development.
aspiers/ai-config
Stars: 14Claude CodeCodexDiscover and run tests that provide meaningful evidence for a code change. Use after implementation, before handoff or commit, or when the user asks to validate behavior, including checking a desktop, window-manager, keyboard or other GUI change by hand.
aspiers/ai-config
Stars: 14Claude CodeCodexUse the Xero MCP server — troubleshoot its self-refreshing OAuth2 token file, maintain the local best-of-breed server build, and pick up other operational notes for working with Xero MCP tools. Use when Xero MCP tools fail with authentication errors, before starting any Xero workflow, when adding or updating upstream xero-mcp-server PRs, or for general guidance on Xero MCP usage.
aspiers/ai-config
Stars: 14Claude CodeCodexMakes the agent reconsider a task it just handed back to the human and find a way to do it itself, checking memory, CLI tools, skills, MCP servers, and documentation in turn. Use when the user invokes `/you` or `$you`, or replies that the agent should do something itself rather than asking them.
aspiers/ai-config
Stars: 14Claude CodeCodexInterview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
DevNullLtd/Yuzu
Stars: 19Claude CodeCodexReview Yuzu C++ source changes for C++23 correctness, idiomatic standard-library use, ABI boundaries, threading primitives, and cross-compiler portability across GCC, Clang, MSVC, and Apple Clang. Use for any governance Gate 3 review when `.cpp`, `.hpp`, or `.h` files change.
DevNullLtd/Yuzu
Stars: 19Claude CodeCodexInterview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
DevNullLtd/Yuzu
Stars: 19Claude CodeCodexCreate a concise Product Development Requirement and one or more implementation-sized YYLO Ledger tasks when the user explicitly asks to plan or register work.
Dianel555/DSkills
Stars: 65Claude CodeCodexChart a large planning effort as decision tickets, or work an existing map within the requested scope.
BumpyClock/agent-templates
Stars: 2Claude CodeCodexWrite or edit tests for a voice agent that can run on the Egma platform.
egma-ai/egma
Stars: 146Claude CodeCodexCompress natural language memory files (CLAUDE.md, todos, preferences) into caveman format to save input tokens. Preserves all technical substance, code, URLs, and structure. Compressed version overwrites the original file. Human-readable backup saved as FILE.original.md. Trigger: /caveman-compress FILEPATH or "compress memory file"
stevesolun/ctx
Stars: 593Claude CodeCodexUI/UX design audit with Steve Jobs and Jony Ive design philosophy. Structured protocol for auditing visual hierarchy, spacing, typography, color, motion, glass materials, and interaction consistency.
wmasfoe/md-editor
Stars: 40Claude CodeCodexSearch academic literature and generate research hypotheses
OpenRaiser/NanoResearch
Stars: 1.3kClaude CodeCodexProduce an experiment blueprint from a research hypothesis
OpenRaiser/NanoResearch
Stars: 1.3kClaude CodeCodexencero-systems/incan
Stars: 74Claude CodeCodex