feat: update BT-301 syllabus, PYQs, and creators page#26
Closed
RamuuXfree wants to merge 1 commit into
Closed
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
📝 WalkthroughWalkthroughAdds complete syllabus and past-year question (PYQ) JSON files for subject AL-301 (Technical Communication) under the RGPV AI&ML semester-3 content directory. Also updates the ChangesAL-301 Content and Creator Profile
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~5 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
⚔️ Resolve merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 4
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@content/rgpv/aiml/semester-3/bt-301/pyqs.json`:
- Around line 790-793: The December 2025 entry in the PYQ JSON is still flagged
as predicted even though that session is already in the past; update the bt-301
dataset entry so the prediction status matches the exam timing. Either change
the "exam"/"year"/"month" fields to a future session if this is intended as a
forecast, or remove the "isPredicted" field from this record if it is a real
past paper.
- Around line 638-650: Retag the June 2025 questions so they match the syllabus
mapping: update q1a and q1b in the pyqs data from Unit 1/communication-skills to
the correct units and module-aligned type based on the existing quiz/question
structure. Use q1a and q1b to locate the entries, and ensure q1a is assigned to
Module 3 and q1b to Module 2 so unit filters and analytics stay consistent.
In `@content/rgpv/aiml/semester-3/bt-301/syllabus.json`:
- Around line 3-6: The embedded subject metadata is mismatched with the bt-301
content path, so update the identifiers in the syllabus payload to use the
bt-301 subject code consistently. In the syllabus JSON, change the values for
the id, code, name, and title fields so they match the bt-301 route and the rest
of the sibling content, keeping the Technical Communication entry aligned with
that subject.
- Around line 26-216: The question reference arrays in the syllabus JSON use IDs
that do not exist in pyqs.json, so the module-to-question links cannot resolve.
Update the questionIds and predictedQuestionIds in the affected module entries
to use the same local ID namespace defined by the pyqs data, matching symbols
from the syllabus module objects and the pyqs question IDs. If the intended
linkage is by global IDs, add a consistent shared identifier field to pyqs.json
and use that everywhere instead of the current local-only ids.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: d9bb31ad-7bfc-4bda-ba86-be3fb52c8c0f
📒 Files selected for processing (3)
app/(public)/creators/page.tsxcontent/rgpv/aiml/semester-3/bt-301/pyqs.jsoncontent/rgpv/aiml/semester-3/bt-301/syllabus.json
Comment on lines
+638
to
+650
| { | ||
| "id": "q1a", | ||
| "label": "a)", | ||
| "text": "Explain the importance of understanding the audience in technical communication. Provide two examples.", | ||
| "unit": "Unit 1", | ||
| "type": "communication-skills" | ||
| }, | ||
| { | ||
| "id": "q1b", | ||
| "label": "b)", | ||
| "text": "How do advancements in technology enhance communication in a globalized environment?", | ||
| "unit": "Unit 1", | ||
| "type": "communication-skills" |
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win
Retag these June 2025 questions to the correct units.
q1a is about audience awareness, which content/rgpv/aiml/semester-3/bt-301/syllabus.json places in Module 3, and q1b is about communication in a globalized environment, which the syllabus places in Module 2. Keeping both under Unit 1 / communication-skills will misfile them in unit/type filters and any derived analytics.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@content/rgpv/aiml/semester-3/bt-301/pyqs.json` around lines 638 - 650, Retag
the June 2025 questions so they match the syllabus mapping: update q1a and q1b
in the pyqs data from Unit 1/communication-skills to the correct units and
module-aligned type based on the existing quiz/question structure. Use q1a and
q1b to locate the entries, and ensure q1a is assigned to Module 3 and q1b to
Module 2 so unit filters and analytics stay consistent.
Comment on lines
+790
to
+793
| "exam": "December 2025", | ||
| "year": 2025, | ||
| "month": "December", | ||
| "isPredicted": true, |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
A December 2025 paper should not still be marked predicted on June 28, 2026.
If this is meant to be the forecast set, the exam date needs to move to a future session; otherwise isPredicted should be removed. Leaving a past session flagged as predicted is misleading in a PYQ dataset.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@content/rgpv/aiml/semester-3/bt-301/pyqs.json` around lines 790 - 793, The
December 2025 entry in the PYQ JSON is still flagged as predicted even though
that session is already in the past; update the bt-301 dataset entry so the
prediction status matches the exam timing. Either change the
"exam"/"year"/"month" fields to a future session if this is intended as a
forecast, or remove the "isPredicted" field from this record if it is a real
past paper.
Comment on lines
+3
to
+6
| "id": "al-301", | ||
| "code": "AL-301", | ||
| "name": "Technical Communication", | ||
| "title": "AL-301 – Technical Communication", |
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win
Keep the embedded subject metadata aligned with the bt-301 path.
This file is stored under content/rgpv/aiml/semester-3/bt-301, but the payload advertises al-301 / AL-301. That will surface the wrong subject code in the UI and can desync this file from sibling content loaded from the bt-301 route.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@content/rgpv/aiml/semester-3/bt-301/syllabus.json` around lines 3 - 6, The
embedded subject metadata is mismatched with the bt-301 content path, so update
the identifiers in the syllabus payload to use the bt-301 subject code
consistently. In the syllabus JSON, change the values for the id, code, name,
and title fields so they match the bt-301 route and the rest of the sibling
content, keeping the Technical Communication entry aligned with that subject.
Comment on lines
+26
to
+216
| "questionIds": [ | ||
| "al301_m1_nov2022_q1", | ||
| "al301_m1_nov2022_q2", | ||
| "al301_m1_dec2023_q2", | ||
| "al301_m1_dec2023_q3", | ||
| "al301_m1_dec2023_q4", | ||
| "al301_m1_june2024_q4", | ||
| "al301_m1_june2024_q5", | ||
| "al301_m1_dec2024_q4", | ||
| "al301_m1_dec2024_q5", | ||
| "al301_m1_dec2024_q6", | ||
| "al301_m1_dec2024_q7", | ||
| "al301_m1_june2025_q4", | ||
| "al301_m1_june2025_q7", | ||
| "al301_m1_june2025_q8" | ||
| ], | ||
| "predictedQuestionIds": [ | ||
| "al301_m1_predicted_q1", | ||
| "al301_m1_predicted_q2", | ||
| "al301_m1_predicted_q3", | ||
| "al301_m1_predicted_q4", | ||
| "al301_m1_predicted_q5" | ||
| ] | ||
| }, | ||
| { | ||
| "id": "module-2", | ||
| "number": 2, | ||
| "title": "Types of Communication & Soft Skills", | ||
| "hours": null, | ||
| "topics": [ | ||
| "Verbal & Non-verbal Communication, Classification of NVC", | ||
| "Barriers to Communication", | ||
| "Communicating Globally, Culture and Communication", | ||
| "Interpersonal Communication", | ||
| "Listening, Persuasion, Negotiation", | ||
| "Communicating bad news/messages", | ||
| "communicating in a global world" | ||
| ], | ||
| "questionIds": [ | ||
| "al301_m2_nov2022_q1", | ||
| "al301_m2_nov2022_q2", | ||
| "al301_m2_dec2023_q2", | ||
| "al301_m2_dec2023_q3", | ||
| "al301_m2_dec2023_q4", | ||
| "al301_m2_dec2023_q5", | ||
| "al301_m2_june2024_q2", | ||
| "al301_m2_june2024_q4", | ||
| "al301_m2_june2024_q5", | ||
| "al301_m2_dec2024_q5", | ||
| "al301_m2_dec2024_q6", | ||
| "al301_m2_dec2024_q7", | ||
| "al301_m2_dec2024_q8", | ||
| "al301_m2_june2025_q1", | ||
| "al301_m2_june2025_q2", | ||
| "al301_m2_june2025_q9", | ||
| "al301_m2_june2025_q10" | ||
| ], | ||
| "predictedQuestionIds": [ | ||
| "al301_m2_predicted_q1", | ||
| "al301_m2_predicted_q2", | ||
| "al301_m2_predicted_q3", | ||
| "al301_m2_predicted_q4", | ||
| "al301_m2_predicted_q5" | ||
| ] | ||
| }, | ||
| { | ||
| "id": "module-3", | ||
| "number": 3, | ||
| "title": "Writing Skills & Speaking Skills", | ||
| "hours": null, | ||
| "topics": [ | ||
| "Traits of Technical Writing, Principles of Business Writing, Style of Writing", | ||
| "Writing Memos, Letters, Reports, and Types of technical reports", | ||
| "Characteristics, format and structure of technical reports", | ||
| "Writing Research Papers", | ||
| "Audience-awareness, Voice, Vocabulary and Paralanguage", | ||
| "Group Discussion, Combating Nervousness", | ||
| "Speaking to one and to one thousand, Mock Presentations" | ||
| ], | ||
| "questionIds": [ | ||
| "al301_m3_nov2022_q1", | ||
| "al301_m3_nov2022_q2", | ||
| "al301_m3_dec2023_q2", | ||
| "al301_m3_dec2023_q3", | ||
| "al301_m3_dec2023_q4", | ||
| "al301_m3_dec2023_q5", | ||
| "al301_m3_dec2023_q6", | ||
| "al301_m3_dec2023_q7", | ||
| "al301_m3_june2024_q1", | ||
| "al301_m3_june2024_q8", | ||
| "al301_m3_june2024_q9", | ||
| "al301_m3_june2024_q10", | ||
| "al301_m3_dec2024_q5", | ||
| "al301_m3_dec2024_q7", | ||
| "al301_m3_dec2024_q8", | ||
| "al301_m3_dec2024_q10", | ||
| "al301_m3_dec2024_q11", | ||
| "al301_m3_june2025_q7", | ||
| "al301_m3_june2025_q8", | ||
| "al301_m3_june2025_q12", | ||
| "al301_m3_june2025_q13" | ||
| ], | ||
| "predictedQuestionIds": [ | ||
| "al301_m3_predicted_q1", | ||
| "al301_m3_predicted_q2", | ||
| "al301_m3_predicted_q3", | ||
| "al301_m3_predicted_q4", | ||
| "al301_m3_predicted_q5" | ||
| ] | ||
| }, | ||
| { | ||
| "id": "module-4", | ||
| "number": 4, | ||
| "title": "Job Interviews, GD & Presentations", | ||
| "hours": null, | ||
| "topics": [ | ||
| "Preparing for interviews, assessing yourself", | ||
| "Drafting Effective Resume", | ||
| "Dress, decorum and Delivery techniques", | ||
| "Techniques of handling interviews", | ||
| "Use of Nonverbals during Interviews", | ||
| "Handling turbulence during interviews", | ||
| "Group Discussion: Objective, Method, Focus, Content, Style and Argumentation skills", | ||
| "Professional Presentations: Individual Presentations (Audience Awareness, Body Language, Delivery and Content of Presentation)" | ||
| ], | ||
| "questionIds": [ | ||
| "al301_m4_nov2022_q1", | ||
| "al301_m4_nov2022_q2", | ||
| "al301_m4_nov2022_q3", | ||
| "al301_m4_nov2022_q4", | ||
| "al301_m4_nov2022_q5", | ||
| "al301_m4_dec2023_q6", | ||
| "al301_m4_dec2023_q7", | ||
| "al301_m4_june2024_q1", | ||
| "al301_m4_june2024_q2", | ||
| "al301_m4_june2024_q3", | ||
| "al301_m4_june2024_q8", | ||
| "al301_m4_dec2024_q8", | ||
| "al301_m4_dec2024_q9", | ||
| "al301_m4_june2025_q7", | ||
| "al301_m4_june2025_q8", | ||
| "al301_m4_june2025_q10", | ||
| "al301_m4_june2025_q11", | ||
| "al301_m4_june2025_q12" | ||
| ], | ||
| "predictedQuestionIds": [ | ||
| "al301_m4_predicted_q1", | ||
| "al301_m4_predicted_q2", | ||
| "al301_m4_predicted_q3", | ||
| "al301_m4_predicted_q4", | ||
| "al301_m4_predicted_q5" | ||
| ] | ||
| }, | ||
| { | ||
| "id": "module-5", | ||
| "number": 5, | ||
| "title": "Grammar & Linguistic Ability", | ||
| "hours": null, | ||
| "topics": [ | ||
| "Basics of grammar, common error in writing and speaking", | ||
| "Study of advanced grammar", | ||
| "Vocabulary, Pronunciation Etiquette", | ||
| "Syllables, Vowel sounds, Consonant sounds", | ||
| "Tone: Rising tone, Falling Tone", | ||
| "Flow in Speaking, Speaking with a purpose", | ||
| "Speech & personality, Professional Personality Attributes" | ||
| ], | ||
| "questionIds": [ | ||
| "al301_m5_nov2022_q1", | ||
| "al301_m5_nov2022_q2", | ||
| "al301_m5_dec2023_q3", | ||
| "al301_m5_dec2023_q4", | ||
| "al301_m5_dec2023_q5", | ||
| "al301_m5_dec2023_q6", | ||
| "al301_m5_dec2023_q7", | ||
| "al301_m5_june2024_q2", | ||
| "al301_m5_june2024_q5", | ||
| "al301_m5_june2024_q6", | ||
| "al301_m5_dec2024_q1", | ||
| "al301_m5_dec2024_q3", | ||
| "al301_m5_dec2024_q8", | ||
| "al301_m5_june2025_q9", | ||
| "al301_m5_june2025_q10" | ||
| ], | ||
| "predictedQuestionIds": [ | ||
| "al301_m5_predicted_q1", | ||
| "al301_m5_predicted_q2", | ||
| "al301_m5_predicted_q3", | ||
| "al301_m5_predicted_q4", | ||
| "al301_m5_predicted_q5" | ||
| ] |
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🟠 Major | 🏗️ Heavy lift
These syllabus question references do not match the IDs defined in pyqs.json.
The arrays here use IDs like al301_m1_nov2022_q1, but content/rgpv/aiml/semester-3/bt-301/pyqs.json only defines local IDs such as q1, q1a, q2b, etc. Without a shared ID namespace, any module-to-question linking based on these arrays cannot resolve.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@content/rgpv/aiml/semester-3/bt-301/syllabus.json` around lines 26 - 216, The
question reference arrays in the syllabus JSON use IDs that do not exist in
pyqs.json, so the module-to-question links cannot resolve. Update the
questionIds and predictedQuestionIds in the affected module entries to use the
same local ID namespace defined by the pyqs data, matching symbols from the
syllabus module objects and the pyqs question IDs. If the intended linkage is by
global IDs, add a consistent shared identifier field to pyqs.json and use that
everywhere instead of the current local-only ids.
imuniqueshiv
approved these changes
Jun 29, 2026
Owner
|
@RamuuXfree Please resolve conflicts and try again. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pull Request
Summary
Updated the AI/ML Semester III BT-301 content by adding the complete syllabus and previous year question papers. Also updated the creators page to reflect the contributor's role.
Related Issue
N/A
Type of Change
What Changed?
Screenshots (UI Changes Only)
N/A
Testing
npx prettier --write.npm run format:check.npm run lint.npm run typecheck.npm run build.Checklist
main.npx prettier --write <file>).npm run format:checkpasses.npm run lintpasses.npm run typecheckpasses.npm run buildpasses.Additional Notes
This PR expands the BT-301 study resources by including structured syllabus content, previous year question papers, and predicted questions while also updating contributor information on the Creators page.
Summary by CodeRabbit
New Features
Bug Fixes