live1,247 agents deployedbuilt by a solo devpowered by hermes
← All skillsSign up to install

git-start

General0 installsUpdated 12d ago
Curatedgardusig

>-

SKILL.md preview

---
name: git-start
description: >-
  Full @git-main → new branch from derived name → full @git-push. Branch naming from Jira/activity/issue number in chat;
  use @gh-issue-view separately for live GitHub issue titles. Does NOT reimplement @git-main; does NOT open PR (@gh-pr).
  User may skip push if explicit.
---

**Normative workflow:** [`read-workflow-workflows`](../../internal/read/workflow/workflows/SKILL.md#git-start-workflow).

# Start (main → new branch from a task)

Normative fences / full matrix: [`read-repo-stream`](../../internal/read/repo/stream/SKILL.md), [`write-workflow-working-tree-align`](../../internal/write/workflow/working/tree/align/SKILL.md).

## Language interaction policy

Always apply [`read-safety-language-interaction-rules`](../../internal/read/safety/language-interaction-rules/SKILL.md) first. Use English by default for all assistant output, including AskQuestion prompts/options, unless the user explicitly requests another full-language response.

## Before batch

**Always run first** (sequential). Complete every applicable row in this table before execution steps in this skill. Skip a row only when its **When** column does not apply.

| Kind | Skill / library | When |
| --- | --- | --- |
| **Required** | [`@git-main`](../main/SKILL.md) | Embedded in this skill before new branch |
| **Recommended** | [`@gh-issue-view`](../../gh/issue/view/SKILL.md) | Branch name from live issue title |
| **Recommended** | [`@git-push`](../push/SKILL.md) | Default publish on new branch (skip only if user says so) |
| **Tooling** | `git` | Repo root |




## Required internal skills

Run after **Before batch** completes (names only; normative fences in linked libraries).

| Library | Role |
| --- | --- |
| `read-workflow-workflows` | See linked library |
| `read-safety-structured-qa` | See linked library |

## Skip & suggestions

| Flag / param | Role |
| --- | --- |
| **`skip=false`** | Root invocation — offer next-step suggestions after **Verification** |
| **`skip=true`** | Nested public-skill child call — no next-step prompt |
| **`SKIP_QA_GIT_START=true`** | Bypass routine write gates for this skill |
| **`SKIP_QA_WRITE=true`** | Shared write-flow Q&A bypass where allowed |
| **`SKIP_SUGGESTIONS=true`** | Suppress next-step suggestions even at root |

High-risk or destructive confirmations still require explicit user confirmation when bypass flags are set.

## Do

- Derive **`$BRANCH`** from Jira key, GitHub issue, or kebab-case activity.
- Run **full** **[`@git-main`](../main/SKILL.md)** with nested optional-suggestion prompting disabled (**`skip=true`**), then create the branch and run **full** **[`@git-push`](../push/SKILL.md)** with nested optional-suggestion prompting disabled (**`skip=true`**) on the new branch—**order and branch-creation recipe** in **`start-workflow`**, not reimplemented here.
- **Default:** publish via **`@git-push`** unless the user explicitly cancels publish.

## Do not

- Reimplement **`@git-main`** (fetch / reset / clean)—delegate to that skill.
- Open or update a PR—use **`@gh-pr`** when ready.
- Skip **`@git-push`** without user saying so (default is publish).

**Expected context (one of):**
- **Jira** — Ticket key (e.g. `TIS-503`, `PROJ-123`) or link. Branch name: lowercase with hyphen, e.g. `tis-503`, `proj-123`, or `tis-503-short-description` if a short description is given.
- **GitHub issue** — Issue number or URL (e.g. `#42`, `https://github.com/owner/repo/issues/42`). Branch name: `42` or `42-short-slug` (e.g. `42-fix-login`) from the issue title if available.
- **Activity / instruction** — Short phrase (e.g. "add user login", "refactor auth"). Branch name: **kebab-case** slug, e.g. `add-user-login`, `refactor-auth`. No spaces; keep it short.

## On invoke

*`@git-start`* — Execute **[`read-workflow-workflows`](../../internal/read/workflow/workflows/SKILL.md#git-start-workflow)** end-to-end. If the user did not give a ticket, issue, or activity, ask: "What's the Jira ticket,