@aethrekh/pi-cs 0.1.1 → 0.1.2

package/CHANGELOG.md

@@ -7,6 +7,22 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ---
 
+## 0.1.2 (2026-06-02)
+
+### Added
+- `/semester` skill with `--init`, `--update`, and `--status` modes — replaces the dead `semester-init` template that was never reachable as a slash command; `--init` scaffolds a new `SEMESTER.md`, `--update` edits fields without starting over, `--status` shows the full detected context
+- Full CS paper structure (9-section scaffold), IEEE LaTeX starter, and writing tips embedded in `/research --mode=review`
+
+### Changed
+- npm package name renamed to `@aethrekh/pi-cs`; install with `pi install npm:@aethrekh/pi-cs`
+- `publishConfig.directory` set to `dist/pack` so `pnpm publish` uses the compiled, Pi-ready layout
+
+### Fixed
+- `project-init` and `research-paper` templates removed from `pi-package.yaml`; `project-init` was redundant with content already inline in the `/project` skill, and `research-paper` content is now live inside the `/research` skill where the LLM can actually use it
+- README configuration section corrected from YAML to JSON format
+
+---
+
 ## 0.1.1 (2026-06-02)
 
 ### ### Added

package/README.md

@@ -15,6 +15,7 @@ It covers every dimension of a CS degree:
 
 | Need | Command | What it does |
 |---|---|---|
+| Set up semester context | `/semester` | Init, update, or inspect your `SEMESTER.md` context |
 | Stuck on an assignment | `/homework` | Hints, pseudocode, guided walkthrough — no cheating |
 | Starting a new project | `/project` | Requirements → architecture → scaffolded codebase |
 | Code review before submitting | `/review` | Strict TA-level review with severity tiers |
@@ -29,13 +30,13 @@ It covers every dimension of a CS degree:
 
 ```bash
 # Install pi-cs
-pi install npm:pi-cs
+pi install npm:@aethrekh/pi-cs
 
 # Navigate to your university folder
 cd ~/university/fall2025
 
 # Initialize your semester context
-/semester-init
+/semester
 
 # Start working
 /homework
@@ -71,6 +72,16 @@ Pisces auto-detects this file at startup and greets you with relevant context:
 
 ## Skills Reference
 
+### `/semester`
+Semester context management. Three modes:
+
+```
+/semester            # status if SEMESTER.md exists, prompts --init if not
+/semester --init     # scaffold a new SEMESTER.md interactively
+/semester --update   # update week, courses, active project, or other fields
+/semester --status   # show everything Pisces currently detects
+```
+
 ### `/homework`
 Guided learning mode. Pisces uses the Socratic method — hints, pseudocode, and guided questions. **Never produces complete submittable solutions for graded work.**
 
@@ -152,21 +163,28 @@ When Pisces detects a potential integrity issue, it redirects to guided learning
 
 ## Configuration
 
-Customize Pisces behavior in your Pi config:
-
-```yaml
-# ~/.pi/config.yaml (pi-cs section)
-pi-cs:
-  student:
-    name: Alex
-    year_of_study: 2
-    primary_language: python
-  explanations:
-    default_depth: intermediate
-    prefer_visuals: true
-  productivity:
-    burnout_nudges: true
-    session_warning_minutes: 180
+Create a `.pi-cs.json` file to override defaults. Pisces checks these locations in order, first match wins:
+
+1. `.pi-cs.json` in the current working directory (project-level)
+2. `~/.pi/pi-cs.json` (user-level)
+3. `~/.config/pi-cs/config.json`
+
+```json
+{
+  "student": {
+    "name": "Alex",
+    "year_of_study": 2,
+    "primary_language": "python"
+  },
+  "explanations": {
+    "default_depth": "intermediate",
+    "prefer_visuals": true
+  },
+  "productivity": {
+    "burnout_nudges": true,
+    "session_warning_minutes": 180
+  }
+}
 ```
 
 See [`config/schema.json`](config/schema.json) for the full configuration reference.
