Skip to content

pelagornis/styleguide / .agents/skills/pelagornis-git-workflow

pelagornis-git-workflow

Verified

Perform safe, consistent Git workflows for inspecting changes, preparing commits, pull requests, conflicts, and cleanup. Use when a user asks for Git operations or commit preparation.

Pelagornis Git workflow

Purpose

Help perform Git operations safely and consistently.

Workflow

  1. Inspect the current branch, status, and relevant history before changing Git state.
  2. Keep unrelated user changes separate and stage only files relevant to the requested work.
  3. Use a clear Conventional Commit message when creating a commit.
  4. Inspect the final diff and run relevant verification before committing or preparing a pull request.
  5. Investigate conflicts before resolving them and summarize the resolution.

Output

Report the branch, files affected, commit or pull-request details, and verification performed.

Boundaries

Never force-push, rewrite published history, discard uncommitted changes, or perform destructive cleanup without explicit authorization.

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: 119kUpdated 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