Update CVs with new contact info and visual enhancements #5
Conversation
- Switch from classic to banking style with darkmagenta color - Update to 10pt font size matching main CV - Restructure sections to follow main CV organization - Condense content to maintain 2-page limit - Standardize formatting and personal data presentation
- Replace teaching details with link to comphy-lab.org/teaching - Add hyperlinks to Google Scholar and Web of Science profiles - Include i10-index metric - Update citation count to 400+
- Set up ChkTeX linter with CV-specific configuration - Create Makefile with colorful output and smart log handling - Add pre-commit hooks for automatic linting - Configure VS Code LaTeX Workshop for proper compilation - Remove BibTeX steps (CVs don't use citations) - Suppress verbose pdflatex output, show only errors/warnings - Add GitHub Actions workflow for CI linting - Update documentation with new lint commands Features: - make lint: Run linter with clean output - make all: Lint + compile with progress indicators - Auto-cleanup of temp files after successful compilation - Color-coded output (blue=info, green=success, yellow=warning, red=error) - Smart log preservation only when errors occur
Changed verb tense from present continuous to past tense for the 2022-2025 position: - 'Leading' → 'Led' Computational Multiphase Physics Lab - 'Working on' → 'Worked on' non-Newtonian flows This reflects that the position has concluded.
- Rearranged PhD students in reverse chronological order
- Added research topics for new PhD students:
- J. Talukdar: Singularities with surfactants (Jul 2025)
- S. Jana: Soft impacts (Jun 2025)
- Updated J. Talukdar master status from 'ongoing' to completed ('25)
- Added S. Jana's master thesis (IIT KGP, '25) with thesis link
- Updated master/BSc count from 15 to 16 in short CV
- Standardized thesis URLs to cleaner format:
- M. Sent: tinyurl → bit.ly/thesisSent
- N. Kuipers: tinyurl → bit.ly/thesisKuipers
- V. Rosario: tinyurl → bit.ly/thesisRosario
- S. Meuleman: ThesisStevenM → thesisMeuleman
- S. van den Heuvel: 4er5VaH → thesisSwen
- Added 4-day interactive course at Universidad Carlos III de Madrid (March 10-13, 2025) - Included link to self-paced version of the course - Added reference to comphy-lab.org/teaching for complete teaching activities
- Add subtle icons throughout CV for better visual hierarchy - Publications: 📄 for open access, 🔒 for paywalled papers - Special features: ⭐ for journal covers and editor's suggestions, 📈 for highly cited papers - Section icons: 🎓 for theses, 🎤 for talks, ✓ for refereeing, etc. - Bold bracketed numbering [1], [2] for publications - Red YouTube icons for video links - Update CLAUDE.md with comprehensive formatting guidelines - Maintain academic professionalism while improving readability
- Add new 2025 publications (J. Fluid Mech. and Phys. Rev. Lett.) - Update publication counts and citation metrics - Enhance visual formatting with icons for publications and sections - Update short CV with 5 most recent publications - Improve overall consistency and readability
- Change website from vatsalsanjay.com to comphy-lab.org - Update email to [email protected] - Replace test tube with light bulb icon for research fellowships - Add links to major awards (Ammodo, JFM Outstanding Reviewer, KIVI, Lindau) - Update education to show "Dept. Gold Medal" instead of CGPA - Expand short CV to 2-3 pages with more details: - Add research intern position - Expand awards with descriptions and links - Add detailed supervision information - Expand service activities with conference details - Add metrics section - Show 7 latest publications - Add full BlueSky and X links for outreach
📝 WalkthroughSummary by CodeRabbit
WalkthroughThis update introduces a comprehensive LaTeX CV project setup, adding new configuration files for linting, building, and editor integration. The CV documents and bibliography are extensively updated with new content, formatting, and publication entries. Documentation is expanded with guides for linting and repository maintenance, and automation scripts are provided for streamlined workflows. Changes
Sequence Diagram(s)sequenceDiagram
participant Developer
participant Editor/VSCode
participant Pre-commit Hooks
participant Makefile
participant ChkTeX/Lacheck/BibTeX
participant Git
Developer->>Editor/VSCode: Edit CV (.tex), bibliography (.bib)
Editor/VSCode->>ChkTeX: Lint .tex files (on save/build)
Editor/VSCode->>Makefile: Build CV (via LaTeX Workshop or terminal)
Makefile->>ChkTeX/Lacheck/BibTeX: Run linting, bib checks
Makefile->>Developer: Output logs, errors, or success
Developer->>Git: Stage files for commit
Git->>Pre-commit Hooks: Trigger on commit
Pre-commit Hooks->>ChkTeX/Lacheck/BibTeX: Lint/check files
Pre-commit Hooks->>Developer: Block or allow commit based on checks
Poem
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 13
📜 Review details
Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro
⛔ Files ignored due to path filters (2)
Vatsal_CV-shortCV.pdfis excluded by!**/*.pdfVatsal_CV.pdfis excluded by!**/*.pdf
📒 Files selected for processing (14)
.chktexrc(1 hunks).github/workflows/latex-lint.yml(1 hunks).gitignore(1 hunks).latexmkrc(1 hunks).pre-commit-config.yaml(1 hunks).vscode/ltex.dictionary.en-US.txt(1 hunks).vscode/settings.json(1 hunks)CLAUDE.md(1 hunks)LINTING.md(1 hunks)Makefile(1 hunks)Vatsal_CV-shortCV.tex(1 hunks)Vatsal_CV.tex(8 hunks)mypublications.bib(2 hunks)package.json(1 hunks)
🧰 Additional context used
🪛 YAMLlint (1.37.1)
.pre-commit-config.yaml
[error] 24-24: no new line character at the end of file
(new-line-at-end-of-file)
.github/workflows/latex-lint.yml
[warning] 3-3: truthy value should be one of [false, true]
(truthy)
[error] 5-5: too many spaces inside brackets
(brackets)
[error] 5-5: too many spaces inside brackets
(brackets)
[error] 7-7: too many spaces inside brackets
(brackets)
[error] 7-7: too many spaces inside brackets
(brackets)
[error] 12-12: trailing spaces
(trailing-spaces)
[error] 14-14: wrong indentation: expected 6 but found 4
(indentation)
[error] 15-15: trailing spaces
(trailing-spaces)
[error] 20-20: trailing spaces
(trailing-spaces)
[error] 25-25: trailing spaces
(trailing-spaces)
[error] 33-33: trailing spaces
(trailing-spaces)
[error] 40-40: trailing spaces
(trailing-spaces)
[error] 46-46: trailing spaces
(trailing-spaces)
[error] 51-51: trailing spaces
(trailing-spaces)
[error] 55-55: no new line character at the end of file
(new-line-at-end-of-file)
🪛 actionlint (1.7.7)
.github/workflows/latex-lint.yml
14-14: the runner of "actions/checkout@v3" action is too old to run on GitHub Actions. update the action's version to fix this issue
(action)
🪛 LanguageTool
LINTING.md
[uncategorized] ~97-~97: You might be missing the article “the” here.
Context: ...Code Integration If using VS Code with LaTeX Workshop extension: 1. Install the LaTe...
(AI_EN_LECTOR_MISSING_DETERMINER_THE)
CLAUDE.md
[uncategorized] ~61-~61: You might be missing the article “the” here.
Context: ...`` Key formatting rules: - Use \\ at end of each line except the last - Page cou...
(AI_EN_LECTOR_MISSING_DETERMINER_THE)
[uncategorized] ~81-~81: You might be missing the article “the” here.
Context: ...er them from newest to oldest - Include year in parentheses at the end ### For mypu...
(AI_EN_LECTOR_MISSING_DETERMINER_THE)
[uncategorized] ~134-~134: You might be missing the article “the” here.
Context: ...ward Icons - Note: No icons used in Major Awards & Achievements section to mainta...
(AI_EN_LECTOR_MISSING_DETERMINER_THE)
🪛 markdownlint-cli2 (0.17.2)
LINTING.md
23-23: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
24-24: Lists should be surrounded by blank lines
null
(MD032, blanks-around-lists)
33-33: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
34-34: Lists should be surrounded by blank lines
null
(MD032, blanks-around-lists)
38-38: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
39-39: Lists should be surrounded by blank lines
null
(MD032, blanks-around-lists)
48-48: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
49-49: Fenced code blocks should be surrounded by blank lines
null
(MD031, blanks-around-fences)
58-58: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
59-59: Fenced code blocks should be surrounded by blank lines
null
(MD031, blanks-around-fences)
64-64: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
66-66: Lists should be surrounded by blank lines
null
(MD032, blanks-around-lists)
72-72: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
74-74: Lists should be surrounded by blank lines
null
(MD032, blanks-around-lists)
78-78: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
80-80: Lists should be surrounded by blank lines
null
(MD032, blanks-around-lists)
86-86: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
88-88: Fenced code blocks should be surrounded by blank lines
null
(MD031, blanks-around-fences)
98-98: Lists should be surrounded by blank lines
null
(MD032, blanks-around-lists)
107-107: Lists should be surrounded by blank lines
null
(MD032, blanks-around-lists)
115-115: Fenced code blocks should be surrounded by blank lines
null
(MD031, blanks-around-fences)
128-128: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
131-131: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
134-134: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
137-137: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
143-143: Lists should be surrounded by blank lines
null
(MD032, blanks-around-lists)
159-159: Fenced code blocks should be surrounded by blank lines
null
(MD031, blanks-around-fences)
171-171: Lists should be surrounded by blank lines
null
(MD032, blanks-around-lists)
173-173: Files should end with a single newline character
null
(MD047, single-trailing-newline)
CLAUDE.md
5-5: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
7-7: Lists should be surrounded by blank lines
null
(MD032, blanks-around-lists)
10-10: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
11-11: Fenced code blocks should be surrounded by blank lines
null
(MD031, blanks-around-fences)
28-28: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
30-30: Lists should be surrounded by blank lines
null
(MD032, blanks-around-lists)
34-34: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
35-35: Lists should be surrounded by blank lines
null
(MD032, blanks-around-lists)
43-43: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
45-45: Fenced code blocks should be surrounded by blank lines
null
(MD031, blanks-around-fences)
53-53: Fenced code blocks should be surrounded by blank lines
null
(MD031, blanks-around-fences)
61-61: Lists should be surrounded by blank lines
null
(MD032, blanks-around-lists)
62-62: Trailing spaces
Expected: 0 or 2; Actual: 1
(MD009, no-trailing-spaces)
67-67: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
69-69: Fenced code blocks should be surrounded by blank lines
null
(MD031, blanks-around-fences)
74-74: Fenced code blocks should be surrounded by blank lines
null
(MD031, blanks-around-fences)
79-79: Lists should be surrounded by blank lines
null
(MD032, blanks-around-lists)
83-83: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
85-85: Fenced code blocks should be surrounded by blank lines
null
(MD031, blanks-around-fences)
97-97: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
98-98: Lists should be surrounded by blank lines
null
(MD032, blanks-around-lists)
105-105: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
107-107: Lists should be surrounded by blank lines
null
(MD032, blanks-around-lists)
117-117: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
118-118: Lists should be surrounded by blank lines
null
(MD032, blanks-around-lists)
124-124: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
125-125: Lists should be surrounded by blank lines
null
(MD032, blanks-around-lists)
133-133: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
134-134: Lists should be surrounded by blank lines
null
(MD032, blanks-around-lists)
137-137: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
138-138: Lists should be surrounded by blank lines
null
(MD032, blanks-around-lists)
141-141: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
142-142: Lists should be surrounded by blank lines
null
(MD032, blanks-around-lists)
148-148: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
149-149: Lists should be surrounded by blank lines
null
(MD032, blanks-around-lists)
153-153: Files should end with a single newline character
null
(MD047, single-trailing-newline)
🔇 Additional comments (25)
.latexmkrc (1)
10-10: Clean up auxiliary file extensions
The configured list covers the common temporary files generated by LaTeX.Optionally, you could include additional extensions like
lof/lotif needed, but the current list is comprehensive..gitignore (1)
68-76: Ignore linting and build artifacts
The new patterns forchktex.log,.pre-commit-cache/,node_modules/,package-lock.json,*_bibertool.bib, and*.blgcorrectly prevent clutter from linting and auxiliary files..pre-commit-config.yaml (3)
1-11: Configure local pre-commit hooks
The local hooks forchktexon.texand the BibTeX check on.bibfiles align well with the CI linting strategy.Be sure to document these hooks in
LINTING.mdso contributors know how to install and run them.
12-16: Verify BibTeX hook error suppression
Usingbash -c 'bibtex -terse "$@" || true'will swallow errors—ensure that critical.bibissues aren’t hidden from CI.Please confirm that any BibTeX failures are still surfaced in your GitHub Actions or Makefile lint targets.
17-24: Include standard formatting hooks
The trailing-whitespace, end-of-file-fixer, and merge-conflict checks provide solid baseline hygiene for.texand.bibfiles.🧰 Tools
🪛 YAMLlint (1.37.1)
[error] 24-24: no new line character at the end of file
(new-line-at-end-of-file)
.chktexrc (2)
4-27: Tailor ChkTeX suppressions for CV style
Suppressing warnings 2, 8, 11, 13, 25, 1, 36, and 12 aligns well with CV formatting conventions (intersentence spacing, dashes, ellipses, font commands, etc.).
28-32: Enable critical reference and label checks
Enabling warnings 15 and 16 will catch undefined references and duplicate labels, ensuring document integrity..vscode/settings.json (1)
2-16: VSCode LaTeX settings look solidThe workspace settings align with the Makefile and CI linting commands and configure build recipes, linting args, and clean-up patterns appropriately. No changes needed.
.github/workflows/latex-lint.yml (1)
14-15: Consider pinning checkout action to latest patchactionlint flagged that
actions/checkout@v3might not be the latest patch release. You can pin it more specifically (e.g.,actions/[email protected]) to ensure you get the newest bug and security fixes.🧰 Tools
🪛 actionlint (1.7.7)
14-14: the runner of "actions/checkout@v3" action is too old to run on GitHub Actions. update the action's version to fix this issue
(action)
🪛 YAMLlint (1.37.1)
[error] 14-14: wrong indentation: expected 6 but found 4
(indentation)
[error] 15-15: trailing spaces
(trailing-spaces)
LINTING.md (1)
97-97: 🧹 Nitpick (assertive)Add missing article “the”
For clarity, update the sentence to:
- If using VS Code with LaTeX Workshop extension: + If using the VS Code with the LaTeX Workshop extension:Likely an incorrect or invalid review comment.
🧰 Tools
🪛 LanguageTool
[uncategorized] ~97-~97: You might be missing the article “the” here.
Context: ...Code Integration If using VS Code with LaTeX Workshop extension: 1. Install the LaTe...(AI_EN_LECTOR_MISSING_DETERMINER_THE)
mypublications.bib (4)
4-4: LGTM!The date update is correct and follows the standard BibDesk format.
7-7: LGTM!The string encoding specification is correctly maintained.
43-51: Great update from preprint to published version!The entry has been properly updated with all the required metadata including volume, pages, DOI, and the full author list for the published version.
53-79: New 2025 publications added correctly!All three new entries follow proper BibTeX formatting with complete metadata. The use of special characters in titles (H$_2$, chemical notations) is handled correctly.
Vatsal_CV.tex (8)
26-30: Contact information updated correctly!The updates align with the PR objectives - email changed to [email protected] and homepage to comphy-lab.org.
54-54: Education section updated as intendedThe CGPA notation has been replaced with "Dept. Gold Medal" as specified in the PR objectives.
67-75: Professional experience properly restructuredThe new Assistant Professor position at Durham University has been added and the experience section has been reordered chronologically with the current position first.
82-96: Awards section enhanced with hyperlinksThe paperclip icons (📎) have been added as intended, providing direct links to official award pages. The implementation looks clean and consistent.
112-125: Service sections properly enhanced with iconsThe use of FontAwesome5 icons (\faUsers, \faCheck) adds visual clarity to the sections as intended.
130-132: Research funding section updated with iconsThe light bulb icon (💡) correctly replaces the test tube icon for the fellowship, matching the PR objectives.
183-280: Publications list properly reformatted with new entriesThe numbered enumeration, added 2025 publications, and icon usage (📄 for open access, 🔒 for paywalled, ⭐ for special features) enhance readability and accessibility.
389-395: Metrics section enhanced with icons and updated linksThe section now includes appropriate icons for each metric type and maintains updated links to profiles.
Vatsal_CV-shortCV.tex (3)
1-7: Style configuration differs from documentationThe AI summary mentions this uses "classic" style, but the code shows "banking" style - same as the main CV. This is actually correct as both CVs should maintain visual consistency.
58-66: Professional experience section well condensedThe section appropriately summarizes the key positions while maintaining consistency with the main CV.
122-129: Metrics section properly formatted with iconsThe metrics are clearly presented with appropriate FontAwesome5 icons, matching the style of the main CV.
Refine the pattern from /CV/ to /CV\.tex$/ to specifically match filenames ending with "CV.tex". This prevents unintended matches with files containing "CV" elsewhere in their names.
There was a problem hiding this comment.
Actionable comments posted: 3
♻️ Duplicate comments (1)
.github/workflows/latex-lint.yml (1)
5-7: 🧹 Nitpick (assertive)Fix bracket spacing in branch lists
YAMLlint flags "too many spaces inside brackets". Remove the spaces immediately inside[...]so the lists read[main, master].
Apply:- branches: [ main, master ] + branches: [main, master] - branches: [ main, master ] + branches: [main, master]🧰 Tools
🪛 YAMLlint (1.37.1)
[error] 5-5: too many spaces inside brackets
(brackets)
[error] 5-5: too many spaces inside brackets
(brackets)
[error] 7-7: too many spaces inside brackets
(brackets)
[error] 7-7: too many spaces inside brackets
(brackets)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro
📒 Files selected for processing (1)
.github/workflows/latex-lint.yml(1 hunks)
🧰 Additional context used
🪛 actionlint (1.7.7)
.github/workflows/latex-lint.yml
14-14: the runner of "actions/checkout@v3" action is too old to run on GitHub Actions. update the action's version to fix this issue
(action)
🪛 YAMLlint (1.37.1)
.github/workflows/latex-lint.yml
[warning] 3-3: truthy value should be one of [false, true]
(truthy)
[error] 5-5: too many spaces inside brackets
(brackets)
[error] 5-5: too many spaces inside brackets
(brackets)
[error] 7-7: too many spaces inside brackets
(brackets)
[error] 7-7: too many spaces inside brackets
(brackets)
[error] 12-12: trailing spaces
(trailing-spaces)
[error] 14-14: wrong indentation: expected 6 but found 4
(indentation)
[error] 15-15: trailing spaces
(trailing-spaces)
[error] 27-27: trailing spaces
(trailing-spaces)
[error] 35-35: trailing spaces
(trailing-spaces)
[error] 42-42: trailing spaces
(trailing-spaces)
[error] 48-48: trailing spaces
(trailing-spaces)
[error] 53-53: trailing spaces
(trailing-spaces)
[error] 57-57: no new line character at the end of file
(new-line-at-end-of-file)
There was a problem hiding this comment.
Actionable comments posted: 3
♻️ Duplicate comments (6)
.pre-commit-config.yaml (1)
24-25: Add missing final newline.The file still lacks a final newline character, as flagged in previous reviews. This violates YAML and POSIX conventions.
- id: check-merge-conflict +package.json (2)
10-14: Verify Makefile targets exist for npm scripts.Previous reviews flagged that these npm scripts reference Makefile targets (
lint-tex,lint-bib,lint-lacheck,check-refs) that may not exist. Please verify these targets are properly defined in the Makefile.#!/bin/bash # Description: Check if the Makefile targets referenced by npm scripts exist echo "Checking for Makefile targets referenced by npm scripts..." for target in lint-tex lint-bib lint-lacheck check-refs; do if grep -q "^${target}:" Makefile 2>/dev/null; then echo "✓ Target '$target' found in Makefile" else echo "✗ Target '$target' not found in Makefile" fi done
32-34: Consider removing empty devDependencies.The
devDependenciesfield is empty and can be removed to clean up the package.json structure, as suggested in previous reviews.- "engines": { - "node": ">=14.0.0" - } + "engines": { + "node": ">=14.0.0" + }.github/workflows/latex-lint.yml (1)
5-7: Fix bracket spacing for YAMLlint compliance.The branch lists contain extra spaces inside brackets, violating YAMLlint rules as flagged in previous reviews.
- branches: [ main, master ] + branches: [main, master]- branches: [ main, master ] + branches: [main, master]🧰 Tools
🪛 YAMLlint (1.37.1)
[error] 5-5: too many spaces inside brackets
(brackets)
[error] 5-5: too many spaces inside brackets
(brackets)
[error] 7-7: too many spaces inside brackets
(brackets)
[error] 7-7: too many spaces inside brackets
(brackets)
LINTING.md (1)
199-199: Ensure single trailing newline
Add exactly one newline at the end of the document to comply with MD047.CLAUDE.md (1)
179-179: Ensure single trailing newline
Add exactly one newline at the end of the document to satisfy MD047.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro
⛔ Files ignored due to path filters (2)
Vatsal_CV-shortCV.pdfis excluded by!**/*.pdfVatsal_CV.pdfis excluded by!**/*.pdf
📒 Files selected for processing (7)
.github/workflows/latex-lint.yml(1 hunks).latexmkrc(1 hunks).pre-commit-config.yaml(1 hunks)CLAUDE.md(1 hunks)LINTING.md(1 hunks)Makefile(1 hunks)package.json(1 hunks)
🧰 Additional context used
🪛 YAMLlint (1.37.1)
.github/workflows/latex-lint.yml
[warning] 3-3: truthy value should be one of [false, true]
(truthy)
[error] 5-5: too many spaces inside brackets
(brackets)
[error] 5-5: too many spaces inside brackets
(brackets)
[error] 7-7: too many spaces inside brackets
(brackets)
[error] 7-7: too many spaces inside brackets
(brackets)
🪛 LanguageTool
CLAUDE.md
[uncategorized] ~9-~9: Loose punctuation mark.
Context: ...y's curriculum vitae: - Vatsal_CV.tex: Comprehensive academic CV using modernc...
(UNLIKELY_OPENING_PUNCTUATION)
[uncategorized] ~71-~71: You might be missing the article “the” here.
Context: ... Key formatting rules: - Use\` at end of each line except the last - Page cou...
(AI_EN_LECTOR_MISSING_DETERMINER_THE)
[uncategorized] ~95-~95: You might be missing the article “the” here.
Context: ...er them from newest to oldest - Include year in parentheses at the end ### For mypu...
(AI_EN_LECTOR_MISSING_DETERMINER_THE)
[uncategorized] ~138-~138: Loose punctuation mark.
Context: ...ns ### Publication Symbols - \faFile: 📄 for open-access publications (replac...
(UNLIKELY_OPENING_PUNCTUATION)
[uncategorized] ~146-~146: Loose punctuation mark.
Context: ... ### Section Icons - \faUserGraduate: 🎓 for PhD Theses subsection - `\faGrad...
(UNLIKELY_OPENING_PUNCTUATION)
[uncategorized] ~156-~156: You might be missing the article “the” here.
Context: ...ard Icons - Note: No icons used in Major Awards & Achievements section to mainta...
(AI_EN_LECTOR_MISSING_DETERMINER_THE)
[uncategorized] ~161-~161: Loose punctuation mark.
Context: ...nly ### Funding Icons - \faLightbulb: 💡 for research fellowships and monetar...
(UNLIKELY_OPENING_PUNCTUATION)
[uncategorized] ~166-~166: Loose punctuation mark.
Context: ...### Metrics Section Icons - \faIdCard: 🆔 for Researcher ID - \faOrcid: ORCI...
(UNLIKELY_OPENING_PUNCTUATION)
🔇 Additional comments (7)
.latexmkrc (1)
1-10: Well-configured Latexmk setup for CV compilation.The configuration correctly disables BibTeX for CV files and defines a comprehensive cleanup extension list. The regex pattern
/CV\.tex$/appropriately targets files ending with "CV.tex" as suggested in previous reviews..github/workflows/latex-lint.yml (2)
14-57: Comprehensive LaTeX linting workflow with proper error handling.The workflow effectively sets up a complete linting pipeline with:
- Updated
actions/checkout@v4addressing previous version warnings- Proper LaTeX environment setup with required linting tools
- Comprehensive checks including ChkTeX, lacheck, and bibliography validation
- Appropriate use of
continue-on-errorfor linting steps- Final compilation and reference validation
57-58: Add missing final newline.The file should end with a newline character to comply with standard formatting practices.
make check-refs +LINTING.md (1)
1-4: Comprehensive and clear linting guide
The document provides a thorough overview of linting tools, configurations, and workflows. The introduction sets clear expectations.Makefile (1)
11-11: .PHONY declarations cover all targets
Includinglint-tex,lint-bib,lint-lacheck, andcheck-refsaligns the Makefile with the documentation and CI scripts.CLAUDE.md (2)
49-67: Verified publication guidelines updated to 7 papers
The short CV now correctly specifies 7 latest publications, matching the code.
173-179: Consistent icon formatting guidance
The icon-spacing conventions are clearly documented and align with the updates inVatsal_CV.texandVatsal_CV-shortCV.tex.
…al_CV and Vatsal_CV-shortCV
… LaTeX lint workflow
There was a problem hiding this comment.
Actionable comments posted: 1
♻️ Duplicate comments (1)
CLAUDE.md (1)
5-191: Comprehensive documentation with markdown formatting issuesThis is excellent, detailed documentation that provides clear guidance for CV maintenance. However, the markdown formatting issues identified in previous reviews persist throughout the file.
The markdown formatting lacks necessary blank lines around headings, lists, and code blocks, which reduces readability. Consider applying consistent formatting fixes as suggested in previous reviews.
🧰 Tools
🪛 LanguageTool
[uncategorized] ~9-~9: Loose punctuation mark.
Context: ...y's curriculum vitae: -Vatsal_CV.tex: Comprehensive academic CV using modernc...(UNLIKELY_OPENING_PUNCTUATION)
[uncategorized] ~84-~84: You might be missing the article “the” here.
Context: ...Key formatting rules: - Use\` at end of each line except the last - Page cou...(AI_EN_LECTOR_MISSING_DETERMINER_THE)
[uncategorized] ~108-~108: You might be missing the article “the” here.
Context: ...er them from newest to oldest - Include year in parentheses at the end ### For mypu...(AI_EN_LECTOR_MISSING_DETERMINER_THE)
[uncategorized] ~151-~151: Loose punctuation mark.
Context: ...ns ### Publication Symbols -\faFile: 📄 for open-access publications (replac...(UNLIKELY_OPENING_PUNCTUATION)
[uncategorized] ~159-~159: Loose punctuation mark.
Context: ... ### Section Icons -\faUserGraduate: 🎓 for PhD Theses subsection - `\faGrad...(UNLIKELY_OPENING_PUNCTUATION)
[uncategorized] ~169-~169: You might be missing the article “the” here.
Context: ...ard Icons - Note: No icons used in Major Awards & Achievements section to mainta...(AI_EN_LECTOR_MISSING_DETERMINER_THE)
[uncategorized] ~174-~174: Loose punctuation mark.
Context: ...nly ### Funding Icons -\faLightbulb: 💡 for research fellowships and monetar...(UNLIKELY_OPENING_PUNCTUATION)
[uncategorized] ~179-~179: Loose punctuation mark.
Context: ...### Metrics Section Icons -\faIdCard: 🆔 for Researcher ID -\faOrcid: ORCI...(UNLIKELY_OPENING_PUNCTUATION)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro
⛔ Files ignored due to path filters (2)
Vatsal_CV-shortCV.pdfis excluded by!**/*.pdfVatsal_CV.pdfis excluded by!**/*.pdf
📒 Files selected for processing (3)
CLAUDE.md(1 hunks)Makefile(1 hunks)Vatsal_CV.tex(8 hunks)
🧰 Additional context used
🪛 LanguageTool
CLAUDE.md
[uncategorized] ~9-~9: Loose punctuation mark.
Context: ...y's curriculum vitae: - Vatsal_CV.tex: Comprehensive academic CV using modernc...
(UNLIKELY_OPENING_PUNCTUATION)
[uncategorized] ~84-~84: You might be missing the article “the” here.
Context: ... Key formatting rules: - Use\` at end of each line except the last - Page cou...
(AI_EN_LECTOR_MISSING_DETERMINER_THE)
[uncategorized] ~108-~108: You might be missing the article “the” here.
Context: ...er them from newest to oldest - Include year in parentheses at the end ### For mypu...
(AI_EN_LECTOR_MISSING_DETERMINER_THE)
[uncategorized] ~151-~151: Loose punctuation mark.
Context: ...ns ### Publication Symbols - \faFile: 📄 for open-access publications (replac...
(UNLIKELY_OPENING_PUNCTUATION)
[uncategorized] ~159-~159: Loose punctuation mark.
Context: ... ### Section Icons - \faUserGraduate: 🎓 for PhD Theses subsection - `\faGrad...
(UNLIKELY_OPENING_PUNCTUATION)
[uncategorized] ~169-~169: You might be missing the article “the” here.
Context: ...ard Icons - Note: No icons used in Major Awards & Achievements section to mainta...
(AI_EN_LECTOR_MISSING_DETERMINER_THE)
[uncategorized] ~174-~174: Loose punctuation mark.
Context: ...nly ### Funding Icons - \faLightbulb: 💡 for research fellowships and monetar...
(UNLIKELY_OPENING_PUNCTUATION)
[uncategorized] ~179-~179: Loose punctuation mark.
Context: ...### Metrics Section Icons - \faIdCard: 🆔 for Researcher ID - \faOrcid: ORCI...
(UNLIKELY_OPENING_PUNCTUATION)
🔇 Additional comments (9)
Vatsal_CV.tex (4)
26-30: Professional progression and contact updates look excellentThe career advancement from postdoctoral researcher to Assistant Professor is clearly reflected in the title, affiliation, and contact information updates. The transition to Durham University and the new comphy-lab.org domain demonstrates professional growth.
54-54: Education section enhancement improves clarityReplacing the CGPA notation with "Dept. Gold Medal" provides more meaningful context for international readers and better highlights the academic distinction achieved.
183-313: Publications section demonstrates excellent scholarly formattingThe numbered enumeration format, comprehensive DOI linking, and clear categorization between published works and works under review create a professional and accessible presentation. The use of FontAwesome icons for publication status (open access, covers, citations) adds visual clarity.
320-395: Talks and metrics sections show strong academic engagementThe extensive invited and contributed talks with YouTube links for recorded presentations demonstrate active academic participation. The summary metrics with proper linking to academic profiles provides easy verification of achievements.
Makefile (2)
11-11: Phony targets declaration is now completeGood improvement addressing the previous review comment - all referenced targets (
lint-tex,lint-bib,lint-lacheck,check-refs) are now properly declared in the.PHONYline, ensuring they work correctly as phony targets.
65-74: Bibliography linting addresses previous feedbackExcellent implementation that now checks both CV files for bibliography issues. The approach correctly runs
bibtex -terseon bothVatsal_CVandVatsal_CV-shortCVtargets with clear success messages for each, addressing the previous review suggestion.CLAUDE.md (3)
92-92: Publication count documentation is now consistentGood update - the documentation now correctly states "7 LATEST publications" which aligns with the actual implementation in
Vatsal_CV-shortCV.tex, resolving the previous inconsistency noted in past reviews.
126-134: Update protocol provides clear workflow guidanceThe step-by-step update process is well-structured and provides clear guidance for maintaining both CV versions consistently. The emphasis on updating the main CV first and then conditionally updating the short CV ensures proper workflow.
14-34: 🧹 Nitpick (assertive)Build commands section could include all available targets
The build commands section covers the basics well, but consider expanding it to include all the linting and validation targets mentioned in the Makefile for completeness.
Add the missing targets for a complete reference:
make lint # Run all linters (ChkTeX on both CV files) make lint-tex # Run ChkTeX linter on .tex files make lint-bib # Check bibliography for warnings/errors in both CVs make lint-lacheck # Run lacheck linter (if installed) +make lint-verbose # Run ChkTeX with verbose output make check-refs # Check for undefined references in both CVsLikely an incorrect or invalid review comment.
Summary
Changes Made
Contact Information
Visual Enhancements
Content Updates
Test plan