@@ -178,7 +196,7 @@ See [`config/schema.json`](config/schema.json) for the full configuration refere
 **Requirements:** Pi >= 1.0.0, Node.js >= 18
 
 ```bash
-pi install npm:pi-cs
+pi install npm:@aethrekh/pi-cs
 ```
 
 That's it. Pisces activates automatically in every Pi session.
@@ -193,22 +211,21 @@ pi-cs/
 ├── pi-package.yaml              # Package manifest
 ├── src/
 │   ├── skills/
-│   │   ├── homework/SKILL.md    # /homework skill
-│   │   ├── project/SKILL.md     # /project skill
-│   │   ├── review/SKILL.md      # /review skill
-│   │   ├── explain/SKILL.md     # /explain skill
-│   │   ├── leetcode/SKILL.md    # /leetcode skill
-│   │   ├── exam/SKILL.md        # /exam skill
-│   │   └── research/SKILL.md    # /research skill
+│   │   ├── semester/SKILL.md       # /semester skill
+│   │   ├── homework/SKILL.md       # /homework skill
+│   │   ├── project/SKILL.md        # /project skill
+│   │   ├── review/SKILL.md         # /review skill
+│   │   ├── explain/SKILL.md        # /explain skill
+│   │   ├── leetcode/SKILL.md       # /leetcode skill
+│   │   ├── exam/SKILL.md           # /exam skill
+│   │   └── research/SKILL.md       # /research skill
 │   ├── extensions/
-│   │   ├── semester-detector.ts # Auto-loads SEMESTER.md
-│   │   ├── folder-detector.ts   # Detects CS folder structures
-│   │   ├── integrity-guard.ts   # Academic integrity monitoring
-│   │   └── progress-tracker.ts  # Weekly stats & burnout nudges
+│   │   ├── semester-detector.ts    # Auto-loads SEMESTER.md
+│   │   ├── folder-detector.ts      # Detects CS folder structures
+│   │   ├── integrity-guard.ts      # Academic integrity monitoring
+│   │   └── progress-tracker.ts     # Weekly stats & burnout nudges
 │   └── templates/
-│       ├── semester-init.md     # SEMESTER.md template
-│       ├── project-init.md      # CS project bootstrap template
-│       └── research-paper.md    # Academic paper structure template
+│       └── semester-init.md        # SEMESTER.md raw template
 ├── config/
 │   ├── schema.json              # Config schema
 │   └── defaults.json            # Default values
@@ -221,7 +238,7 @@ pi-cs/
 
 ## Roadmap
 
