compresr-vscode

2025-11-29 ~ 2026-02-02 · 65 days

README Dreamer

Succumbed to a single day's burst of ambition, never compressing a single token in production

“Compressed its own lifespan to a single day”

Death Type

README Dreamer

This project embodied the 'README Dreamer' archetype by articulating a clear, ambitious purpose in its summary ('reduce token usage and save money') but manifesting it only in a single day's burst of 3 commits. It had 7 dependencies installed and 28KB of TypeScript code but no observable further development beyond 2026-02-02.

Cause of Death

1. Ephemeral Existence

The project's entire lifecycle, from its inception to its final commit, spanned a single day: 2026-02-02. Its ambition outlived its development window by 64 days.

2. Weekend Warrior, One-Day Wonder

All 3 recorded commits (100%) were made by Kamel Charaf on a single Sunday, 2026-02-02, at 22:00. This singular burst of activity proved unsustainable for long-term development.

3. Dependency Weight, Feature Light

Despite its short life, the project introduced 7 direct dependencies and a 4091-line package-lock.json, a substantial setup for a project that produced no observable further development. No dedicated test directory was found, indicating a focus on infrastructure over validation.

Vibe Score

28/ 100

AI-assisted but human-driven

What They Did

Conceived as a VS Code extension, Compresr aimed to reduce token usage and save money for AI coding assistants by compressing files like CLAUDE.md and COPILOT.md. Its README promised side-by-side diffs and workspace processing. All 3 commits, by solo developer Kamel Charaf, landed on 2026-02-02, encapsulating its entire functional ambition within 24 hours.

@types/node@types/vscode@typescript-eslint/eslint-plugin@typescript-eslint/parsereslinttypescript@vscode/vsce

Burnout Analysis

With a burnout score of 15/100, this project didn't suffer from a slow burn; it was a sudden, intense flash. Solo developer Kamel Charaf authored 100% of the 3 commits, all landing on 2026-02-02 at 22:00. This concentrated effort, followed by immediate silence, signifies a 'burst-and-abandon' pattern rather than prolonged developer exhaustion.

Dependency Archaeology

Compresr-ai/compresr-vscode installed 7 direct dependencies, including `@types/vscode` and `@vscode/vsce`, indicating a full VS Code extension development setup. The `package-lock.json` file ballooned to 4091 lines, a veritable dependency forest for a project that lived only one day. Despite this extensive setup, the project had no dedicated test directory (Key Finding 7), perhaps betting on compression over correctness.

Autopsy: File Structure

├──src/extension.ts578 lines of core logic, born and abandoned on the same day, 2026-02-02.

├──src/settingsPanel.ts199 lines for user settings, likely never configured by an actual user.

├──src/client.ts148 lines for communication, with whom or what remains a mystery to this day.

├──package.json7 direct dependencies, a small army assembled for a one-day war.

├──package-lock.json4091 lines of transitive dependencies, the heaviest part of the project's legacy.

└──README.mdThe primary artifact, detailing a future that never arrived, updated in the final commit.

Eulogy Stats

Total Commits: 3
Ambitious Adjectives: 0
Deploy Config: No
Estimated Users: 0 (its active lifespan was less than a single work day, 2026-02-02)

Last Words

“'updated readme' — a final testament to documentation over deployment, a 66% shift from initial code to project description.”