Skip to content
Skill

claude-skills-supercharged

by jefflester

AI Summary

A skill that guides AI assistants through a structured wrap-up workflow for code changes, ensuring linting, tests, docs, and skill updates are completed before context runs out. Useful for developers working with Claude-based coding assistants who need systematic quality checks.

Install

Copy this and paste it into Claude Code, Cursor, or any AI assistant:

I want to install the "claude-skills-supercharged" skill in my project.

Please run this command in my terminal:
# Install skill into the correct directory
mkdir -p .claude/skills/commands && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/commands/SKILL.md "https://raw.githubusercontent.com/jefflester/claude-skills-supercharged/main/.claude/commands/wrap.md"

Then restart Claude Code (or reload the window in Cursor) so the skill is picked up.

Description

A "supercharged" implementation of Claude Code Skills – using Haiku prompt analysis/critical skill scoring and skill auto-injection for friction-free, context-driven workflows.

description: Wrap up current work

Wrap up the current work by following the checklist below. **NOTE: If you are low on context and/or if any of the wrap tasks are easily delegated, feel free to leverage subagents to complete the task(s) to stretch your remaining context. Checklist: For all changes/additions made, please: • Lint the code. It should pass pre-commit checks. • Check to see if there are any related tests. If there are, update them to ensure they reflect the changes/additions made. • Check to see if there are any related docs. If there are, modify them as necessary to account for the changed/added code. • Check if any skills need updates (NOTE: all skill/resource docs should be \<= 500 LOC): • Activate the "skill-developer" skill to assist with skill maintenance. • Check that proper code reuse was employed, no DRY violations were introduced, and existing codebase patterns were followed. Be wary of magic strings/numbers and use constants/enums where appropriate. • If there are ANY actionable next steps or current problems/failures, detail them in the form of an actionable summary for the next session. When finished, provide a commit message (without any single quotes) summarizing the changes made.

Discussion

0/2000
Loading comments...

Health Signals

MaintenanceCommitted 1mo ago
Active
AdoptionUnder 100 stars
37 ★ · Niche
DocsREADME + description
Well-documented

GitHub Signals

Stars37
Forks3
Issues0
Updated1mo ago
View on GitHub
MIT License

My Fox Den

Community Rating

Sign in to rate this booster

Works With

Claude Code