Claude Skills by Greg-Klein

github.com/Greg-Klein

12 skillsA× 120 installs0 views

Clarify SpecATurn a software request and its source documents into established requirements, explicit assumptions, contradictions and decision questions before planning or when a specification gap appears. Does not choose missing product decisions, change tickets or implement code.developmentVotes: 0GitHub stars: 2
Collect EvidenceACollect reproducible results for checks already selected by a caller, using documented commands or a running application. Use to execute checks reliably and distinguish observations, failures, unavailable checks and stale results. Does not choose a test strategy, independently review a change, fix code or declare acceptance.developmentVotes: 0GitHub stars: 2
Document ChangeAUpdate repository documentation made stale by an authorized code change, covering decisions, contracts, configuration and the behavior actually shipped. Use when a change affects existing documentation or introduces a mechanism that needs a documented home.developmentdocumentationVotes: 0GitHub stars: 2
Figma ReviewAIndependently review a running interface against a design reference (Figma frames, mockups attached to the ticket, or already shipped neighbouring screens), using measured properties, geometry, states, accessibility and layout invariants. Despite its name it runs with or without Figma. Use for design review of a change visible in the UI, without reading product source code or implementing corrections.developmentVotes: 0GitHub stars: 2
Gh Github ApiARecipes and traps for the `gh` CLI and the GitHub API when the ticket is a GitHub issue - reading an issue with its comments, attachments, sub-issues and dependencies, opening a pull request from a description file, requesting a reviewer and reading it back, publishing the consolidated review. Use whenever the ticket URL is a GitHub one (`/<owner>/<repo>/issues/<n>`), and whenever a gh command returns without error but changed nothing (reviewer not set, stacked pull request closed).developmentgobashVotes: 0GitHub stars: 2
Gitlab TicketsAHouse conventions for creating or hand-writing a GitLab epic or ticket (titles, estimation, labels, structure, assignment, the French exception, no cross-referencing). Use whenever a GitLab ticket or epic is written or reviewed, and whenever a merge request is about to reference a ticket.developmentgobashVotes: 0GitHub stars: 2
Skills DirectorySkills Directory Look up any of 103,619 scanned skills — grade, score, and every finding. Free.Check a skill
Glab Gitlab ApiARecipes and traps for the `glab` CLI and the GitLab API - linking a ticket to an epic, passing a long description from a file, assigning an issue reliably, reading and writing a work item's native status. Use whenever a glab command fails silently or returns an unexpected error (404 on --epic, assignee_ids ignored, description filled with the literal text "@file.md", status absent from the REST API).developmentgobashVotes: 0GitHub stars: 2
HowAReconstruct how an existing software subsystem works from code, call sites, configuration, and tests. Use for explicit how requests, tracing execution or data flow, identifying state ownership, boundaries, and invariants, or establishing an unfamiliar subsystem before planning a change. Produce a read-only, evidence-backed mental model for a human or another agent. Exclude implementation, architecture critique, and historical motivation investigations.developmentrefactoringgitVotes: 0GitHub stars: 2
Review ChangeAIndependently challenge an implementation from its specification and diff, looking for counterexamples, regressions, untested consumers and tests that pass for the wrong reason. Use for code review or independent QA, not author self-checks. Returns findings without fixing code.developmentrustcode-reviewVotes: 0GitHub stars: 2
Self CheckAVerify your own implementation before handing it to a reviewer. Derive checks from the assigned requirements, changed behavior and concrete edge cases, then report coverage and limits. For authors of changes, not independent reviewers.developmentVotes: 0GitHub stars: 2
UnslopACut AI tells from prose, in French or English. Use for docs, READMEs, MR descriptions, tickets, Slack messages, blog posts, any non-code text that should read like a person wrote it. Triggers: "unslop", "humanize", "dé-IA ce texte", "ça sonne IA", "rends ça naturel", "make this sound human", "clean up this writing". Applies while drafting as well as to existing text.developmentgogitVotes: 0GitHub stars: 2
WhyAInvestigate why existing software behavior or structure took its current form using a current-code anchor, Git history, commits, linked PRs or MRs, tickets, and documentation or ADRs. Use for explicit why requests, design rationale, unusual compatibility logic, historical constraints, and questions about whether an old constraint still applies. Produce a read-only rationale investigation that separates documented intent from inference. Requires the how skill; report that dependency and stop i...developmentshellgitVotes: 0GitHub stars: 2