feat: add ci-guard and semantic-versioning skills

[Aliciapet11]

Summary

• CI Guard skill — auto-activates when working in a repo without CI configuration. Alerts the user to add a CI workflow (GitHub Actions, GitLab CI, etc.) and provides starter templates for Python and Node.js. Repos can be exempted by adding a .research marker file.
• Semantic Versioning skill — analyzes commits using conventional commit prefixes (feat:, fix:, feat!:, BREAKING CHANGE) to determine whether the next release is a major, minor, or patch bump. Includes a helper script (version-bump.py) that detects version files (pyproject.toml, package.json, Cargo.toml, VERSION) and can apply the bump with --apply.

Both are skills (not commands) so they auto-activate based on context — no manual invocation needed.

Why skills over commands?

• CI Guard needs to alert automatically at session start when CI is missing — commands require manual /ci-guard invocation
• Versioning needs to contextually activate when pushing changes — skills trigger based on context

Test plan

• check-ci.py tested: detects CI in basecamp repo (OK), warns on repo without CI (WARNING + exit 1), skips research-marked repos (SKIP + exit 0)
• version-bump.py tested: analyzes 167 commits, correctly classifies conventional commits, suggests v0.1.0 for pre-1.0 major bumps
• Verify skills load correctly in a fresh Claude Code session
• Test CI guard alert triggers when working in a repo under repositories/ without CI

🤖 Generated with Claude Code