All authors
Claude Skills by HugoLopes45
github.com/HugoLopes4527 skills0 installs69 views
- CommitWrite a conventional commit message for the staged changes and commit them. Use only when the user explicitly asks to commit.Votes: 0GitHub stars: 2
- Hl AdrDraft an architecture decision record (ADR): context, options actually considered, decision, consequences, and reversal cost. Use when a consequential technical decision needs to be recorded.Votes: 0GitHub stars: 2
- Hl ChallengeTest a plan, technical decision, design, or just-finished work against its goal and agreed reference, using the code, evidence, and safe commands, then recommend proceed, fix first, or stop, and name the smaller version if one exists. Returns a verdict, not design questions. --premortem assumes the goal failed and traces present weaknesses to that failure. --lens reviews through one fixed method (minimalist, failure-hunter, data-model, distributed, operability, boring-stack, agent-tooling, te...Votes: 0GitHub stars: 2
- Hl CheckpointBefore clearing or compacting the conversation context, check that decisions, evidence, pending work, and the next action are saved, and that the worktree state is deliberate. --stuck diagnoses why work is going in circles (repeated fixes, the same failure coming back, a growing diff, no progress) and names the cause and the one change that breaks the loop. Use when a work phase ends, before a context reset, or when the user or agent is stuck, looping, or keeps retrying the same thing.Votes: 0GitHub stars: 2
- Hl Ci FixDiagnose failing required checks on a pull request and apply bounded fixes without weakening tests or CI policy. Use only when the user explicitly asks to fix CI on a pull request.Votes: 0GitHub stars: 2
- Hl Code ReviewReview a diff (current branch, pull request, ref range, tag, or commit) statically at a known revision, with location, trigger, consequence, and evidence for each finding. --deep runs parallel specialists (architecture, simplicity, security, slop, tests, comments, silent failures) and an independent skeptic. --spec also checks the diff against its spec, slice, or issue as a separate axis. Use when the user asks to review code, a branch, or a pull request. Not for a whole-repository security a...Votes: 0GitHub stars: 2
- Hl CommitCommit the staged changes with a grounded conventional message, or preview the message with --dry-run. Use only when the user explicitly asks to commit.Votes: 0GitHub stars: 2
- Hl DebugInvestigate a bug by first building a fast feedback loop that shows the symptom, then running discriminating experiments, and report the supported hypotheses or the defect proven by toggling it. Fixes only when asked, behind a failing regression test. Use when something fails (including a named test the user asks you to explain), behaves unexpectedly, is flaky, or got slower and the cause is unknown. Not for fixing failing pull request checks (use `hl-ci-fix`).Votes: 0GitHub stars: 2
- Hl DeslopRemove AI-generated slop and hallucinations from a change: style tells (narrating comments, defensive cruft on trusted paths, type escapes, needless nesting, one-call wrappers), dead weight (unused code, speculative generality, placeholder residue, reinvented helpers), false claims (comments the code contradicts, phantom references, fabricated numbers, doc drift, error-message drift), and AI prose tells in Markdown, docs, and comments in any language. Edits only changed lines by default; nami...Votes: 0GitHub stars: 2
- Hl DiscoverOrient in an unfamiliar repository or one area of it: purpose, stack, git state, build and test commands, and, in full mode, a source-backed map of layout, responsibilities, callers, entry points, boundaries, dependencies, and a read order. Use when starting work in a new or unfamiliar codebase, when the user asks how a part of the code is organized or where to start reading, or when another agent needs a context pack.Votes: 0GitHub stars: 2
- Hl Explainer VideoMake a short narrated explainer video on one topic, in the style of animated math explainers: a beat-by-beat script, animated scenes, narration from a local voice or a provider the user supplies, captions, and one MP4. Use only when the user explicitly asks for a video explainer. Experimental: behavior and inputs may change in any release.Votes: 0GitHub stars: 2
- Hl GrillCompare structurally different ways to solve a problem, including reuse of what exists, and question the user in rounds, each question with a recommended answer, until a loose idea or a written plan becomes a shared understanding. --gaps instead lists what a written plan or spec is missing (decisions, ambiguous terms, edge cases, acceptance criteria), each with one question. Saves the brief, or with --docs records terms in GLOSSARY.md and proposes ADRs, only when the user explicitly asks. Use...Votes: 0GitHub stars: 2
- Hl ImproveSurvey a codebase and write prioritized, self-contained implementation plans for another agent to execute; never edits source code. Use when asked to audit a codebase for improvements (bugs, security, performance, test coverage, tech debt, migrations, developer experience), to suggest where to take the project next, to write a handoff plan for another agent, to run an architecture audit (dead code, duplication, coupling, layering, dependencies), or to plan a behavior-preserving refactor as sm...Votes: 0GitHub stars: 2
- Hl Launch MarketingProduce marketing artifacts for a solo or small-team software product: positioning block, paste-ready landing copy, 14-day launch plan, ranked channel experiments, 30-day content engine. Produces the artifact, not advice. Also prices the product and designs the offer and unit economics. Use when the user asks how to market, launch, position, or price a product.Votes: 0GitHub stars: 2
- Hl LessonsTurn what went wrong or right in a session or a merged change into the cheapest durable fix, with evidence: an automated check for mechanical mistakes, a review rule for judgement calls, a navigation pointer, an ADR, or a doc. Use when a session or a merged change ends, or when the user wants a retrospective or to capture what was learned. Not for recording a single decision (use `hl-adr`).Votes: 0GitHub stars: 2
- Hl Open PrCreate or preview a pull request from the current branch with why, changes, verification, and risks, as a draft by default. Use only when the user explicitly asks to open a pull request.Votes: 0GitHub stars: 2
- Hl Receive ReviewEvaluate review feedback item by item against the code and decide agree, defer, disagree, or clarify, without applying fixes. Use when the user receives code review comments and wants to decide how to respond.Votes: 0GitHub stars: 2
- Hl Security AuditComplete read-only security audit of a codebase or a path in it. Runs real scanners for evidence, traces untrusted input to dangerous sinks, scores by CWE/CVSS, writes a prioritized report. Use when the user asks for a security review or audit, or whether an attacker can abuse a repository, file, or endpoint. Not for reviewing a single diff (use `hl-code-review`).Votes: 0GitHub stars: 2
- Hl Show MeAnswer the current topic with a picture instead of paragraphs, as pseudocode, a call tree, a component tree, types and signatures, a file tree, a table, a timeline, a Mermaid diagram, a diff shaped like the thing that changes, or one focused HTML page, interactive when the reader must step through or vary the concept. Use when the user says \"show me\", \"draw it\", \"diagram this\", \"what does the flow look like\", \"too much text\", or when the shape of the code, the data, or the change is...Votes: 0GitHub stars: 2
- Hl SpecDraft a grounded feature plan: problem, scope, observable acceptance criteria, assumptions, failure scenarios, and open decisions. --handoff writes it as a brief for another agent to implement. --prd instead writes a full sourced product and technical specification (PRD) in sections, with explicit assumptions, research, and review gaps. Use when the user wants to plan a feature before implementing it, to hand a feature to another agent, or a full product requirements document for a new produc...Votes: 0GitHub stars: 2
- Hl SpikeRun a time-boxed technical spike: define a testable hypothesis and budget, run the fewest discriminating experiments, and conclude proceed, pivot, or inconclusive. Use when a technical unknown blocks a decision.Votes: 0GitHub stars: 2
- Hl Split PrPropose how to split a large diff into coherent, dependency-ordered pull requests without rewriting history. Use when a branch is too large to review as one change.Votes: 0GitHub stars: 2
- Hl StartupTake a software product from no idea to keep or kill. scout finds SaaS ideas a solo developer can ship with an AI coding agent, from live pain signals, scored on evidence. evaluate (default) runs five gated stages (core assumption, problem validation, competition, first 10 customers, two-week MVP test) ending in go, pivot, stop, or insufficient evidence; --stage runs one. ship decides the smallest first version to launch; kill decides whether to continue, pivot, or shut down a product based o...Votes: 0GitHub stars: 2
- Hl TddImplement one observable behavior through a verified red-green-refactor cycle at an agreed seam: failing test first, smallest change, then refactor. Use when implementing a behavior or slice test-first. Not for finding the cause of a bug (use `hl-debug`).Votes: 0GitHub stars: 2
- Hl TicketsSplit a feature or plan into thin, independently verifiable delivery slices, each one pull request, as Markdown files or GitHub issues. --tracker writes paste-ready tickets in the real field conventions and markup of Jira, Linear, GitHub, GitLab, or a similar tracker, gated on a stranger test and a no-invention rule. Use when a plan, spec, or intent needs to become executable tickets, agent tasks, epics, stories, or sub-tasks, or when tickets keep coming back with \"what does this actually me...Votes: 0GitHub stars: 2
- Hl VerifyCheck each requested outcome against current artifacts and real command results, and report passed, failed, unverified, or blocked per requirement. --claim measures a change's claimed effect against a matched baseline. --text checks the factual claims in a text against current files and primary sources, and annotates each one as supported, corrected, conflicting, or unverified. Use when about to claim work is done, when the user asks whether a task is really done, when proving a claim such as...Votes: 0GitHub stars: 2
- Hl Writing For AgentsWrite text an agent executes. By default, rewrite a raw intent, a prompt, a system prompt, or an AGENTS.md or other instruction-file snippet into the shortest text that gets the behavior, for any capable LLM; --for loop|goal tunes a prompt that runs unattended; --verify <check> gives a task prompt its done predicate. --skill writes or reviews an agent skill (SKILL.md): one job, a description that triggers at the right time, an output a person can skim, a lean body, and checks before it ships....Votes: 0GitHub stars: 2