Alternatives
Products that do what SkillCI does
Regression testing for Claude Skills
- 1SC
I got tired of Claude Code forgetting all my context every time I open a new session: set-up decisions, how I like my margins, decision history. etc. We built a shared memory layer you can drop in as a Claude Code Skill. It’s basically a tiny memory DB with recall that remembers your sessions. Not magic. Not AGI. Just state. Install in Claude Code: /plugin marketplace add https://github.com/mutable-state-inc/ensue-skill /plugin install ensue-memory # restart Claude Code What it does: (1) persists context between sessions (2) semantic & temportal search (not just…
Dec 2025 · github.com
- 2
- 3IM
At my work they provided a single Claude subscription for everyone on the team. To be honest I like kiro better as it provides a way better SDD management. But the company can't provide it and I can't afford it yet. Turns out I had the skill creator skill in my claude instance so I made use of it to create this Skill. I made it fully by using Claude but I wanted to make it open source, so I asked it to help me make tests and preparations for it, even a CI to run python tests. Well, we got this results with it: - Phase 2A: 67 static assertions (Python script, runs in CI) - Phase 2B: 15…
May 2026 · github.com
- 4PS
I got tired of playwright-mcp eating through Claude's 200K token limit, so I built this using the new Claude Skills system. Built it with Claude Code itself. Instead of sending accessibility tree snapshots on every action, Claude just writes Playwright code and runs it. You get back screenshots and console output. That's it. 314 lines of instructions vs a persistent MCP server. Full API docs only load if Claude needs them. Same browser automation, way less overhead. Works as a Claude Code plugin or manual install. Token limit issue:…
Oct 2025 · github.com
- 5
- 6CC
Continuous Claude is a CLI wrapper I made that runs Claude Code in an iterative loop with persistent context, automatically driving a PR-based workflow. Each iteration creates a branch, applies a focused code change, generates a commit, opens a PR via GitHub's CLI, waits for required checks and reviews, merges if green, and records state into a shared notes file. This avoids the typical stateless one-shot pattern of current coding agents and enables multi-step changes without losing intermediate reasoning, test failures, or partial progress. The tool is useful for tasks that require many…
Nov 2025 · github.com
- 7RG
Hey HN! I'm José, and I built Recall to solve a problem that was driving me crazy. The Problem: I use Claude for coding daily, but every conversation starts from scratch. I'd explain my architecture, coding standards, past decisions... then hit the context limit and lose everything. Next session? Start over. The Solution: Recall is an MCP (Model Context Protocol) server that gives Claude persistent memory using Redis + semantic search. Think of it as long-term memory that survives context limits and session restarts. How it works: - Claude stores important context as "memories" during…
Oct 2025 · npmjs.com
- 8
- 9CR
I got tired of sharing AI demos with terminal screenshots or screen recordings. Claude Code already stores full session transcripts locally as JSONL files. Those logs contain everything: prompts, tool calls, thinking blocks, and timestamps. I built a small CLI tool that converts those logs into an interactive HTML replay. You can step through the session, jump through the timeline, expand tool calls, and inspect the full conversation. The output is a single self-contained HTML file — no dependencies. You can email it, host it anywhere, embed it in a blog post, and it works on mobile. Repo:…
Mar 2026 · github.com
- 10AC
Dec 2025 · github.com
- 11
- 12SP
Hey HN, My cofounder and I have gotten tired of CC ignoring our markdown files so we spent 4 days and built a plugin that automatically steers CC based on our previous sessions. The problem is usually post plan-mode. What we've tried: Heavily use plan mode (works great) CLAUDE.md, AGENTS.md, MEMORY.md Local context folder (upkeep is a pain) Cursor rules (for Cursor) claude-mem (OSS) -> does session continuity, not steering We use fusion search to find your CC steering corrections. - user prompt embeddings + bm25 - correction embeddings + bm25 - time decay - target query embeddings -…
Mar 2026 · gopeek.ai
- 13KS
Hi All, Recently I've been using Claude Code a lot for debugging cluster issues and I realized I was performing similar tasks repeatedly so I decided to package them up into skills so I could call them up more easily (e.g. `/investigate`, `/audit-security`, `/audit-outdated`). I'm calling the skill pack "kstack" and the goal is to be able to monitor and troubleshoot K8s from within Claude Code. If you have time, I'd love to get some feedback on the project! Andres Source: https://github.com/kubetail-org/kstack Docs: https://kstack.sh/
May 2026 · github.com
- 14CC
I built a Claude Code skill called crabby that makes Claude output diagnostics in rustc error format - severity codes, location arrows, causation spans, and a paste-able fix every time. The twist: Claude becomes Ferris the crab, grumpy and unimpressed, but technically precise. The format works for code review, writing review, architecture, strategy - anything you submit. The "writing review" example tends to surprise people: it flags passive voice in a postmortem with the exact same error[W002] format as a SQL injection. https://github.com/ekadetov/crabby
Apr 2026
- 15
- 16
Contribute to alpbahadur/interns-review-plugin development by creating an account on GitHub.
17h ago · github.com
- 17
- 18
- 19AC
2024 · github.com
- 20CC
We’ve been building visual rule engines (clear spreadsheet interfaces -> API endpoints that map incoming data to a large number of potential outcomes), and had the fun idea lately to see what happens when we use our decision table UI with Claude’s PreToolUse hook. The result is a surprisingly useful policy/gating layer– these tables let your team: - Write conditional, exception-friendly policies beyond globs/prefixes (e.g. allow rm -rf only in */node_modules/*, deny / or $HOME, ask if --force or network call; gate kubectl delete / SQL DROP with a clear reason) -…
Jan 2026 · github.com
- 21TS
Hello HN! I’ve been playing with Claude Skills and stumbled on a simple pattern for tiny, durable personal data systems: * CLI: a small, self-contained executable * SKILL.md: the operator guide (what to run, how to parse output, how to think about the system) * SQLite: a local DB for persistent state It’s nothing mind-blowing, but the ergonomics of this combo feel great. If you define a process/flow, Claude can "turn the crank" by running the CLI, accumulating context, and animating the system to life over time. They’re also easy to share: you can distribute System Skills via Claude…
Oct 2025 · shruggingface.com
- 22WO
Apr 2026 · npmjs.com
- 23CM
We built CodeYam Memory because Claude Code kept making the same mistakes on our codebase. Our claude.md files quickly got stale and maintaining by hand or with Claude wasn’t sufficient. While digging into this we found that Claude has a native rules system that allowed us to target specific parts of our repo with path matching. This was ideal for our use case but trying to manage these rules by hand was already not working and would be even harder with more granular, targeted rules. CodeYam Memory uses a background agent to review your coding session transcripts, identifies confusion…
Mar 2026
- 24
Ranked by how close each launch is in meaning, then by votes. Refine with a description →