Six-skill safety net: generate, drift-check, lint, test-stub, coverage-audit, and scope-walk E2E specs against the current implementation
Plugin spec-mirror from marketplace donghyuns-agent-tools in edonghyun/donghyuns-agent-tools. Commands read from the repo's manifest — 20 days ago.
compareDrift-check the current implementation against the existing specs/ directory. Use when the user wants to verify the spec is still accurate, catch undocumented changes, or run the safety-net check after recent code edits. Triggers include "spec compare", "drift check", "verify spec", "is the spec sta
coverageCross-reference existing tests against the specs/ directory to find untested flows, endpoints, and invariants. Use when the user wants to see how much of the spec is actually covered by tests, before relying on the test suite as a safety net. Triggers include "spec coverage", "test coverage vs spec"
gen-testsGenerate test stubs from the existing specs/ directory and record whether they are active todos or inactive planning stubs. Use when the user wants to turn the spec into planned executable coverage for domain invariants, backend endpoints, and e2e flows. Triggers include "gen tests", "generate tests
generateGenerate end-to-end specification markdown files that mirror the current implementation as a safety net. Use when the user wants to extract, document, or snapshot the app's behavior — across frontend action flows, backend use cases, queries, and domain features. Triggers include "generate spec", "sp
lintAudit the specs/ directory for internal hygiene issues — dead cross-references, missing source lines, stale [INFERENCE] markers, orphaned KEEP blocks, broken refs/ links. Use when the user wants to verify the spec itself is healthy, after manual edits to spec files, or before relying on the spec as
scopeGenerate a focused mini-spec for an upcoming change — "everything that touches X" — by walking the spec graph forward and backward from a target element. Use when the user is about to modify code and wants to know the blast radius before changing anything. Triggers include "spec scope", "blast radiu
Screenshot-backed product intake for external PoCs, demos, prototypes, and VoC experiments before product integration, with page-walk, control-reaction, PoC fidelity, implementation specs, and static web reports
9 skills
Delegated browser QA operator: plan, run, monitor, triage, and optionally repair acceptance checks from requirements with evidence dashboards
6 skills
Evidence-backed UI iteration operator for baseline/current web, mobile web, native mobile, local session, and requirement parity comparisons during product UI changes
6 skills
Branch a conversation point into a capsule another session continues from, merge results back, and always show where you are
4 skills
Evidence-driven development discipline for strict RED-GREEN-REFACTOR TDD with co-located executable specifications and contract tests for fakes
2 skills
Talk like caveman. Cut filler. Keep technical details explicit.
22 skills · 1 command · 3 agents · hooks
Persistent memory for Claude Code: the next session starts where the last one left off.
29 skills · 1 MCP server · hooks
tasteskill 2.5.1: professional company websites at the figma.com and x.ai level, with one section per screen, real photographs, real product UI, effects kept for tech and gaming pages, and a real-browser checker and finish gate.
1 skill
Open-source AI job search that runs locally in your AI coding CLI: scan job portals, evaluate listings into a structured A-H report with a 1-5 score, tailor your CV, track applications
5 skills · hooks
Cross-session memory and token savings for coding agents.
6 skills · 1 agent · 1 MCP server · hooks
Package any website or local web build into a lightweight desktop app with Pake CLI.
1 skill
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.