-- [x] 7 core skills
+- [x] 8 core skills
 - [x] 4 background extensions
 - [x] Semester context system
 - [x] Academic integrity guard

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@aethrekh/pi-cs",
-  "version": "0.1.1",
+  "version": "0.1.2",
   "description": "Pisces — The CS Student Edition for Pi Coding Agent. Your personal AI teaching assistant from homework to thesis.",
   "keywords": [
     "academic",

package/pi-cs.meta.json

@@ -1,7 +1,7 @@
 {
   "name": "pi-cs",
-  "version": "0.1.1",
-  "built_at": "2026-06-02T06:13:15.521Z",
+  "version": "0.1.2",
+  "built_at": "2026-06-02T08:57:02.495Z",
   "entry": "index.js",
   "node_minimum": "18.0.0"
 }

package/pi-package.yaml

@@ -1,5 +1,5 @@
 name: pi-cs
-version: 0.1.1
+version: 0.1.2
 display_name: "pi-cs (Pisces)"
 description: "The CS Student Edition for Pi — Your personal AI teaching assistant for Computer Science, from homework to thesis."
 icon: public/pisces-logo-512.png
@@ -33,6 +33,9 @@ skills:
   - name: research
     path: skills/research/SKILL.md
     description: "Paper summarization, arXiv search, and literature review assistance"
+  - name: semester
+    path: skills/semester/SKILL.md
+    description: "Manage semester context: scaffold a new SEMESTER.md (--init), update fields (--update), or inspect what Pisces detects (--status)"
 
 # Extensions that run automatically in the background
 extensions:
@@ -64,12 +67,6 @@ templates:
   - name: semester-init
     path: templates/semester-init.md
     description: "Initialize a new semester workspace with SEMESTER.md and folder structure"
-  - name: project-init
-    path: templates/project-init.md
-    description: "Bootstrap a new CS project with README, structure, and CI"
-  - name: research-paper
-    path: templates/research-paper.md
-    description: "Academic research paper structure and writing guide"
 
 # User-level config schema
 config:

package/skills/research/SKILL.md

@@ -137,7 +137,7 @@ in Proc. NIPS, 2017, vol. 30.
 
 ### Mode: Review (`--mode=review`)
 
-Help write a literature review section:
+Help write a literature review section or a full research paper:
 
 1. Ask for: topic, papers to include, section length, target audience (course report vs journal)
 2. Produce an outline first — confirm before writing
@@ -145,6 +145,63 @@ Help write a literature review section:
 4. Include proper in-text citations
 5. End with a "gap statement" that motivates the student's own work
 
+When the student needs a full paper structure, use this as the reference scaffold:
+
+#### Standard CS Paper Structure
+
+1. **Title & Abstract** (150–250 words) — Problem → Approach → Results → Contribution
+2. **Introduction** — motivate the problem, state contributions as a bullet list, outline the paper
+3. **Background / Related Work** — group by theme not chronology; seminal papers + recent advances
+4. **Problem Formulation** — formal definition, assumptions, notation
+5. **Approach / Methodology** — proposed solution, algorithm/system design with diagrams, justification
+6. **Evaluation / Experiments** — setup, metrics, results with tables/figures, ablation studies
+7. **Discussion** — interpret results, limitations, threats to validity
+8. **Conclusion** — summarise contributions, future work
+9. **References** — consistent citation style (IEEE, ACM, or as required)
+
+#### LaTeX Starter (IEEE Style)
+
+```latex
+\documentclass[conference]{IEEEtran}
+\usepackage{cite}
+\usepackage{amsmath}
+\usepackage{graphicx}
+\usepackage{hyperref}
+
+\begin{document}
+
+\title{Your Paper Title}
+\author{
+  \IEEEauthorblockN{Your Name}
+  \IEEEauthorblockA{Department of Computer Science\\
+  Your University}
+}
+\maketitle
+
+\begin{abstract}
+Your abstract here (150--250 words).
+\end{abstract}
+
+\section{Introduction}
+\section{Related Work}
+\section{Methodology}
+\section{Evaluation}
+\section{Conclusion}
+
+\bibliographystyle{IEEEtran}
+\bibliography{references}
+
+\end{document}
+```
+
+#### Writing Tips to Surface
+
+- Every figure needs a caption that stands alone without reading the text
+- Every claim needs evidence — cite or show data
+- Define every symbol the first time it appears
+- Use consistent terminology — one word per concept throughout
+- Common mistakes: vague problem statements, missing baselines, burying contributions mid-introduction, figures with unreadable font sizes
+
 ---
 
 ## Research Integrity Notes

package/skills/semester/SKILL.md

@@ -0,0 +1,129 @@
+---
+name: semester
+description: Manage semester context. Scaffolds a new SEMESTER.md, updates fields in an existing one, or shows what Pisces currently detects. Use when a student wants to set up or refresh their academic context.
+---
+
+## Purpose
+The central command for managing semester context — the primary signal Pisces uses to personalize every session. Supports three modes: initialize, update, and status.
+
+## Activation
+```
+/semester                     # shows status if SEMESTER.md exists, prompts --init if not
+/semester --init              # scaffold a new SEMESTER.md interactively
+/semester --update            # update fields in the existing SEMESTER.md
+/semester --status            # show what Pisces currently detects
+```
+
+---
+
+## Mode: `--init`
+
+Run when no `SEMESTER.md` exists yet, or when starting a fresh semester.
+
+### Step 1 — Collect Details
+Ask for all of the following in a single message (do not ask one at a time):
+
+1. **Semester and year** — e.g., Fall 2025, Spring 2026
+2. **Current week of semester** — integer, e.g., 1
+3. **Year of study** — 1 (freshman) through 6 (graduate)
+4. **Courses this semester** — each as `COURSECODE: Course Name`, e.g., `CS301: Operating Systems`. Accept as many as they have. Gently correct codes that don't match `[A-Z]{2,4}\d{2,4}` (e.g., "cs301" → "CS301").
+5. **Active project** — current assignment or project (or "none")
+6. **Primary language** — language they write most code in this semester
+7. **Anything they feel weak on** — optional
+
+If the student provides some details inline when invoking `/semester --init`, pre-fill what is already known and only ask for what is missing.
+
+### Step 2 — Generate SEMESTER.md
+Produce the complete file as a fenced `markdown` code block with real values — no placeholder text. Use this exact structure:
+
+```
+semester: <semester> <year>
+year: <year>
+week: <week>
+year_of_study: <year_of_study>
+
+## Courses
+
+<one line per course: - COURSECODE: Course Name>
+
+## Active Project
+
+active_project: <project name and course, or "none">
+
+## Current Focus
+
+Working on: <active project or first task>
+Upcoming: <first deadline or exam if mentioned, else leave blank>
+Feeling weak on: <weak topics, else leave blank>
+
+## Notes
+
+Primary language: <language>
+```
+
+Do not include any comment block — that belongs only in the raw template file.
+
+### Step 3 — Save Instructions
+Tell the student:
+- **Recommended location:** `~/university/SEMESTER.md` — Pisces finds it from any course subdirectory
+- Saving to the current directory also works
+- Reloads automatically on every `cd` — no restart needed
+- Update `week:` each week and `active_project:` whenever it changes
+
+### Step 4 — Live Preview
+Greet the student using their actual semester context to show personalization working immediately.
+
+---
+
+## Mode: `--update`
+
+Run when the student wants to change one or more fields without starting from scratch.
+
+### Step 1 — Identify What to Change
+Ask: *"What would you like to update? (e.g., week number, active project, courses, semester, year of study, weak topics)"*
+
+Common update patterns:
+- **Weekly update** — ask for new `week:` value and new `active_project:` if changed
+- **New semester** — ask for new semester, year, week (reset to 1), courses, and year_of_study
+- **Course change** — add or remove a course from the list
+- **Weak topics** — replace the "Feeling weak on" line
+
+### Step 2 — Output the Updated File
+Show a brief summary of what changed, then output the complete updated `SEMESTER.md` as a fenced code block so the student can copy-paste it wholesale. Never output a partial file that would leave the student manually merging.
+
+---
+
+## Mode: `--status`
+
+Run to inspect what Pisces currently detects without changing anything.
+
+Output a structured summary of the active session context:
+
+```
+Semester Context
+────────────────────────────────────────
+Source:          ~/university/SEMESTER.md (or "not found")
+Semester:        Fall 2025, Week 7
+Year of study:   2nd year
+Courses:         CS301, CS315, CS320, MATH210
+Active project:  shell-implementation (CS301)
+Feeling weak on: Virtual memory, page tables
+────────────────────────────────────────
+Folder context:  CS301 project detected (cpp, has tests, has CI)
+```
+
+If no `SEMESTER.md` is found, say so clearly and offer to run `--init`.
+
+---
+
+## Default Behavior (no flag)
+
+- If a `SEMESTER.md` is detected in the session: behave as `--status`, then ask if the student wants to `--update` anything.
+- If no `SEMESTER.md` is detected: explain that it's missing and ask if the student wants to run `--init` now.
+
+---
+
+## Constraints
+- Never produce placeholder text in generated file output — use real values from what the student told you, or omit the field if unknown.
+- Keep the SEMESTER.md format exactly as shown so the semester-detector extension can parse it correctly.
+- Course codes must match `[A-Z]{2,4}\d{2,4}` — gently correct any that do not.