start-change

Files (2)

• SKILL.md
• openai.yaml · agents/

SKILL.md (first lines)

# Start Change

1. Inspect the working tree and current branch. Preserve unrelated user changes.
2. Fetch `origin`. Create the branch from the latest `origin/develop` using exactly one of:
   - `feature/<kebab-title>` for new behavior
   - `fix/<kebab-title>` for a defect
   - `chore/<kebab-title>` for maintenance
   - `chore/updates-YYYY-MM-DD` for a coordinated group of multiple tasks implemented that day; merge it to
     `develop` in one pull request after the group is ready
3. Use `develop` as the feature base and pull-request target. Do not directly push `develop` or `main`.
   Do not block ordinary feature work on `develop` containing `main`; reconcile main-only changes back into
   `develop` through a dedicated pull request when that integration is needed.
4. State the target branch (`develop`) and the validation expected for the scope. For release work, use `release-macos-plugin` and promote `develop` to `main`.
5. Before handoff, synchronize with `origin/develop` and resolve conflicts on the feature branch. Preserve a linear history.

Use a task-specific branch for isolated work. `develop` consolidates related work, but the final promotion to
`main` remains subject to its required checks. Use Conventional Commit subjects. Treat global-capture changes as
privacy-sensitive: never log keystroke contents and preserve the actionable Accessibility warning.

From brendanwilliam/hd-obs, GPL-2.0.

More from brendanwilliam/hd-obs