commit-and-push

Use when the user asks to commit and push, publish, ship, or prepare a release commit. Guides staging only intended changes, writing a Conventional Commit, committing, and pushing to origin after veri

SKILL.md

GitHub

Commit and push (compiled harness)

Ship local work only when the user explicitly asks. Pair with release-bump when VERSION / CHANGELOG.md were promoted.

Invoke

# Dry-run inspect (default)
python scripts/harness.py --json

# Release prep: list + run framework verify
python scripts/harness.py --release --run-verify --json

# Only after explicit user request to commit/push:
python scripts/harness.py \
  --execute --commit -m "feat(scope): summary" --json
python scripts/harness.py --execute --push --json

LLM judgment slots

  • Draft Conventional Commit subject/body (commit-conventions).
  • Prefer explicit path staging when unrelated dirty files exist (inspect paths first).

Human / safety (enforced)

  • Harness defaults to dry-run; --execute required for commit/push.
  • Secret-looking paths (.env, secrets.json, keys) block staging.
  • Never modify .git/config, never --no-verify unless user asked.
  • Never force-push main/master unless user asked.
  • Do not amend after a failed hook — new commit instead.

Resolve helper paths from this skill directory. Run project commands from the target workspace.

Похожие навыки: other

limits-colimits

Context management for Claude Code. Hooks maintain state via ledgers and handoffs. MCP execution without context polluti...

Автор: parcadei
3,392

ddttom-allaboutv2-claude-skills-block-collection-and-party

The Block Collection and Block Party are repositories for existing AEM blocks, build tools, code snippets, integration p...

Автор: mattnigh
20

nodnarbnitram-claude-code-extensions-claude-skills-esphome-confi

This skill should be used when the user asks to "create an esphome config", "set up an esp32 device", "configure esphome...

Автор: mattnigh
20