pulse

Verify documented self-descriptions against actual project state.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/orenmagid/claude-cabinet --skill pulse-orenmagid
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pulse
Source: https://github.com/orenmagid/claude-cabinet/tree/main/templates/skills/pulse
Command: npx skills add https://github.com/orenmagid/claude-cabinet --skill pulse-orenmagid

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Self-description drift from reality. A CLAUDE cabinet's documented state can diverge from actual project state, causing confusion and misinformed decisions. Pulse detects these mismatches and surfaces them for correction.

Core Features & Use Cases

  • Mechanical verification of self-descriptions to ensure counts, references, and state align with reality.
  • Embedded health checks within orient/debrief (15-second budget) and standalone audits to surface and fix drift in project documentation.
  • Auto-fix capabilities for numeric counts via the defined auto-fix-scope, with structured reporting for non-automatic discrepancies.

Quick Start

Run /pulse inside an active session (orient or debrief) to perform an embedded health check and verify description accuracy.

Frequently Asked Questions about pulse

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

FAQPage Schema
How do I check if project documentation matches the actual codebase state?

Run a documentation consistency-check to mechanically verify counts, references, and staleness against the actual project state. It surfaces discrepancies safely and optionally auto-fixes numeric counts when configured.

What is documentation drift and how do I detect it during development?

Documentation drift happens when self-descriptions diverge from actual project state. Detect it by running embedded health checks during orient or debrief phases to identify mismatches in mechanical counts and references.

Can I automatically fix outdated numeric counts in my system descriptions?

Yes, you can automatically fix outdated numeric counts by configuring the auto-fix-scope. The tool safely corrects numeric discrepancies during audits while structurally reporting non-automatic mismatches for manual review.

How long does an embedded health check take during a session?

An embedded health check takes up to 15 seconds during orient or debrief sessions. It mechanically verifies self-descriptions to ensure state alignment without disrupting your active workflow.

What limitations exist when auditing project documentation for consistency?

Auditing enforces safe, non-destructive reporting, limiting auto-fixes to numeric counts within the defined auto-fix-scope. All other reference and staleness discrepancies are surfaced structurally for manual correction.