planner-commit
Handle git commits for plan execution with support for Conventional Commits or simple format. Called by plan-executor when auto_commit is enabled.
What this skill does
# Planner Commit Skill
This skill handles git commits after successful plan execution, respecting the configured commit message standard.
## Context You Receive
When called, you receive:
- `plan_name`: The name of the executed plan (e.g., "auth-01-setup.md")
- `summary`: Brief description of what was accomplished
- `files_modified`: List of files that were changed
- `auto_commit_standard`: Either `"conventional_commits"` or `"no_standard"`
---
## Commit Logic
### If `auto_commit_standard` is `"conventional_commits"`
Follow the Conventional Commits specification (v1.0.0):
**Format**: `<type>(<scope>): <description>`
**Determine the commit type** by analyzing the changes:
| Type | When to Use |
| ---------- | ------------------------------------------------------------ |
| `feat` | New feature or functionality |
| `fix` | Bug fix |
| `refactor` | Code restructuring without behavior change |
| `docs` | Documentation only changes |
| `test` | Adding or updating tests |
| `chore` | Maintenance, dependencies, tooling, config |
| `style` | Formatting, whitespace, missing semicolons (no logic change) |
| `perf` | Performance improvements |
**Determine the scope** from the plan name:
- Extract a meaningful scope from the plan filename
- Example: `auth-01-setup.md` → scope is `auth`
- Example: `user-profile-03-api.md` → scope is `user-profile`
- If unclear, use `planner` as the default scope
**Write the description**:
- Use imperative mood ("add feature" not "added feature")
- Keep it under 72 characters
- Be concise but descriptive
**Include a body** if more than 3 files were modified:
- Add a blank line after the subject
- List key changes or provide context
- Wrap at 72 characters
**Example commits**:
```
feat(auth): add user authentication endpoints
- Implement login and logout routes
- Add JWT token generation
- Create auth middleware
```
```
fix(user-profile): correct avatar upload validation
```
```
refactor(planner): reorganize plan execution flow
```
---
### If `auto_commit_standard` is `"no_standard"` (or missing)
Use the simple format:
```
feat(planner): Complete [plan_name] - [summary]
```
**Examples**:
```
feat(planner): Complete auth-01-setup.md - Set up authentication module
```
```
feat(planner): Complete user-profile-02-api.md - Add profile API endpoints
```
---
## Git Commands
1. **Stage all modified files**:
```bash
git add .
```
2. **Create the commit** with the appropriate message format:
```bash
git commit -m "<message>"
```
For multi-line messages (Conventional Commits with body):
```bash
git commit -m "<subject>" -m "<body>"
```
3. **Do NOT push** - leave that to the user
---
## Rules
1. **Never push to remote** - only commit locally
2. **Always stage with `git add .`** before committing
3. **Analyze the actual changes** to determine the correct commit type
4. **Use the plan name** to derive a meaningful scope
5. **Keep commits atomic** - one commit per plan execution
6. **Handle errors gracefully** - if commit fails, report the error
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.