Loading article...
Loading article...
Stream/Area:
-
Subject:
-
Paper ID:
IJSREM64222
Volume:
10 |
5 |
May 2026
Pages:
1-6
Publication Frequency:
Monthly (12 issues per year)
License:International Journal of Scientific Research in Engineering and Management follows the Creative Commons Attribution 4.0 (CC BY 4.0) License, allowing free use and distribution with proper attribution.

Computer Science
Malnad College of Engineering

Computer Science
Malnad College of Engineering

Computer Science
Malnad College of Engineering

Computer Science
Malnad College of Engineering

Computer Science
Malnad College of Engineering
Most engineering teams today live inside platforms like GitHub or GitLab, where dozens of contributors push code from different time zones, often without much coordination. In any project of reasonable size, the repository never really sits still — commits accumulate, branches get created and collapsed, and Pull Requests arrive faster than anyone can comfortably read them. Staying on top of documentation and code review under those conditions is harder than it looks. Developers are not negligent; they’re simply busy shipping things. When something has to slip, it’s almost always the documentation that goes first — and review thoroughness follows not far behind. This paper presents CodeSage Docs, a system we built to take that burden off developers. It hooks into the standard Git workflow and uses Large Language Models to automatically interpret what changed, write commit summaries that actually make sense, keep documentation in step with the codebase, and give Pull Requests a first-pass review before a human reviewer even opens the diff. The plumbing underneath connects GitHub Webhooks to an Express.js server, runs inference through OpenAI’s API, and stores everything in MongoDB. The practical effect is less manual overhead, fewer things slipping through code review, and documentation that does not immediately become a lie the moment someone refactors a module.
KEYWORDS
Modern codebases move fast and have too many moving parts for manual documentation and review to keep up re- liably. That is not a failing of any particular team; it is just what happens when development velocity outpaces the tooling designed to support it. CodeSage Docs is our attempt to close that gap. Connecting GitHub’s event stream to an LLM-powered processing pipeline through an Express.js backend, with MongoDB holding the results, gives teams a system that genuinely tracks what is happening in their repository and does something useful with that information automatically. In practice, the automated commit summaries made code- bases easier to navigate. Documentation stopped being a manual chore. PR reviews caught things earlier. None of this is magic — the model makes mistakes, and a human reviewer is still essential for anything consequential. But having a reliable first pass, and having documentation that does not immediately drift from reality, noticeably reduces the friction of working in a large codebase. There is still plenty to build. Multi-repository support, natural language search, deeper security analysis, and a con- versational interface are all on the roadmap. The modular architecture was designed with that in mind, so adding them will not require rethinking the foundation. The broader point CodeSage Docs demonstrates is that AI is most effective when it is woven into the workflow rather than sitting next to it. When understanding a codebase is a continuous automated process rather than a periodic manual effort, teams can spend less time explaining what they built and more time building it.
[1] Y. Li et al., “Code Reviewer: Pre-Training for Automating Code Review Activities,” IEEE Transactions on Software Engineering, 2023. [2] S. Liu et al., “Auto Commit: Diff-Aware Transformer for Commit Message Generation,” Journal of Automated Software Engineering, 2024. [3] A. Gupta and M. Chen, “RAG-Based Software Repository Comprehen- sion,” ICSE Proceedings, 2025. [4] K. Patel, “Continuous Documentation Systems in Agile Development,” Software Engineering Journal, 2024. [5] B. Wang and H. Lee, “Semantic Code Diffing for AI-Based Code Review,” ACM SIGSOFT, 2025. [6] J. Doe et al., “Dev Agents: Autonomous DevOps Systems,” AI for Software Engineering Workshop, 2025. [7] R. Verma, “Vulnerability Detection in CI/CD Pipelines Using LLMs,” DevSecOps Journal, 2024. [8] H. Tan et al., “Deep Learning for Commit Message Generation,” IEEE Access, 2023. [9] OpenAI Research, “Large Language Models for Code Understanding,” 2023. [10] M. Smith et al., “GitHub Webhook-Based Event Processing Systems,” Cloud Computing Conference, 2022. [11] Y. Zhang et al., “AI-Assisted Software Engineering Survey,” IEEE Computing Surveys, 2025.
Publication Date
5/28/2026
Peer Review Type
Double-Blind Peer Review
Review Rounds: 2
Documents
Article Views
0
Total views since publication
PDF Downloads
3
Total downloads since publication
Geographic Reach
5
Digital Preservation: This article is permanently archived on Zenodo and complies with all data preservation standards across major indexing platforms.
Plagiarism Screening
This manuscript has been checked for plagiarism using TurnitinPlagiarismChecker software.
Conflict of Interest
The authors declare no conflict of interest related to this research work.
Funding Information
No funding information available for this research.
Related research in the same subject area
Loading similar articles...