aidenreed937/comet
Overview
This skill provides a concise, practical workflow for Git and GitHub operations in Flutter projects, covering branch management, commits, pushes, PRs, rebases, and merges. It enforces safe practices (no direct main pushes), Conventional Commits, and recommends using a child agent for heavy Git tasks to keep the main conversation context small. The goal is reliable, auditable branch workflows and clean history for Flutter codebases.
How this skill works
When invoked for Git work (commit, push, PR, rebase, merge, repo creation), the skill outlines the exact commands and checks to run. It recommends executing heavy operations inside a child agent that runs git/gh commands and returns compact results (commit hashes, PR URLs) to the main session. The skill also enforces guardrails: run quality checks, rebase onto latest main, resolve conflicts, and use squash merges for PRs.
When to use it
- Creating a new feature, fix, hotfix, refactor, or docs branch
- Preparing and creating a Pull Request to merge into main
- Rebasing a branch onto latest main or resolving rebase conflicts
- Committing and pushing changes while following commit message standards
- Creating a new GitHub repository and setting default branch
Best practices
- Never push directly to main; always merge via PR after review and checks
- Use child agent for operations that read diffs/logs (commit, PR creation, rebase, merge) to save main-context tokens
- Follow Conventional Commits: <type>(<scope>): <subject>; include tests and summary in PR body
- Run flutter analyze, dart format, and flutter test before creating PRs
- When rebasing, use git push --force-with-lease and prefer squash merge to keep history linear
Example use cases
- Start a feature branch: checkout main, pull, git checkout -b feature/<name>, develop, rebase frequently
- Finish work: run analysis/tests, rebase to origin/main, resolve conflicts, force-push, then create gh PR with summary and test plan
- Emergency hotfix: branch from main, fix, push, create PR titled hotfix:, merge, then rebase other branches onto main
- Repository creation: gh repo create <name> --private --source=. --push and set default branch to main
FAQ
Child agents run git/gh commands and parse diffs without consuming the main session context, returning only compact results like commit hashes and PR links.
What commit format should I use?
Use Conventional Commits: <type>(<scope>): <subject> (e.g., feat(auth): add token refresh). Include a short summary and, if needed, a longer body with test plan and references.
