.cursor/skills/git-workflow/SKILL.md
Git branching workflow, commit conventions, changelog, and version bumping for the Conscius project. USE WHEN: user wants to start an epic or task, create a branch, open a PR, merge to main, bump the version, update the changelog, or needs git workflow guidance. EXAMPLES: 'start epic 4', 'create the task branch', 'open a PR for this task', 'bump the version', 'update the changelog', 'how do I start a new task?'.
npx skillsauth add jwill9999/conscius git-workflowInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
git branch --show-currentgit status -sb | head -1git log --oneline -5$ARGUMENTS
main
└── feat/e{N}-{epic-name} ← epic branch (PR → main)
├── feat/e{N}-t{M}-{task-name} ← task sub-branch (PR → epic branch)
└── feat/e{N}-t{M}-{task-name}
Examples: feat/e4-agent-plugin-mulch, feat/e4-t1-mulch-adapter
maingit checkout main && git pull
git checkout -b feat/e{N}-{epic-name}
git checkout feat/e{N}-{epic-name}
git checkout -b feat/e{N}-t{M}-{task-name}
main)git add . && git commit -m "feat(e{N}-t{M}): description
Co-authored-by: Copilot <[email protected]>"
git push -u origin feat/e{N}-t{M}-{task-name}
gh pr create --base feat/e{N}-{epic-name} --title "feat(e{N}-t{M}): description"
Human reviews the PR. Do not self-merge. Wait for approval.
git checkout feat/e{N}-{epic-name}
npx nx run-many -t typecheck,lint,test,build --all
maingit push -u origin feat/e{N}-{epic-name}
gh pr create --base main --title "feat: Epic {N} — {Epic Name}" --body "..."
git checkout main && git pull
git-cliff --output CHANGELOG.md
# Bump version in: package.json, packages/*/package.json
# Also update the static version badge in README.md: 
# (Replace with npm badge once packages are published to npm)
git add CHANGELOG.md package.json packages/*/package.json README.md
git commit -m "chore: update CHANGELOG.md and bump to 0.{N+1}.0-alpha.0"
git push
<type>(scope): short description
Types: feat | fix | docs | chore | refactor | test | ci
Scope: e.g. e4-t1, agent-core, agent-plugin-mulch
Always include:
Co-authored-by: Copilot <[email protected]>
CHANGELOG.md at the repo root — auto-generated by git-cliff (cliff.toml at root)All package.json (root + packages/*/package.json) carry the same version.
| Stage | Format | When |
| ------------------ | --------------- | ---------------- |
| Active development | 0.x.0-alpha.0 | Now |
| Feature complete | 0.x.0-beta.0 | All 9 epics done |
| Release candidate | 1.0.0-rc.0 | Tested + docs |
| Stable | 1.0.0 | Production ready |
Minor version increments per completed epic (e.g. Epic 4 merges → 0.4.0-alpha.0).
testing
Manage SESSION.md and SUMMARY.md for the Conscius project. USE WHEN: user says 'update session', 'update SESSION.md', 'end of session', 'taking a break', 'stepping away', 'compress conversation', 'add summary', or when completing an epic/task and session state needs recording. EXAMPLES: 'update the session', 'let's update session.md', 'add a summary segment', 'I am done for today'.
testing
PR review workflow for the Conscius project. USE WHEN: user opens a pull request, asks to check CI status, mentions SonarCloud or Sourcery feedback, asks if a PR is ready to merge, or needs to resolve a merge conflict. EXAMPLES: 'check if the PR is ready', 'CI failed on my PR', 'SonarCloud flagged something', 'is this ready to merge?', 'fix merge conflict', 'review PR feedback'.
tools
Plan, document, and manage epics, features, tasks, and backlog items for the Conscius project. Creates entries in both the markdown planning docs (docs/planning/) and the Beads task graph (bd CLI). Use this skill for all planning work. Supported slash commands: /new-epic, /new-feature, /add-task, /update-status, /close-feature, /archive-feature, /new-backlog, /move-to-feature, /list-features, /list-backlog, /sync-beads, /help /planning
development
Explore and understand Nx workspaces. USE WHEN answering questions about the workspace, projects, or tasks. ALSO USE WHEN an nx command fails or you need to check available targets/configuration before running a task. EXAMPLES: 'What projects are in this workspace?', 'How is project X configured?', 'What depends on library Y?', 'What targets can I run?', 'Cannot find configuration for task', 'debug nx task failure'.