Instruction file imported from sampathvigneshmv/LibraryManagementSystem (.github/instructions/*.instructions.md). Copyright stays with the author.

Code Review Standards

Use these instructions whenever reviewing, updating, or generating code in this workspace.

Review Priorities

1. Correctness and behavior safety first.
2. Maintainability and readability second.
3. Style and consistency third.

Naming Convention (Mandatory)

1. Use PascalCase for all new and updated identifiers.
2. Do not introduce new camelCase identifiers.
3. When touching code that uses camelCase, prefer renaming to PascalCase if safe and in scope.
4. Keep existing public APIs stable unless a rename is explicitly requested or safely coordinated.

PascalCase Rule Examples

• Use: UserProfile, CalculateTotal, FetchBookRecords, IsAvailable
• Avoid: userProfile, calculateTotal, fetchBookRecords, isAvailable

Code Review Checklist

1. Confirm no behavioral regressions.
2. Confirm naming follows PascalCase in changed code.
3. Confirm logic is easy to read and has clear structure.
4. Confirm error handling is present where needed.
5. Confirm no unused variables, imports, or dead code remain.
6. Confirm changed code is minimal and focused on the task.

Scope and Safety

1. Prefer small, focused changes over large refactors.
2. Do not rewrite unrelated files during review fixes.
3. If a broad rename is needed, call it out clearly before applying it.