Standards for version control, commit messages, and branching strategy
npx skills add https://github.com/hongluu92/research-kit --skill gitانسخ والصق هذا الأمر في Claude Code لتثبيت المهارة
Autonomous task execution cycle: Plan -> Research -> Prototype -> Evaluate -> Report
Methodologies for rapidly building software proofs-of-concept
Writing engaging yet rigorous academic text and generating reports
Techniques for querying academic databases (ArXiv, Semantic Scholar, PubMed) and code repositories (GitHub)
Standards for academic citation and findings connected papers
Management of local knowledge, embeddings, and information retrieval (RAG)
| name | git |
| description | Standards for version control, commit messages, and branching strategy |
| allowed-tools | run_command |
| version | 1 |
| priority | CRITICAL |
CRITICAL SKILL - Maintain a clean, traversable, and semantic history.
| Principle | Rule |
|---|---|
| Atomic Commits | One logical change per commit (e.g., "Fix bug" vs "Fix bug and add feature") |
| Conventional Commits | Use structured messages (feat, fix, docs, refactor, etc.) |
| Clean History | Don't commit broken code. Squash WIP commits before merging. |
| Ignore Artifacts | Never commit derived files (builds, local configs, secrets). |
Follow the Conventional Commits specification:
<type>(<scope>): <subject>
<body>
<footer>
| Type | Description |
|---|---|
feat | A new feature |
fix | A bug fix |
docs | Documentation only changes |
style | Changes that do not affect the meaning of the code (white-space, formatting, etc) |
refactor | A code change that neither fixes a bug nor adds a feature |
perf | A code change that improves performance |
test | Adding missing tests or correcting existing tests |
chore | Changes to the build process or auxiliary tools and libraries |
Good:
feat(auth): implement jwt token validationfix(search): handle empty result sets gracefullydocs(readme): update installation instructionsBad:
update codefix bugwipBefore Committing:
git status to see what will be staged.git diff to review changes line-by-line.Branching (if applicable):
main / master: Stable production code.develop / dev: Integration branch.feat/feature-name: Feature branches.fix/issue-description: Bug fix branches.Handling Conflicts:
| Action | Command |
|---|---|
| Check Status | git status |
| View Changes | git diff |
| Stage Files | git add <file> (Avoid git add . unless sure) |
| Commit | git commit -m "type(scope): message" |
| Log | git log --oneline --graph --decorate --all |
Ask yourself:
node_modules, venv, or .env?