li-sense

Loads session memory and inspects repository state to scope incoming requests.

Updated May 27, 2026
One-click install
npx skills add https://github.com/jokerman89/lintel --skill li-sense-jokerman89
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: li-sense
Source: https://github.com/jokerman89/lintel/tree/main/.github/skills/li-sense
Command: npx skills add https://github.com/jokerman89/lintel --skill li-sense-jokerman89

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Starting a new coding session without context wastes time re-explaining prior decisions and repository state. This Skill loads relevant memory, inspects the current repository, and scopes the user's request so the session begins with shared context. ## Core Features & Use Cases - Memory Loading: Retrieves committed lessons, architecture decisions, and working state from the repository at session start. - Repository Inspection: Examines the current state of the working repository before any planning or implementation begins. - Request Scoping: Executes the canonical sense workflow through the Copilot adapter contract, following its tool mapping, authorization, and verification rules. - Use Case: A developer opens a project in GitHub Copilot and invokes the sense workflow so the agent recalls prior decisions and understands the repository before scoping a new feature request. ## Quick Start Ask your Copilot agent to run the li-sense skill to load session memory and scope your request before starting work.

Frequently Asked Questions about li-sense

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

FAQPage Schema
How do I load prior session context in GitHub Copilot?▼

Invoke the li-sense skill at session start to load committed lessons, decisions, and working state from the repository. It executes the canonical sense workflow through the Copilot adapter contract before scoping your request.

What does the li-sense skill do before planning work?▼

It reads the Copilot adapter contract, then runs the canonical sense workflow to load memory, inspect repository state, and scope the user's request. Outputs are written to the working repository.

Can I use li-sense with clients other than GitHub Copilot?▼

The skill is defined as a Copilot adapter that delegates to a canonical sense workflow. The Lintel repository describes keeping the same workflow across clients like Claude Code or Codex through their own adapters.

Why does li-sense reference files outside its own directory?▼

It is a thin adapter that points to the canonical sense workflow and Copilot contract elsewhere in the repository. Source resources resolve relative to the canonical file, while outputs are written to the working repository.

When should I run the sense workflow in a session?▼

Run it at session start, before planning or implementation. Its description specifies it is used to load relevant memory, inspect repository state, and scope the incoming request.