session-start

Establishes session context by checking GitHub project state, repository status, and memory before work.

Updated Jan 1, 2026
One-click install
npx skills add https://github.com/sarkarshivaditya-lab/WellMate --skill session-start-sarkarshivaditya-lab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: session-start
Source: https://github.com/sarkarshivaditya-lab/WellMate/tree/main/.engineering-skills/troykelly-claude-skills/skills/session-start
Command: npx skills add https://github.com/sarkarshivaditya-lab/WellMate --skill session-start-sarkarshivaditya-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Starting a work session without knowing the current state of the repository, project board, or prior context leads to duplicated effort, stale branches, and missed in-progress work. This Skill orients you at the start of every session by systematically verifying the environment, repository, GitHub Project board, and memory before any work begins. ## Core Features & Use Cases - Environment and Repository Verification: Checks GitHub CLI authentication, git state, environment variables, and docker-compose development services before proceeding. - GitHub Project Board Sync: Caches project fields and items via the GitHub CLI to minimize API calls, then verifies that issue statuses match actual branches and open pull requests. - Orchestration Resume and Memory Recall: Detects interrupted autonomous orchestration via MCP memory and recalls prior session context to resume in-progress work. - Use Case: You return to a project after the weekend. Run this Skill to discover which issue was In Progress, confirm its branch still exists, verify the project board matches reality, and get a summary of exactly where to resume. ## Quick Start Use the session-start skill to orient me on the current repository state, GitHub project board, and any in-progress work before we begin.

Frequently Asked Questions about session-start

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

FAQPage Schema
How do I check GitHub Project board status from the command line?▼

Use the GitHub CLI with gh project field-list and gh project item-list to retrieve project fields and items as JSON. Cache the results in environment variables and query them with jq to avoid repeated API calls.

How to reduce GitHub API calls when querying project boards?▼

Cache all project fields and items in a single batch of API calls at session start, then extract field IDs, statuses, and issue numbers locally with jq. This replaces dozens of individual API calls with about three.

How do I verify project board status matches actual branches?▼

Compare issues marked In Progress against remote feature branches matching the issue number, and check that open pull requests correspond to issues marked In Review. Report any mismatches before proceeding with work.

What should I check before resuming in-progress development work?▼

Read the associated issue and its comments, check the last commit message, verify the working directory state, run tests to confirm the codebase works, and search memory for prior session context before continuing.

Why does gh auth status fail in a new session?▼

The GitHub CLI requires authentication via gh auth login before any project or repository queries work. If authentication fails, report it immediately and re-authenticate before running project board checks.