Skip to main content
Run any Skill in Manus
with one click
jsiovn
GitHub creator profile

jsiovn

Repository-level view of 31 collected skills across 1 GitHub repositories.

skills collected
31
repositories
1
updated
2026-06-29
repository map

Where the skills live

Top repositories by collected skill count, with their share of this creator catalog and occupation spread.

repository explorer

Repositories and representative skills

cleanup-worktree
software-developers

Remove a sibling git worktree created by `executor-task-worktree`, `executor-epic-task-worktree`, `executor-epic-sequential-worktree`, or `create-new-worktree` once follow-up work (review comments, screenshots, CI fixes) is done. Lists existing worktrees, confirms which to remove, verifies the branch is safe to drop (PR merged or user-approved), removes the worktree, prunes stale entries, and optionally deletes the local branch.

2026-06-29
executor-epic-sequential
software-developers

Run every ready child bead of one epic end-to-end, sequentially, on a single epic branch (epic/<epic-bead-id>). Each bead executes in a fresh headless `claude -p` session so context never carries between tasks; a failed bead is marked blocked and skipped (along with its dependents) and the run continues; finishes with one PR from the epic branch to the default branch. Use when the user wants to deliver a whole epic unattended as one branch and one PR instead of running one bead at a time.

2026-06-29
executor-epic-sequential-worktree
software-developers

Use when you want to deliver a whole epic unattended as ONE branch and ONE PR WITHOUT disturbing in-flight work in the main checkout. Runs every ready child bead of one epic sequentially in a fresh sibling git worktree checked out on the epic branch (epic/<epic-bead-id>) so the main working tree is never touched — each bead executes in its own fresh headless `claude -p` session (clean context per task), committing directly onto the single epic branch; a failed bead is marked blocked and skipped (along with its dependents) and the run continues; finishes with one PR from the epic branch to the default branch and leaves the worktree in place for follow-up (review comments, CI fixes). Use the `cleanup-worktree` skill to remove the worktree once the PR has landed.

2026-06-29
executor-epic-task
software-developers

Run a full executor cycle for one bead on a fresh feature branch off its parent epic branch (epic/<epic-bead-id>): stash any in-flight work, switch to the epic branch, pull, create feat/<bead-id>-<short-slug>, execute the bead end-to-end, then push and open a PR targeting the epic branch. Use when the user wants a single bead delivered as its own PR into an in-progress epic branch instead of main.

2026-06-29
executor-epic-task-worktree
software-developers

Run a full executor cycle for one bead in a fresh git worktree off its parent epic branch (epic/<epic-bead-id>): leaves the main working tree completely untouched, creates a sibling worktree at ../<repo>-feat-<bead-id>, executes the bead end-to-end, pushes, opens a PR targeting the epic branch, and leaves the worktree in place for follow-up work (review comments, screenshots, CI fixes). Use when an epic has its own integration branch and the main tree has active work that must not be disturbed. Use the `cleanup-worktree` skill to remove the worktree once follow-up work is done.

2026-06-29
prune-local-branches
software-developers

Delete local git branches whose upstream was removed from origin, and tear down any sibling git worktree still attached to them. Use when the user asks to clean up stale, pruned, merged, or deleted remote branches locally — including the worktrees the executor-*-worktree / create-new-worktree flows leave behind.

2026-06-29
rebase-and-push
software-developers

Use when the user wants to rebase the current branch onto its up-to-date base and force-push with lease — e.g. "rebase this branch", "rebase and push", "bring my branch up to date with the epic", "bring the epic branch up to date with main". Works on a feature branch (rebased onto its parent epic branch epic/<epic-bead-id> or the default branch main/master) and on an epic branch itself (rebased onto the default branch). Detects the base, rebases onto the matching origin ref, resolves conflicts, runs verification-before-completion, then pushes with --force-with-lease. Maintenance op; refuses to run on the default branch, and stops to confirm before rebasing an epic branch that still has open child PRs targeting it.

2026-06-29
create-new-worktree
software-developers

Use when the user wants to spin up a fresh sibling git worktree from a branch name or a bead id/name, off the origin default branch — seed its `.env*`, optionally copy other git-ignored working files, install dependencies, and ensure Beads is operational inside it — then stop and hand off to an executor. Setup only: never claims the bead, plans, or implements. Use the `cleanup-worktree` skill to remove the worktree afterward.

2026-06-21
Showing top 8 of 31 collected skills in this repository.
Showing 1 of 1 repositories
All repositories loaded