luzgan/workflow
skills/workflow/SKILL.md
Enforces a feature-branch Git workflow — work on branches, commit meaningfully, create PRs, and only merge with user approval. Triggers on any code changes or when the user asks to implement something.
development
Updated Apr 7, 2026
$ install --global
skillsauthnpx skillsauth add luzgan/llm-skills workflowInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 7, 2026, 2:37 AM30.8s1 file scanned
SKILL.md
- name:
- workflow
- description:
- Enforces a feature-branch Git workflow — work on branches, commit meaningfully, create PRs, and only merge with user approval. Triggers on any code changes or when the user asks to implement something.
- user-invocable:
- false
- allowed-tools:
- Bash
Git Workflow
Follow this workflow for ALL code changes. Never commit directly to main.
1. Feature Branch
Before making any changes, create a feature branch from main:
git checkout -b feat/short-description
Use prefixes: feat/, fix/, refactor/, chore/ as appropriate.
2. Commit Meaningful Work
Commit as you go — don't wait until everything is done:
- Commit after completing a logical unit of work (new file, working feature, bug fix)
- Write clear commit messages that explain what and why
- Stage specific files, not
git add .
3. Create a PR
When the feature is complete:
- Push the branch:
git push -u origin <branch> - Create a PR with
gh pr create— include a summary and test plan - Do NOT merge automatically
4. Merge Only With Permission
After creating the PR, ask the user if they want to merge. Only merge when explicitly approved:
gh pr merge <number> --squash --delete-branch
Behavior
- If you realize mid-conversation you forgot to branch, stop, create the branch, and continue — don't keep committing to main
- If a project's CLAUDE.md has its own workflow instructions, defer to those for project-specific details but still follow the branch/PR pattern
- This workflow applies to every repository, not just specific projects
Related Skills
luzgan/openbrain-memory
testing
VerifiedTrustedCommunity
Proactively use OpenBrain to save and recall thoughts during conversations. Triggers when the user shares insights, makes decisions, learns something new, or works on topics that might have prior context in OpenBrain.
SKILL.mdUpdated Apr 7, 2026
luzgan/nightly-sync
development
VerifiedTrustedCommunity
Fetch recent GitHub commits and update LifeManager project descriptions and OpenBrain with development activity. Designed to run via /loop for periodic syncing.
SKILL.mdUpdated Apr 7, 2026
luzgan/morning-planner
data-ai
VerifiedTrustedCommunity
Generate today's daily plan by gathering context from LifeManager (projects, todos, calendar, yesterday's plan) and creating a focused schedule. Designed to run via /loop for daily planning.
SKILL.mdUpdated Apr 7, 2026
luzgan/lifemanager-projects
development
VerifiedTrustedCommunity
Proactively keep LifeManager project descriptions up to date as development progresses. Triggers when working on a project that is tracked in LifeManager — updates descriptions with recent changes, new features, and current state.
SKILL.mdUpdated Apr 7, 2026