student-activity-analysis
Analyze student git activity, lab submissions, and project work for software engineering courses. Use when asked to "update student analysis", "check student activity", "analyze the class", or when working with student rosters and git repositories. Handles inconsistencies in student behavior like multiple usernames, name variations, and missing data.
npx skills add majiayu000/claude-skill-registry --skill nibzard-2025-intro-swe-claude-skills-student-activity-analysis --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Student Activity Analysis Skill ## When to Use This Skill Invoke this skill when the user: - Asks to "update the student activity analysis" - Asks "how are students doing?" or "check student progress" - Mentions checking class activity, lab submissions, or project work - Wants to see who has completed labs or is actively contributing - Needs to verify student participation or identify at-risk students ## Overview This skill automates the analysis of student git activity in a software engineering course. It reads from a canonical student roster (OFFICIAL_STUDENT_ROSTER.json), queries git history, checks file systems, and generates a comprehensive markdown report (STUDENT_ACTIVITY_ANALYSIS.md). ## Step-by-Step Instructions ### Step 0: Sync with Main Branch (CRITICAL) **Always start by syncing with the main branch** to ensure you're analyzing the latest activity: ```bash git fetch origin main git merge origin main -m "Sync with main before analysis" ``` ⚠️ **Why this is critical:** Without syncing, you may miss up to 76% of student activity that exists on the main branch but not on your current branch. ### Step 1: Collect Activity Data Run the data collection script: ```bash python3
- When to Use This Skill
- Overview
- Step-by-Step Instructions
- Step 0: Sync with Main Branch (CRITICAL)
- Step 1: Collect Activity Data
- Step 2: Generate Report
- Step 3: Review and Commit
- Handling Edge Cases
- Edge Case 1: Multiple GitHub Usernames
- Edge Case 2: Name Variations and Diacritics
- Edge Case 3: Lab Submissions in Wrong Location
- Edge Case 4: Stale or Orphaned Project Folders
- Edge Case 5: Team Lead with No Commits
- Validation and Error Handling
git fetch origin main git merge origin main -m "Sync with main before analysis" python3 .claude/skills/student-activity-analysis/collect_data.py python3 .claude/skills/student-activity-analysis/generate_report.py git add STUDENT_ACTIVITY_ANALYSIS.md STUDENT_ACTIVITY_DATA.json git commit -m "Update student activity analysis - $(date +%Y-%m-%d)" git push -u origin <branch-name> git log --all --author="jcuzic\|Zlicone" --oneline | wc -l find students/ -name "intro.py" -type f
What does the student-activity-analysis skill do?
Analyze student git activity, lab submissions, and project work for software engineering courses. Use when asked to "update student analysis", "check student activity", "analyze the class", or when working with student rosters and git repositories. Handles inconsistencies in student behavior like multiple usernames, name variations, and missing data.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill nibzard-2025-intro-swe-claude-skills-student-activity-analysis --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.