All authors
Claude Skills by rse
github.com/rse58 skills0 installs48 views
- Ase Spec ActivateActivate 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 smal...Votes: 0GitHub stars: 56
- Ase Task StatusGet 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.Votes: 0GitHub stars: 56
- Ase Repo ChangelogUpdate ChangeLog entries in CHANGELOG.md filesVotes: 0GitHub stars: 56
- Ase Repo CommitDetermine commit message for staged Git changes.Votes: 0GitHub stars: 56
- Ase Repo DiffSummarize 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.Votes: 0GitHub stars: 56
- Ase Repo DissectDissect 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.Votes: 0GitHub stars: 56
- Ase Repo MergeMerge 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.Votes: 0GitHub stars: 56
- Ase Repo ResolveResolve 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.Votes: 0GitHub stars: 56