session-context

Generates a project orientation brief covering stack, services, git state, and conventions.

15|3|Updated Jul 9, 2026
One-click install
npx skills add https://github.com/thefear078/cursor-kit-for-ai --skill session-context-thefear078
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: session-context
Source: https://github.com/thefear078/cursor-kit-for-ai/tree/main/plugins/productivity/skills/session-context
Command: npx skills add https://github.com/thefear078/cursor-kit-for-ai --skill session-context-thefear078

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Opening an unfamiliar codebase or resuming a project after a break wastes time on unfocused exploration and risks building on top of uncommitted work. This Skill runs a targeted recon that produces a one-screen orientation brief with the stack, service map, current state, and the next logical move. ## Core Features & Use Cases - Ordered Recon Workflow: Reads identity files (README, package manifests), runtime files (docker-compose.yml, .env.example, entry points), git state (log, status, branches), and one representative feature to extract conventions. - Structured Orientation Brief: Outputs a Markdown brief with a project map table, in-flight work, recent commit direction, conventions to mirror, and a suggested next move. - Resume-After-Break Variant: Leads with the delta since the last session and proposes whether to finish, commit, or stash-and-restart WIP. - Use Case: You return to a FastAPI project after two weeks. The Skill checks git status and recent commits, maps services from docker-compose, and hands you a brief ending with the single most logical next task. ## Quick Start Ask the agent to orient itself in this project and produce a session context brief with the current state and suggested next move.

Frequently Asked Questions about session-context

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

FAQPage Schema
How do I quickly understand an unfamiliar codebase?▼

Start with the README and package manifest for the stack, then docker-compose.yml for the service map, then the entry point's imports and route registration. Finish with git log and git status to see current state before reading any implementation files.

How to resume a coding project after a long break?▼

Run git log --since with your last session date, check git status for uncommitted work, and read the last commit message to understand why work was left that way. Then decide to finish, commit, or stash-and-restart rather than building on mystery WIP.

What files should an AI agent read first in a new repo?▼

Read README.md, pyproject.toml or package.json, docker-compose.yml, .env.example, and the main entry point first. These reveal purpose, stack, services, integrations, and request flow without diving into implementation details.

Why check git status before starting work in a repository?▼

Git status reveals uncommitted in-flight changes that represent someone else's half-finished work. Ignoring it risks plowing over WIP or duplicating a feature that was already started on disk.

When is a full repository read better than a quick recon?▼

A quick recon fits orientation and task selection, but deep refactoring, security audits, or architectural changes require reading implementations thoroughly. The recon brief tells you which areas deserve that deeper read.