nodefony-session

Manages Nodefony development session lifecycle with resume, start, end, and consolidate modes.

Updated Dec 19, 2023
One-click install
npx skills add https://github.com/nodefony/nodefony-core --skill nodefony-session-nodefony
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nodefony-session
Source: https://github.com/nodefony/nodefony-core/tree/main/.claude/skills/nodefony-session
Command: npx skills add https://github.com/nodefony/nodefony-core --skill nodefony-session-nodefony

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? After a context reset (like /clear), an AI assistant loses track of where work on the Nodefony framework left off, and hand-written status documents go stale between sessions. This Skill restores the real state of work by reading GitHub milestones and tickets rather than stale notes, prepares module context at session start, and closes sessions with retrospectives, ticket closure, and a resumption memory. ## Core Features & Use Cases - RESUME mode: Rebuilds the true project state after a context reset by cross-checking the last session memory against git commits and a generated GitHub board snapshot (.ai/BOARD.md), then names the single next ticket from the current milestone. - START mode: Bootstraps a module's working context (CLAUDE.md/MEMORY.md, git status, dist freshness, exported symbols) in under 40 lines of output. - END / CONSOLIDATE modes: Closes a session by updating the RETEX digest, closing solved GitHub tickets with reports, regenerating the board snapshot and pinned dashboard issue, and writing a resumption memory. - Migration audit: Compares MIGRATION_STATUS.md against the actual code, phase by phase, with scripted counting instead of manual tallies. - Use Case: After losing context mid-migration, say "reprends" and the Skill verifies GitHub reachability, refreshes the ticket snapshot, detects that the saved state file is stale relative to recent commits, and tells you the exact next ticket in the current milestone. ## Quick Start Say "reprends" to resume where the last Nodefony session left off, or invoke the skill with a module name like "http" to prepare that module's working context.

Frequently Asked Questions about nodefony-session

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I resume work after a context reset in an AI coding session?

Say "reprends" to trigger RESUME mode, which reads the latest session state memory, cross-checks it against recent git commits, and refreshes the GitHub ticket snapshot. It then names the single next ticket from the current milestone rather than trusting stale hand-written priorities.

How does the skill track project progress without manual status documents?

It generates a committed snapshot of the GitHub project board (`.ai/BOARD.md` and `.ai/board.json`) via paginated GraphQL queries using board-snapshot.mjs. The snapshot is never hand-edited, so it cannot diverge from its source, and it works offline with a stated freshness date.

Can the board snapshot script run when GitHub is unreachable?

When GitHub is unreachable, the script preserves the existing snapshot instead of overwriting it with empty data, and exits with a distinct code signaling the state was not verified. It also refuses to write when the item count drops suspiciously unless forced.

Why does the skill read the issue title instead of the project board title field?

The board item title field is a stale derived copy; measurement showed 38 of 38 items carried an outdated label. The GraphQL content title returns the current issue title, so the skill always reads `.content.title`.

What happens at the end of a Nodefony development session?

END mode updates the RETEX digest with the session's frictions, closes solved GitHub tickets with a completion report, demotes stale In Progress tickets, regenerates the board snapshot and pinned dashboard issue, writes a resumption memory, and commits both the project and the AI memory repository.