common-git-collaboration
Enforce version control best practices for commits, branching, pull requests, and repository security. Use when writing commits, creating branches, merging, or opening pull requests.
What this skill does
# Git & Collaboration ## **Priority: P0 (OPERATIONAL)** ## 1. Write Conventional Commits - Format: `<type>(<scope>): <description>` (e.g., `feat(auth): add login validation`). - Types: `feat`, `fix`, `docs`, `style`, `refactor`, `perf`, `test`, `chore`. - Use imperative mood: "add feature" not "added feature". - One commit = one logical change — no mega-commits. See [implementation examples](references/implementation.md) for conventional commit examples. ## 2. Manage Branches - Name with prefixes: `feat/`, `fix/`, `hotfix/`, `refactor/`, `docs/`. - Create new branch for every task to keep main stable and deployable. - Never push directly to `main` or `develop` — use Pull Requests. - Pull before you push to resolve conflicts locally. - Prefer `git rebase` over merge for linear history on feature branches. - Use `git rebase -i` to squash messy commits before pushing. ## 3. Submit Quality Pull Requests - Limit to < 300 lines of code for effective review. - State what changed, why, and how to test. Link issues (`Closes #123`). - Self-review for obvious errors before requesting peers. - PRs must pass all CI checks (lint, test, build) before merging. ## 4. Protect Secrets and Metadata - Never commit `.env`, keys, or certificates — use `.gitignore` strictly. - Use `husky` or `lefthook` for local Git Hooks enforcement. - Tag releases with SemVer (`vX.Y.Z`) and update `CHANGELOG.md`. ## Anti-Patterns - **No direct push to main**: All changes via PR, no exceptions. - **No mega-commits**: One commit = one logical change. Split large ones. - **No secrets in history**: Use `git filter-repo` to purge; rotate secret. ## References - [Clean Linear History & Rebase Examples](references/CLEAN_HISTORY.md)
Related in Security
mac-ops
IncludedComprehensive macOS workstation operations — diagnose kernel panics, identify failing drives, audit launchd startup items, decode wake reasons, triage TCC permission denials, manage APFS snapshots, recover from no-boot. Use for: Mac is slow, slow bootup, won't boot, kernel panic, kernel_task hot, mds_stores CPU, photoanalysisd, cloudd, login loop, gray screen, sleep wake failure, drive failing, IO errors, APFS snapshots eating space, Time Machine local snapshots, Spotlight indexing, launchd, LaunchAgent, LaunchDaemon, login items, TCC permissions, Full Disk Access, Screen Recording denied, Gatekeeper, quarantine, com.apple.quarantine, app is damaged, helper tool, /Library/PrivilegedHelperTools, pmset, wake reasons, dark wake, sysdiagnose, panic.ips, DiagnosticReports, configuration profile, MDM profile, remote diagnostics over SSH.
a11y-audit
IncludedRun accessibility audits on web projects combining automated scanning (axe-core, Lighthouse) with WCAG 2.1 AA compliance mapping, manual check guidance, and structured reporting. Output is configurable: markdown report only, markdown plus machine-readable JSON, or markdown plus issue tracker integration. Use this skill whenever the user mentions "accessibility audit", "a11y audit", "WCAG audit", "accessibility check", "compliance scan", or asks to check a web project for accessibility issues. Also trigger when the user wants to verify WCAG conformance or map findings to a specific standard (CAN-ASC-6.2, EN 301 549, ADA/AODA).
erpclaw
IncludedAI-native ERP system with self-extending OS. Full accounting, invoicing, inventory, purchasing, tax, billing, HR, payroll, advanced accounting (ASC 606/842, intercompany, consolidation), and financial reporting. 413 actions across 14 domains, 43 expansion modules. Constitutional guardrails, adversarial audit, schema migration. Double-entry GL, immutable audit trail, US GAAP.
assess
IncludedAssesses and rates quality 0-10 across multiple dimensions (correctness, maintainability, security, performance, testability, simplicity) with pros/cons analysis. Compares against project conventions and prior decisions from memory. Produces structured evaluation reports with actionable improvement suggestions. Use when evaluating code, designs, architectures, or comparing alternative approaches.
spring-boot-security-jwt
IncludedProvides JWT authentication and authorization patterns for Spring Boot 3.5.x covering token generation with JJWT, Bearer/cookie authentication, database/OAuth2 integration, and RBAC/permission-based access control using Spring Security 6.x. Use when implementing authentication or authorization in Spring Boot applications.
code-hardcode-audit
IncludedDetect hardcoded values, magic numbers, and leaked secrets. TRIGGERS - hardcode audit, magic numbers, PLR2004, secret scanning.