bearings

Generate a four-section repository status snapshot from git state and validation results.

1|Updated Jul 20, 2026
One-click install
npx skills add https://github.com/pessinamistic/pitwall --skill bearings-pessinamistic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bearings
Source: https://github.com/pessinamistic/pitwall/tree/main/.claude/skills/bearings
Command: npx skills add https://github.com/pessinamistic/pitwall --skill bearings-pessinamistic

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill solves the problem of context loss by providing a standardized, read-only status report that allows developers or agents to quickly understand the current state of a repository after a break or session reset.

Core Features & Use Cases

  • Automated Status Reporting: Aggregates git state, recent commit history, and validation results into a structured four-section report.
  • Handoff Documentation: Automatically discovers and incorporates relevant notes from scratch handoff files to ensure continuity.
  • Use Case: Use this when you return to a project after several days and need to immediately identify what was last completed, what is currently in progress, and what decisions are pending.

Quick Start

Ask the agent to generate a status report or debrief for the current repository state.

Frequently Asked Questions about bearings

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

FAQPage Schema
How do I generate a project status report from git history and handoff notes?

To generate a project status report, use an automated tool to aggregate git state, recent commit history, and validation results into a structured summary. This provides a read-only snapshot outlining progress and pending decisions.

What is the best way to restore context on a repository after a session reset?

Restoring context after a session reset involves generating a comprehensive status snapshot aggregating git state and handoff documentation. This report identifies completed work, in-progress tasks, and pending decisions.

Does generating a repository status snapshot require specific dependencies?

Generating a repository status snapshot requires access to git, node, and bash. These dependencies execute diagnostic scripts and parse repository metadata to produce the final report.

Can I use automated status reporting to discover scratch handoff files?

Yes, automated status reporting can automatically discover and incorporate relevant notes from scratch handoff files. This ensures continuity by integrating existing documentation into the project summary.

When do I need a read-only status snapshot for my development environment?

You need a read-only status snapshot when returning to a project after several days to immediately identify the repository state. It prevents context loss by providing a consistent four-section summary of progress.