All authors
Claude Skills by Lingelo
github.com/Lingelo25 skills0 installs0 views
- Address FeedbackHandles feedback already left on a GitHub PR — judges each thread and comment on its merits (nits included), fixes what is valid, verifies, commits and pushes, then replies in each thread with the context quoted and resolves it; escalates without blocking what needs a human decision. Use when the user says "handle the PR comments", "answer the review", "fix Bob's remarks", /kaizen:address-feedback; called by /kaizen:watch-pr.Votes: 0GitHub stars: 2
- AutopilotKaizen autonomous mode — takes a request all the way without stopping, through the right skills (plan or debug, work, simplification, review with fixes, capture, commit, push, PR, CI watching). A code change ends as an open PR. Use only when the user explicitly asks for end-to-end autonomous work or invokes /kaizen:autopilot — ideally after /kaizen:brainstorm. For step-by-step follow-up, use plan, work, debug.Votes: 0GitHub stars: 2
- BrainstormTurns a fuzzy or ambitious idea into clear requirements (WHAT to build) through a one-question-at-a-time dialogue grounded in the code and past learnings, then writes the first version of the unified plan (product contract with R ids and acceptance examples). Use when the user wants to explore, frame or refine a feature or a problem before planning — "let's think about…", "I'd like…", /kaizen:brainstorm. Not for executing already specified work (/kaizen:plan or /kaizen:work).Votes: 0GitHub stars: 2
- ConstitutionCreates, amends or audits the project's engineering constitution (CONSTITUTION.md) — 5 to 9 non-negotiable principles, each with a verifiable check, an AI policy (what agents do on their own), versioning and governance — through an interview that pushes back on vague principles and a stress test. Plan, doc-review and review then enforce it as checks. Use when the user says "create our constitution", "our engineering principles", "add a principle", "amend the constitution", /kaizen:constitution.Votes: 0GitHub stars: 2
- DebugKaizen diagnosis loop for bugs, red tests, wrong or slow behavior — reproduction, backward tracing, past learnings and git history, one hypothesis at a time, full causal chain with file:line before any fix, then test-first fix and capture. Use when the user says "it crashes", "this test fails", "why does X…", a bug ticket, /kaizen:debug.Votes: 0GitHub stars: 2
- DecideMakes a hard or irreversible technical decision on evidence — frames the question, explores the code, the learnings, the constitution and external docs, compares 2 to 4 real options (including "do nothing"), gives an argued verdict with its confidence level and the signal that would change its mind, then records it as an ADR (docs/adr/) when it is costly to undo — a decision undone by a revert gets a simple answer, without an ADR. Use when the user asks "should we adopt X?", "A or B?", "do we...Votes: 0GitHub stars: 2
- DeployDeploys a commit to an environment through the commands the team declared (.kaizen/config.json → deploy), with verified preconditions (green CI, production checklist of the shipped plans, rollback ready), approval typed by the user for a protected environment (production), a shared deploy/<env>/… tag, then a watch of the plan's production signals and a rollback if a threshold is breached. Use when the user says "deploy", "ship to production", "push to staging", "rollback", /kaizen:deploy <env...Votes: 0GitHub stars: 2
- Doc ReviewReviews a Kaizen plan or requirements before they get built — deterministic check (plan check), then specialized reviewers in parallel (coherence and feasibility always; scope, security, adversarial, design depending on the document), verification of the findings, mechanical fixes applied, decisions put to the author. Called automatically by /kaizen:plan; usable on its own. Use when the user says "review this plan", "challenge this spec", /kaizen:doc-review [path].Votes: 0GitHub stars: 2
- HelpKaizen orientation guide — explains what Kaizen is (the loop, the gates, the deliverables, the profiles) and recommends the command to use for the situation described and the repo's actual state (setup done?, constitution?, plan in progress?, gate active?, review recorded?), with the exact invocation and what it will produce. Read-only. Use when the user asks "which command should I use?", "where do I start?", "what is kaizen?", "I want to fix a bug / ship / measure, what do I run?", "where a...Votes: 0GitHub stars: 2
- IdeateGenerates then critiques ideas grounded in the repo (or a topic) — six angles in parallel (frictions, inversion/automation, broken assumptions, leverage, analogies from other domains, flipped constraints), each idea with a verifiable basis, explicit and motivated rejection, 5 to 7 ranked survivors in docs/ideation/. Use when the user wants ideas, improvement leads or surprising directions before choosing one ("what could we improve", "surprise me", /kaizen:ideate). Not for refining an already...Votes: 0GitHub stars: 2
- LearnCaptures a solved problem as a durable learning in docs/learnings/ (validated frontmatter, corpus vocabulary, update rather than duplicate) so the next /kaizen:plan and the next /kaizen:review read it back — the step that makes each cycle make the next one easier. Use after verified work that produced non-obvious reasoning (a trap, a surprising cause, a decision costly to rediscover): "document this", "remember the lesson", /kaizen:learn. Not for a routine fix the code already explains.Votes: 0GitHub stars: 2
- MetricsMeasures the health of delivery and of the Kaizen loop — DORA metrics approximated from git and GitHub (delivery frequency, change lead time, rework rate, change failure rate, time to restore), batch size, and the compounding effect (learnings created and reused by plans, constitution exceptions) — then interprets them with 1 to 3 actions. Use when the user asks "where do we stand", "our DORA metrics", "is kaizen any use", a retrospective, /kaizen:metrics [window].Votes: 0GitHub stars: 2
- MonitorChecks or watches the production signals declared by the team (.kaizen/config.json → monitor.signals: native HTTP health-check, or any command printing a number — Prometheus, Datadog, CloudWatch, logs) against the thresholds of the config and the shipped plans, and says what to do if a threshold is breached (rollback, postmortem). Read-only, except a requested or automatic rollback. Records incidents (dated detection, resolution) detected outside the post-deployment window: schedulable check ...Votes: 0GitHub stars: 2
- PlanTurns an idea, requirements or a plan from /kaizen:brainstorm into an implementation plan ready to execute (HOW to build) — parallel research (repo patterns, past learnings, git history, external docs), justified technical decisions, work units with files, evidence strategy and tests, verification contract. Use when the user says "plan it", "break this work down", "how do we implement…", /kaizen:plan, or to deepen an existing plan (deepen). Never writes production code.Votes: 0GitHub stars: 2
- PolishPolishes the experience of a feature that already works, guided by the user on the live page — detects and starts the dev server (Next, Vite, Nuxt, SvelteKit, Astro, Angular, Rails, Django, Phoenix, Laravel, .claude/launch.json), opens the page in the browser (Playwright), applies each piece of feedback live (spacing, copy, states, responsiveness, accessibility), checks by screenshot, and commits locally. Use when the user says "let's polish the UI", "polish", "let's tune the rendering before...Votes: 0GitHub stars: 2
- PostmortemRuns a blameless incident postmortem — rebuilds the timeline from git, CI, deployments and the logs provided, measures the impact, analyzes the contributing factors (not a single cause or a person), lists actions with owners, then closes the Kaizen loop (learning, pack rule, constitution amendment, regression test). Use after an incident, a production regression or a near miss: "postmortem", "look back at the outage", "incident analysis", /kaizen:postmortem.Votes: 0GitHub stars: 2
- Prune LearningsMaintains the learnings in docs/learnings/ against the current code — detects stale learnings (vanished paths, symbols, behaviors), duplicates, overlaps and contradictions, then applies Keep / Update / Merge / Replace / Delete with evidence, and returns a full report. Use when the user says "clean up the learnings", "audit docs/learnings", after a big refactor, or when a learning turned out wrong: /kaizen:prune-learnings [area]. Never changes product code.Votes: 0GitHub stars: 2
- ReleasePrepares a release — conventional commits since the last tag grouped into readable release notes (features, fixes, breaking changes with migration), proposed SemVer version, CHANGELOG entry, and production checklist (checks, migrations, flags, rollback, communication). Never tags or publishes without explicit approval. Use when the user says "prepare the release", "release notes", "changelog", "which version?", /kaizen:release.Votes: 0GitHub stars: 2
- ReviewKaizen multi-agent code review — selects the specialized reviewers by what the diff touches (correctness always; security, tests, performance, reliability, API contracts, migrations, maintainability, adversarial, standards/packs/learnings depending on the case), launches them in parallel, merges, filters by confidence, verifies each blocking finding and returns a verdict against the plan. Report only by default; applies fixes with "apply". Use when the user says "review my code", "review the ...Votes: 0GitHub stars: 2
- SetupInstalls the Kaizen SDLC in a repo and audits it — project maturity diagnosis (audit: CI, tests, secrets, branch protection, CODEOWNERS, dependencies, deployment, rollback, monitoring, constitution) with a prioritized roadmap and guided fixes; creates .kaizen/config.json and the deliverable folders, detects the stack, the verification commands and the deployment platform, sets profile, models, language and tracker, creates a Kaizen Pack (pack:<name>), health check (check). Use when the user s...Votes: 0GitHub stars: 2
- ShipShips Kaizen work as a reviewable PR — green checks, size under the limit (otherwise split into stacked PRs), conventional commits with Jira, branch push (never the default branch), PR with a description from the plan (goal, covered requirements, evidence, constitution check, rollout and rollback) and a reviewer guide; then offers /kaizen:watch-pr. Can also only draft or refresh a PR description. Use when the user says "open the PR", "ship it", "push and create the PR", "update the PR descrip...Votes: 0GitHub stars: 2
- Watch PrAccompanies an open GitHub PR until it "looks ready to merge" — every cycle, first handles review feedback (through /kaizen:address-feedback), then the head commit's red CI (rerun if infrastructure, diagnosis and fix otherwise), updates the branch only when GitHub asks for it, refreshes the description, and stops on a true, reported state. Never merges. Use when the user says "watch my PR", "drive the PR to merge", "babysit the PR", /kaizen:watch-pr. Not for a single comment or a single CI fa...Votes: 0GitHub stars: 2
- WorkExecutes a Kaizen plan (or a concrete request) end to end — dedicated branch, unit by unit with test-first evidence, one conventional commit per unit, quality gate active (Stop hook) while checks are red, then simplification, mandatory review and delivery. Use when the user says "implement the plan", "execute", /kaizen:work [path]. For a bug without a known cause, prefer /kaizen:debug.Votes: 0GitHub stars: 2
- Motion VideoCreates motion design videos with sound (intro, product teaser, explainer, logo animation, animated data viz, social media) by writing an HTML/CSS/SVG/Canvas composition and rendering it frame by frame to MP4/WebM/GIF/MOV through Playwright + ffmpeg, deterministically, with synthesized sound effects, music, voice-over (local text-to-speech or a recording) and burned-in/exported subtitles (SRT/VTT) synced to the picture. Use when the user says /motion-video, wants to "generate a video", "make ...Votes: 0GitHub stars: 2
- SlidesBuilds presentation decks (talk, pitch deck, team review, training, keynote) as a single HTML file from a themed template with 19 layouts (title, agenda, section, statement, bullets, split, cards, columns, big number, KPIs, chart, timeline, comparison, code, quote, full-bleed image, closing…), presentable in any browser (keyboard, speaker notes, overview, step reveals) and exported to PDF, PNG per slide or a contact sheet, with an automatic layout check (overflow, collisions, safe area, contr...Votes: 0GitHub stars: 2