babarmuhammad
UserThe workspace layer for Claude Code — browse every session, persistent project memory, MCP awareness, and per-project launch control. Terminal UI and desktop GUI. Zero runtime dependencies.
Categories
Indexed Skills (16)
changelog
Use when updating a CHANGELOG or preparing release notes. Turns merged changes into Keep a Changelog entries written for users.
code-explainer
Use when asked to explain how code works, trace a flow, or onboard to an unfamiliar area of the codebase.
commit-message
Use when writing a git commit message. Turns staged changes into a clear Conventional Commits message with an accurate summary and body.
pr-description
Use when opening or updating a pull request. Produces a reviewer-friendly PR title and description from the branch's changes.
refactor-planner
Use before a non-trivial refactor. Produces a safe, staged plan that preserves behavior — plan first, edit second.
security-review
Use when reviewing code or a diff for security issues before merging. Flags concrete, high-confidence vulnerabilities with fixes.
test-writer
Use when adding tests for new or changed code. Writes focused, behavior-driven tests that match the project's existing framework and conventions.
token-economy
Use when you want terse, low-token responses for routine or mechanical work — status updates, confirmations, simple edits — without losing correctness.
changelog
Use when updating a CHANGELOG or preparing release notes. Turns merged changes into Keep a Changelog entries written for users.
code-explainer
Use when asked to explain how code works, trace a flow, or onboard to an unfamiliar area of the codebase.
commit-message
Use when writing a git commit message. Turns staged changes into a clear Conventional Commits message with an accurate summary and body.
pr-description
Use when opening or updating a pull request. Produces a reviewer-friendly PR title and description from the branch's changes.
refactor-planner
Use before a non-trivial refactor. Produces a safe, staged plan that preserves behavior — plan first, edit second.
security-review
Use when reviewing code or a diff for security issues before merging. Flags concrete, high-confidence vulnerabilities with fixes.
test-writer
Use when adding tests for new or changed code. Writes focused, behavior-driven tests that match the project's existing framework and conventions.
token-economy
Use when you want terse, low-token responses for routine or mechanical work — status updates, confirmations, simple edits — without losing correctness.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.