# Help Gnadd

> >-

- **Type:** Skill
- **Install:** `agentstack add skill-alexhagemeister-gnadd-help-gnadd`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [AlexHagemeister](https://agentstack.voostack.com/s/alexhagemeister)
- **Installs:** 0
- **Category:** [Developer Tools](https://agentstack.voostack.com/c/developer-tools)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [AlexHagemeister](https://github.com/AlexHagemeister)
- **Source:** https://github.com/AlexHagemeister/gnadd/tree/main/skills/help-gnadd

## Install

```sh
agentstack add skill-alexhagemeister-gnadd-help-gnadd
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# GNADD Help

Provide lightweight orientation for Git-Native Agent-Driven Development (GNADD).
Do not run git commands from this skill; route mechanics to the operational
skills.

## Core Model

- GitHub is the system of record: issues capture intent, branches hold work, PRs
  record what shipped, and git history is the audit trail.
- The seven operational skills drive the loop: `prime-gnadd`, `new-issue-gnadd`,
  `start-issue-gnadd`, `commit-gnadd`, `resolve-issue-gnadd`,
  `quickfix-gnadd` (the no-issue fast path for trivial changes), and
  `yolo-gnadd` (autonomous full-loop on a decided unit; explicit invocation
  only). Their git mechanics run through a bundled deterministic script
  (`gnadd.sh`), not improvised commands.
- Enforcement is layered, lowest layer that can hold each invariant: GitHub
  server rules (`gnadd init` — squash-only merges, PR-required main), the
  script (ff-only syncs, divergence halts, gated cleanup), the skills
  (judgment and conversation), and the human (reading the diff before merge).
- Recovery from bad states has a sanctioned path: `gnadd.sh doctor` (bundled
  with `prime-gnadd`) diagnoses and offers lossless fixes. Never improvise
  `reset`/`force` recoveries.
- The user's load-bearing job is to describe desired behavior, answer scope
  questions, and read diffs before merge.

## Describe vs Track

Files that describe stable truth are fine. Files that track mutable state should
not exist.

- Keep: README vision, project conventions, stable reference docs.
- Avoid: task lists, progress files, maintained plans, status checklists.
- Test: would the agent need to keep this file up to date? If yes, that state
  belongs in GitHub issues, PRs, branches, or commits instead.

## Skill Router

- Adopt or realign a repo: use `/audit-gnadd`.
- Start a session or inspect state: use `/prime-gnadd`.
- Capture new work: use `/new-issue-gnadd`.
- Begin or resume issue work: use `/start-issue-gnadd `.
- Save progress on an issue branch: use `/commit-gnadd`.
- Verify, PR, merge, and clean up: use `/resolve-issue-gnadd`.
- Land one trivial fix (typo, doc line) without an issue: use `/quickfix-gnadd`.
- Run a decided issue or quickfix end-to-end without mid-loop gates: use
  `/yolo-gnadd ` (never auto-invoked).
- Diagnose or recover from a bad git state (diverged main, stashes,
  leftovers): run `gnadd.sh doctor` from the `prime-gnadd` skill's directory.
- Set up server-side rails on a new repo: `gnadd.sh init` (squash-only
  merges, branch ruleset on main; `--ci` adds a test workflow stub).
- If a git operation seems needed and no skill covers it, ask for a
  skill-shaped path before improvising raw git commands.

## Deep Reference

For startup guidance, file-hygiene questions, rationale, or edge cases not
covered here, fetch the canonical guide from this pinned URL:

https://raw.githubusercontent.com/AlexHagemeister/gnadd/v0.3.0/GNADD.md

This URL is pinned to a commit, not `main`, so installed skills do not drift with
unreleased guide changes. The pin is rewritten by `scripts/release.sh` at release
time — do not hand-edit it out of band.

## Closing Guidance

Do not nudge after every answer. Match nudge depth to user intent:

- **Purely informational** (describe-vs-track, "which skill does X?", rationale questions): no nudge — the answer stands alone.
- **Routing toward action** ("how do I start?", "where should this state live?"): light nudge — one skill pointer (e.g. `/prime-gnadd`, `/new-issue-gnadd`), no full loop recap.
- **Session bootstrap** ("I'm new here", end-to-end workflow orientation): full nudge toward `/prime-gnadd` to see live repo state.

When nudging, keep it to a sentence with an invitational option. Do not restate the skill router table.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [AlexHagemeister](https://github.com/AlexHagemeister)
- **Source:** [AlexHagemeister/gnadd](https://github.com/AlexHagemeister/gnadd)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-alexhagemeister-gnadd-help-gnadd
- Seller: https://agentstack.voostack.com/s/alexhagemeister
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.