Skip to content

nickgallick/perlantir-fleet / skills/nick-git-ops

nick-git-ops

Verified

Git workflow automation and guidance for Nick's multi-project workflow, especially repos in ~/Projects/. Use when doing git commits, status checks, branching, merges, rebases, reviewing dirty working trees, cleaning branch flow, or managing multiple repos. Enforce conventional commits and safer git habits.

Nick Git Ops

Use this as the default Git workflow skill for Nick.

Purpose

Make git work cleaner, safer, and faster across multiple projects.

Core use cases

  • check repo status quickly
  • manage multiple repos in ~/Projects/
  • create clean branches
  • write conventional commit messages
  • decide merge vs rebase
  • prepare changes before push
  • reduce accidental messy git operations

Hard rules

  • Follow conventional commits
  • Never commit secrets or .env files
  • Check status before risky git operations
  • Prefer readable branch names and history
  • Be explicit about repo context when multiple projects exist

Conventional commit defaults

Use formats like:

  • feat: add signup flow
  • fix: resolve dashboard loading bug
  • refactor: simplify auth guard
  • chore: update dependencies
  • docs: clarify setup notes
  • test: add login flow coverage

Standard workflow

  1. Confirm current repo and branch
  2. Review working tree status
  3. Review staged vs unstaged changes
  4. Choose branch action if needed
  5. Create a clear conventional commit message
  6. Push cleanly
  7. Note any merge/rebase risk before acting

Multi-project rules

When working across projects:

  • identify the exact repo first
  • avoid assuming current directory is the intended repo
  • prefer repo summary before batch work
  • call out dirty repos clearly

Merge vs rebase defaults

  • use merge when preserving branch history matters
  • use rebase when cleaning local feature history before merge
  • avoid rewriting shared history casually

References

  • Read references/commit-conventions.md for commit style
  • Read references/branching.md for naming and branch hygiene
  • Read references/merge-rebase-guide.md when choosing history strategy
  • Read references/multi-repo-workflow.md for ~/Projects/ habits
  • Read references/safety-checklist.md before risky git operations

Bundled scripts

  • scripts/repo_status_summary.sh — summarize git status across repos
  • scripts/generate_commit_message.sh — generate conventional commit stubs
  • scripts/create_branch_name.sh — generate readable branch names
  • scripts/pre_push_checklist.sh — create a pre-push sanity checklist
planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies.Stars: 108kUpdated Claude CodeCodexVerifiedInstall
meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要".Stars: 108kUpdated Claude CodeCodexVerifiedInstall