← all publishers

mgoodness

@mgoodness source repo

Report this profile Claim this profile

• 8 skills
• 0 followers
• 9 hours ago last updated

1. ▌
   Go CI · mgoodness

   The Go-specific band of a GitHub Actions release pipeline: GoReleaser build recipe, Go checks for a required CI job, golangci-lint scoping, and go.mod/toolchain judgment calls. Use when writing or reviewing a Go CI workflow, `.goreleaser.yaml`, or golangci-lint config. Defers semver rules to `go-release`, release cutting to `release-please`, and repo hardening to `repo-hardening`.
   0 installs
2. ▌
   Split Commits · mgoodness

   Split a dirty working tree into well-scoped Conventional Commits, staged and proposed for approval before anything is committed. Use when the user wants to split or organize pending changes into commits, turn a messy working tree into clean commits, or asks for a commit plan before committing.
   0 installs
3. ▌
   Cleanup Branch · mgoodness

   Clean up a branch and its associated worktree, remote ref, and local tracking branch. Use when the user wants to clean up after a PR is merged, or mentions "delete worktree" or "delete branch".
   0 installs
4. ▌
   Release Please · mgoodness

   Wire release-please to cut versioned releases automatically from Conventional Commits. Use when setting up or reviewing `release-please-config.json`, `.release-please-manifest.json`, or the release-please workflow. Covers the tag-trap (component in tag), the loop-trap (`GITHUB_TOKEN`-authored push), and the draft-trap (draft releases without forced tag creation). Defers App-token mechanics to `github-app-token`, hardening to `repo-hardening`, and build recipes to a language skill (e.g. `go-ci`).
   0 installs
5. ▌
   Repo Hardening · mgoodness bundle

   Harden a GitHub repo so required checks and automated merges are actually safe: rulesets, merge settings, Dependabot with auto-merge, immutable releases, and Actions security practices (SHA pinning, `pull_request_target` hygiene, token scoping). Use when configuring or auditing a ruleset, merge settings, Dependabot, auto-merge, immutable releases, or when zizmor/actionlint flags a workflow. Defers CI content to a language skill (e.g. `go-ci`), release-please to `release-please`, and App-token mechanics to `github-app-token`.
   0 installs
6. ▌
   Github App Token · mgoodness

   Mint a GitHub App installation token to replace the default `GITHUB_TOKEN`. Use when a workflow's push/tag/PR needs first-party identity, a downstream workflow silently never fires after a bot-authored push (loop-trap), a bot PR's checks are stuck needing manual approval (gate-trap), or re-establishing bot identity downstream (actor-override). Defers ruleset hardening to `repo-hardening` and release-please wiring to `release-please`.
   0 installs
7. ▌
   Spin Up Worktrees · mgoodness

   Open one or more git worktrees, each in its own nested herdr workspace — a single task or several in parallel, with or without an associated ticket. Use when the user wants to work on a ticket/issue/task in its own worktree, mentions "open a worktree (or worktrees) for this", "spin up worktrees", or wants several worktrees ready in parallel.
   0 installs
8. ▌
   Agent Context Branch · mgoodness

   Preserve repo-wide agent context docs (AGENTS.md, CLAUDE.md, CONTEXT.md, docs/adr, or similar design/domain docs) on a dedicated branch off the default branch, separate from feature-branch code, so they can be pulled into other worktrees. Use when the user wants to preserve context docs across worktrees, keep design docs out of feature-branch or default-branch commits, or sync a doc correction back onto that branch.
   0 installs