git

Solid

Open Harness git workflow: issues, branches, commits, PR titles/bodies, changelog discipline, worktrees, branch catch-up, stacked PRs, releases, and post-push CI checks. TRIGGER when: any chat mentions git, GitHub, branches, commits, pushes, pulls, PRs, issues, worktrees, merge conflicts, dirty workspaces, changelog entries, release branch/tag workflow, or project git conventions.

AI & Automation 38 stars 3 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 83/100

Stars 20%
53
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Git Workflow ## Always Load This Skill Any time a chat mentions git, GitHub, branches, commits, pushes, pulls, PRs, issues, worktrees, merge conflicts, releases, changelog entries, or dirty workspace cleanup, read this skill before acting. Treat it as the source of truth for routing changes to the right remote and for preserving local work safely. ## Repository and Memory Routing This checkout commonly has two remotes: - `upstream` → `mifunedev/openharness` (public template/canonical upstream) - `origin` → your fork of `openharness` (private/operator fork) Before every commit or PR, inspect the changed paths and choose the remote explicitly. Do not assume `origin` is the public target. **Memory is private. Never commit memory artifacts to the public upstream repo.** Anything under `.oh/memory/` — especially `.oh/memory/MEMORY.md`, dated session logs, retro notes, and private lessons — belongs only in your private fork (`origin`) unless the operator gives an explicit one-off exception. If a public PR branch contains `.oh/memory/` changes, remove them before pushing/creating the PR, and preserve them separately on an `origin`-only branch or PR. Use this quick guard before pushing to `upstream`: ```bash git diff --name-only upstream/development...HEAD | grep '^.oh/memory/' \ && { echo "BLOCK: memory changes must go to origin only"; exit 1; } ``` ## Issue Titles Format: `<prefix>(<issue#>): <shortdesc>` `<prefix>` ∈ `feat` · `bug` · `task` · `audit` · `skill` · `a...

Details

Author
mifunedev
Repository
mifunedev/openharness
Created
5 months ago
Last Updated
today
Language
TypeScript
License
Apache-2.0

Similar Skills

Semantically similar based on skill content — not just same category