Explore skills
Showing 18961–18990 of 37382 skills
Determine commit message for staged Git changes. Use when the user asks to "give", "write", "craft", "suggest", or "propose" a "commit message", or wants to know how to "describe" or "phrase" the staged changes for a commit.
rse/ase
Stars: 76Claude CodeCodexSummarize the currently staged Git changes as a human-readable, intent-grouped narrative. Use when the user wants a concise and brief report of what changed and why. Optionally can check the diff for intent coherence and show a risk and blast radius report.
rse/ase
Stars: 76Claude CodeCodexDissect the current Git change set, treated as an epic, domain-wise and logically into cohesive parts and materialize each part in its own dedicated Git WorkTree. Use when the user calls to "dissect", "split", "break up", or "decompose" a large change set into atomic, separately committable parts.
rse/ase
Stars: 76Claude CodeCodexMerge a Git source branch, including its still uncommitted changes, into a target branch through a regular merge, a rebase with fast-forward, or a squash merge, resolving merge conflicts semantically, check that the source branch landed, and emit a MERGED, CONFLICT, or FAILED verdict. Use when the user calls to "merge", "integrate", or "land" a branch.
rse/ase
Stars: 76Claude CodeCodexResolve 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.
rse/ase
Stars: 76Claude CodeCodexStage 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".
rse/ase
Stars: 76Claude CodeCodexDerive 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".
rse/ase
Stars: 76Claude CodeCodexActivate 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.
rse/ase
Stars: 76Claude CodeCodexEdit 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.
rse/ase
Stars: 76Claude CodeCodexExport 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.
rse/ase
Stars: 76Claude CodeCodexImport 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.
rse/ase
Stars: 76Claude CodeCodexReconcile 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.
rse/ase
Stars: 76Claude CodeCodexAssign 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".
rse/ase
Stars: 76Claude CodeCodexCondense 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".
rse/ase
Stars: 76Claude CodeCodexDelete the current or given task plan. Use when the user calls to "delete", "remove" or "clear" the "task", "plan", "spec", or "specification".
rse/ase
Stars: 76Claude CodeCodexDissect 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".
rse/ase
Stars: 76Claude CodeCodexIteratively 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").
rse/ase
Stars: 76Claude CodeCodexEstimate 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.
rse/ase
Stars: 76Claude CodeCodexInterview 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".
rse/ase
Stars: 76Claude CodeCodexGet 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.
rse/ase
Stars: 76Claude CodeCodexImplement 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".
rse/ase
Stars: 76Claude CodeCodexIntegrate 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.
rse/ase
Stars: 76Claude CodeCodexList all available task ids. Use when user wants to see all tasks.
rse/ase
Stars: 76Claude CodeCodexReboot 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".
rse/ase
Stars: 76Claude CodeCodexRename the current or given task plan. Use when the user calls to "rename", "move" or "relabel" the "task", "plan", "spec", or "specification".
rse/ase
Stars: 76Claude CodeCodexGet 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.
rse/ase
Stars: 76Claude CodeCodexView current or given task plan. Use when the user calls to "view", "show" or "see" the "task", "plan", "spec", or "specification".
rse/ase
Stars: 76Claude CodeCodexBuild and maintain a structured LLM-generated wiki for any codebase. Use when the user asks to analyze/understand/document a codebase, build a code wiki, create project documentation from source, or update an existing .llm-wiki. Triggers on phrases like "build wiki", "analyze this codebase", "document this project", "update wiki", "llm-wiki", or when entering an unfamiliar project that has no .llm-wiki yet.
staruhub/ClaudeSkills
Stars: 739Claude CodeCodexUse once a month, or when the platform feels slow, heavy or cluttered, to review the whole platform from the query logs and the repo, and propose improvements with effort and risk.
DataWithBaraa/claude-code-data-engineering-skills
Stars: 102Claude CodeCodexUse when a new source is connected or a source changes how it delivers, to write the data contract with the source system, the format, the schema, the quality rules, the delivery, the owner and the change process.
DataWithBaraa/claude-code-data-engineering-skills
Stars: 102Claude CodeCodex