Explore skills
Search every indexed skill by name, description, repository or instructions, then narrow the results.
Showing 14461–14490 of 15434 skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| ase-repo-resolverse/aseResolve the Git merge conflicts of a working directory -- of an in-progress merge, rebase, cherry-pick, revert, stash apply, or of conflict markers left by patch -- carefully and semantically, never losing any change, escalate unresolvable hunks as-is, continue the in-progress operation, and emit a RESOLVED, PARTIAL, NONE, or FAILED verdict. Use when the user calls to "resolve" or "fix" merge conflicts. | Stars: 76 | Updated | Claude CodeCodex | Unverified | Install |
| ase-repo-reviewrse/asePerform a holistic, human-reviewer-style critique of the currently staged Git changes (or, with `--unstaged`, of the unstaged and untracked changes, with `--branch`, of a branch against its base, or, with `--commit`, of a single commit) and emit an approve/reject verdict with prioritized, severity-tagged, line-cited findings. Use when the user wants the staged diff, a branch, or a commit "reviewed", "critiqued", or "code-reviewed". | Stars: 76 | Updated | Claude CodeCodex | Unverified | Install |
| ase-repo-stagerse/aseStage only the part of the current Git working copy changes which belongs to a topic, to the last `CHANGELOG.md` entry, to the last turn, or to the entire session, by picking and, if necessary, splitting hunks, check that the staged state builds on its own, and optionally chain into ChangeLog updating and commit message crafting. Use when the user calls to "stage" only a part of the changes, like "the hunks related to" a topic or "the last turn". | Stars: 76 | Updated | Claude CodeCodex | Unverified | Install |
| ase-repo-taskrse/aseDerive a new task plan from a Git change set -- the staged changes (or, with `--unstaged`, the unstaged and untracked changes, with `--branch`, a branch against its base, or, with `--commit`, a single commit) -- optionally narrowed to a scope topic, by filling its SPECIFICATION (WHAT), DESIGN (HOW), and VERIFICATION (WHEN) sections (or only the focused ones), so that a re-implementation of the task, e.g. after an export to a foreign issue tracker, yields a similar change set. Use when the user wants a change set, branch, or commit "turned into", "described as", or "reverse-engineered into" a "task", "plan", or "issue". | Stars: 76 | Updated | Claude CodeCodex | Unverified | Install |
| ase-spec-activaterse/aseActivate Specification Know-How: load the SpecBook format contract, the SpecBook schema configuration of the project, and the list of specification (SPEC) artifacts into the context, so the specification can be read, queried, explained, and edited ad-hoc in plain conversation. Use *automatically* whenever the user wants to work with the specification files -- asks what the "spec" or "specification" says, wants to "look up", "query", "check", or "explain" specification content, or wants a small ad-hoc change to it -- and no dedicated specification skill (`ase-spec-edit`, `ase-sync-import`, `ase-sync-reconcile`, `ase-sync-export`) is invoked, as those activate the know-how implicitly or need none. | Stars: 76 | Updated | Claude CodeCodex | Unverified | Install |
| ase-spec-editrse/aseEdit Specification: Use when the user wants to "edit" the SpecBook-based specification (SPEC) in one shot from a query, with optional grilling, SpecBook validation, looping, and Git worktree isolation. | Stars: 76 | Updated | Claude CodeCodex | Unverified | Install |
| ase-spec-lintrse/aseLint the SpecBook-based specification (SPEC) for potential quality problems: its syntax, its formatting, its statements, the logical gaps of its model, and its completeness for an implementation. Use when the user wants to "lint" or "check" the "spec" or "specification". | Stars: 76 | Updated | Claude CodeCodex | Unverified | Install |
| ase-sync-exportrse/aseExport the SpecBook-based specification (SPEC) into ready-to-consume renderings like HTML, PDF, normalized Markdown, or JSON. Use when the user wants to "export", "render", or "materialize" the specification. | Stars: 76 | Updated | Claude CodeCodex | Unverified | Install |
| ase-sync-importrse/aseImport information from foreign sources into a set of artifact kinds (the target), generating or updating them to reflect the imported information. Use when the user wants to "import", "ingest", or "bring in" external sources like files, URLs, or pasted text into artifacts like SPEC, CODE, DOCS, TASK, INFR, or OTHR. | Stars: 76 | Updated | Claude CodeCodex | Unverified | Install |
| ase-sync-reconcilerse/aseReconcile one set of artifact kinds (the target) to reflect the current state of another set of artifact kinds (the source), while optionally honoring a filtering hint. Use when the user wants to "reconcile", "sync", "align", or "update" artifacts like SPEC, CODE, DOCS, TASK, INFR, or OTHR against each other. | Stars: 76 | Updated | Claude CodeCodex | Unverified | Install |
| ase-task-assignrse/aseAssign the current or given task plan to oneself or to somebody else, with assigning it to oneself tracking the AI usage (time, tokens, and costs) of the session until the task is given back, which adds the accumulated usage to the usage attachment of the task. Use when the user wants to "assign", "take", "pick up", "give back", "hand over", or "unassign" the "task" or "plan". | Stars: 76 | Updated | Claude CodeCodex | Unverified | Install |
| ase-task-condenserse/aseCondense the current or given task plan by compressing its wording. Use when the user calls to "condense", "compress", "shrink" or "shorten" the "task", "plan", "spec", or "specification". | Stars: 76 | Updated | Claude CodeCodex | Unverified | Install |
| ase-task-deleterse/aseDelete the current or given task plan. Use when the user calls to "delete", "remove" or "clear" the "task", "plan", "spec", or "specification". | Stars: 76 | Updated | Claude CodeCodex | Unverified | Install |
| ase-task-dissectrse/aseDissect the current or given task plan, treated as an epic, domain-wise and logically into cohesive parts and materialize each part as its own separate task plan. Use when the user calls to "dissect", "split", "break up", or "decompose" a large "task" or "plan". | Stars: 76 | Updated | Claude CodeCodex | Unverified | Install |
| ase-task-editrse/aseIteratively edit and refine a named plan for a task through a conversational loop. A new plan is optionally composed along the chosen one of several proposed crafting, refactoring, resolution, or specification approaches. Each round, the current plan is shown and the user is asked whether to keep refining, mark the plan as done, or proceed to the implementation or draft. Use when the user wants to plan a task purely through chat-driven refinement, or wants a plan to "craft" a new feature, "refactor" the code base, or "resolve" a problem (also from a bare analyzer issue id like "P1"). | Stars: 76 | Updated | Claude CodeCodex | Unverified | Install |
| ase-task-estimaterse/aseEstimate the effort of the current, given, or all unestimated task plans as T-shirt sizes (XS, S, M, L, XL) of expected human time, and store it in the "Effort:" frontmatter key, or calibrate the estimation against the actual human time of the finished tasks. Use when the user wants to "estimate", "size", or "gauge the effort" of a "task" or "plan", or to "calibrate" the effort estimation. | Stars: 76 | Updated | Claude CodeCodex | Unverified | Install |
| ase-task-grillrse/aseInterview the user relentlessly about the task plan until reaching a shared understanding, resolving each branch of the question decision tree. Use when the user wants to stress-test a plan, get grilled on their plan, or mentions "grill me" or "grill plan". | Stars: 76 | Updated | Claude CodeCodex | Unverified | Install |
| ase-task-idrse/aseGet or set unique task id <id>. Use when user requests to work on a certain task or wants to know what the current task is. | Stars: 76 | Updated | Claude CodeCodex | Unverified | Install |
| ase-task-implementrse/aseImplement current or given task plan, optionally as an implementation draft attachment only. Use when the user calls to "implement", "realize", "draft", "dry-run", or "test-drive" the "task", "plan", "spec", or "specification". | Stars: 76 | Updated | Claude CodeCodex | Unverified | Install |
| ase-task-integraterse/aseIntegrate the change set or implementation draft of the current or given task plan into its target. Use when the user calls to "deliver" or "apply" the change set or draft of the "task" or "plan". For merging a plain Git branch, use `ase-repo-merge` instead. | Stars: 76 | Updated | Claude CodeCodex | Unverified | Install |
| ase-task-listrse/aseList all available task ids. Use when user wants to see all tasks. | Stars: 76 | Updated | Claude CodeCodex | Unverified | Install |
| ase-task-rebootrse/aseReboot the current or given task plan by re-creating it from scratch. Use when the user calls to "reboot", "recreate" or "refresh" the "task", "plan", "spec", or "specification". | Stars: 76 | Updated | Claude CodeCodex | Unverified | Install |
| ase-task-renamerse/aseRename the current or given task plan. Use when the user calls to "rename", "move" or "relabel" the "task", "plan", "spec", or "specification". | Stars: 76 | Updated | Claude CodeCodex | Unverified | Install |
| ase-task-researchrse/aseResearch a topic in depth for the current or given task plan, by combining Internet/Web search with a grounding in the source artifacts of the project, and append the resulting research report to the "research" attachment of the task, optionally refining the plan by its recommendations. Use when the user wants to "research", "investigate", or "look into" a topic for a "task" or "plan". | Stars: 76 | Updated | Claude CodeCodex | Unverified | Install |
| ase-task-statusrse/aseGet or set the lifecycle status of the current or given task plan. Use when the user wants to know or change the "status" or "state" of the "task" or "plan", e.g. to "close", "shelve", "cancel", or "re-open" it. | Stars: 76 | Updated | Claude CodeCodex | Unverified | Install |
| ase-task-viewrse/aseView current or given task plan. Use when the user calls to "view", "show" or "see" the "task", "plan", "spec", or "specification". | Stars: 76 | Updated | Claude CodeCodex | Unverified | Install |
| brainstormoprogramadorreal/optimus-claudeRuns a structured design conversation — clarifies intent, proposes 2-3 approaches with trade-offs, iterates the design — and writes a user-approved engineering spec to docs/specs/ that /optimus:tdd auto-detects. No implementation happens until the spec is approved. With the scaffold argument, creates docs/product/ steering skeletons instead (never overwrites, authors no content). Recommends /optimus:init first. | Stars: 75 | Updated | Claude CodeCodex | Unverified | Install |
| code-reviewoprogramadorreal/optimus-claudeReviews local changes, an open PR/MR, or a branch diff for bugs, security issues, and violations of the project's own coding guidelines, through review lenses applied inline on a small diff or in parallel agents on a larger one. Excludes style and linter-catchable issues. Read-only: applies fixes or posts PR/MR comments only on explicit approval. For an iterative auto-fix loop, use /optimus:deep review. | Stars: 75 | Updated | Claude CodeCodex | Unverified | Install |
| commitoprogramadorreal/optimus-claudeStages, commits, and optionally pushes local changes with a Conventional Commits message — always previews and confirms first, and offers a feature branch on protected branches. Modes: "suggest" proposes a message without committing (read-only); "branch [description]" creates and switches to a conventionally named branch, never committing or altering local changes. Multi-repo aware. | Stars: 75 | Updated | Claude CodeCodex | Unverified | Install |
| deepoprogramadorreal/optimus-claudeRuns an iterative auto-fix loop on a chosen target — review, refactor, or coverage — dispatching the base skill into fresh subagent contexts per iteration, applying fixes automatically without per-change approval, running tests with bisection on failure, and checkpoint-committing until convergence or the cap. Requires /optimus:init and a test command in .claude/CLAUDE.md. | Stars: 75 | Updated | Claude CodeCodex | Unverified | Install |