dstack-git

Plugin dstack-git from marketplace dstack in gosuda/dalcom-skills. Commands read from the repo's manifest — 3 days ago.

Skills (15)

• atomic-issues-prs

  Use when the user says "atomic PRs" or requests one issue or PR per logical change. Don''t use for single-change pushes or uncommitted change-sets.

• commit-push-current

  Use when a human explicitly asks to commit and push to the checked-out branch with no branch creation and no pull request. Not for the default branch: use commit-push-main; not for a pull request: use commit-push-pr.

• commit-push-main

  Use when a human explicitly asks to commit and push directly to the default branch, with no feature branch and no pull request. Not for another checked-out branch: use commit-push-current.

• gate-and-merge

  Use when landing a queue of open PRs: gate each PR, sweep its review feedback to root cause, then merge, repair, hold, or close it. Human-only.

• git-branchless

  Use when asked for multi-commit stack edits, rebases, fixups, or stacked-PR publishing with branchless git idioms. Not for plain-git workflows in repos without branchless.

• git-cleanup

  Use when the user explicitly invokes branch or worktree cleanup for a repo with accumulated local branches. Don''t use for remote branch deletion or force-push operations.

• issue-triage

  Use when a human invokes triage on a new configured Slack issue report. Not for triaging reports from other channels or posting more than one verdict.

• make-pr-easy-to-review

  Use when a human explicitly asks to reshape or annotate one pull request for review. Don''t use for pushing the rewritten branch or mutating any remote.

• modernize

  Use when a human explicitly asks whether an aging pull request should still land, whether an old PR should be rebased, or whether a stale branch should be revived. The skill proves intent against the current base and never force-pushes or closes a PR.

• post-merge-cleanup

  Use when a landed merge, release, or completed change needs its cleanup surface reconciled. Scans for stale TODOs, deprecations, unused flags, and doc gaps. Not for unrelated refactoring.

• propose-issue

  Use when the user asks to propose an issue, file or open a bug report, or turn a reported defect into a tracked issue. Not for fixing the defect, triaging existing issues, or reviewing PRs.

• resolve-merge-conflicts

  Use when a merge, rebase, cherry-pick, or stash pop stops on conflicts. Not for people-mediation conflicts.

• triage

  Use when issues or external pull requests must move through a category and state machine with verification, grilling, and agent-ready briefs. Not for Slack channel reports (use issue-triage).

• watch-and-repair-pr

  Use when a human or autowatch explicitly invokes one watcher cycle that fixes, replies, resolves, and pushes review feedback on the open pull request or merge request own branch and waits for every expected review until the request is clean or blocked. Not for merge, force-push, or work outside the

• worktree

  Use when work needs an isolated git worktree: new work, an existing ref, a gated feature workspace, a manifest-tracked loop run, or a candidate patch captured without touching the current checkout. Not for plain branches: work in the current checkout.

Similar plugins