commit
Wraps up work by syncing documentation, committing, pushing, and opening a pull request. Use when committing code, finishing a task, pushing changes, or creating a PR.
What this skill does
# Commit ## Step 1: Require Commit Config Check if `.agents/commit.config.yml` exists. - If exists, continue to step 2 - If not, follow `references/config-setup.md` to create it, then continue ## Step 2: Gather Context Run each command separately: 1. `git diff --staged` 2. Only if step 1 had NO output: `git diff` 3. `git log --oneline` ## Step 3: Determine Staging - If `git diff --staged` has output -> use as-is (user curated manually) - If empty -> run `git add -A` to stage everything ## Step 4: Sync Documentation 1. Read `files` from `.agents/commit.config.yml` 2. Find staged `*.md` files not in the config that could be documentation (excluding `skills/`), detect their update condition, register them 3. For each tracked file, evaluate whether `update_when` is met by staged changes 4. Read and update every file whose condition is met 5. If new files were registered in step 2, persist the updated config ## Step 5: Stage Documentation ```bash git add <updated-doc-files> ``` ## Step 6: Generate and Execute Commit **Subject:** semantic commit format (`feat:`, `fix:`, `refactor:`, `docs:`, `chore:`, `test:`, `ci:`, `perf:`, `style:`, `build:`). Lowercase imperative, no period, max 70 chars. Use scope when it adds clarity. **Body:** explain **why** — motivation, trade-offs, decisions. State breaking changes explicitly. **References:** issue/ticket refs on their own line (e.g., `Closes #142`). Execute with HEREDOC: ```bash git commit -m "$(cat <<'EOF' feat: subject line describing what changed Body explaining why this change was made. Closes #issue (if applicable) EOF )" ``` ## Step 7: Push ```bash git push -u origin HEAD ``` ## Step 8: Pull Request Only if branch was pushed in step 7. 1. Run `git branch` — if on `main`, stop 2. Generate PR title and body: ```bash git log <base-branch>..HEAD --oneline git diff <base-branch>...HEAD ``` 3. Create PR: ```bash gh pr create --title "<title>" --body "$(cat <<'EOF' ## Summary <bullet points from commit analysis> ## Test plan <checklist> EOF )" ``` ## Acceptance checklist - [ ] Commit config exists at `.agents/commit.config.yml` - [ ] Documentation synced with staged changes - [ ] Commit message follows semantic format with body - [ ] Changes pushed to remote - [ ] PR created (if not on main)
Related in Productivity
gitea-workflow
IncludedOrchestrate agile development workflows for Gitea repositories using the tea CLI. Use when working with Gitea-hosted repos and asking to 'run the workflow', 'continue working', 'what's next', 'complete the task cycle', 'start my day', 'end the sprint', 'implement the next task', or wanting guided step-by-step development assistance. Keywords: workflow, orchestrate, agile, task cycle, sprint, daily, implement, review, PR, standup, retrospective, gitea, tea.
microsoft-graph-gateway
IncludedRoute Microsoft Graph work in this workspace. Use when users want to read or write Outlook mail, calendar events, contacts, OneDrive or SharePoint files, Teams, Planner, To Do, users, groups, directory data, or arbitrary Microsoft Graph endpoints from VS Code. Prefer WorkIQ for common read scenarios. Use Microsoft Graph for write actions and gap-read scenarios that need exact Graph properties, filters, permissions, or endpoints.
copilotkit
IncludedUse when building with CopilotKit — setup, development, integrations, debugging, upgrading, or contributing. Routes to the appropriate specialized skill based on the task.
wordly-wisdom
IncludedProvides calibrated decision analysis using Charlie Munger-style multiple mental models, inversion, incentive mapping, circle-of-competence checks, misjudgment audits, second-order effects, and forecast updates. Use when the user asks for an oracle take, a hard call, a decision memo, a premortem, an outside view, a red-team, a sanity-check, what am I missing, think this through, or wants a strategy, hire, investment, plan, product, partnership, or major life choice analysed. Avoid for simple factual lookups or time-sensitive legal, medical, or market questions without fresh evidence.
swain-session
IncludedSession management and project status dashboard. Owns the full session lifecycle (start/work/close/resume), focus lane, bookmarks, worktree detection, and tab naming. Also serves as the project status dashboard — shows active epics, progress, actionable next steps, blocked items, tasks, GitHub issues, and recommendations. Worktree creation is deferred to swain-do task dispatch (SPEC-195). Triggers on: 'session', 'status', 'what's next', 'dashboard', 'overview', 'where are we', 'what should I work on', 'show me priorities', 'bookmark', 'focus on', 'session info'.
gandi
IncludedComprehensive Gandi domain registrar integration for domain and DNS management. Register and manage domains, create/update/delete DNS records (A, AAAA, CNAME, MX, TXT, SRV, and more), configure email forwarding and aliases, check SSL certificate status, create DNS snapshots for safe rollback, bulk update zone files, and monitor domain expiration. Supports multi-domain management, zone file import/export, and automated DNS backups. Includes both read-only and destructive operations with safety controls.