All authors
Claude Skills by edloidas
github.com/edloidas39 skills0 installs93 views
- BroRestate the previous answer — or the connected thread of answers — as something shorter and easier to act on: the bottom line first, only what matters, and anything to decide at the end.Votes: 0GitHub stars: 2
- DiscussWork through a design question as a dialogue rather than a lecture — investigate the ground, take a position on it, lay out the options with a pick among them, and push back on what will not hold up. Works one part of the design at a time. Reads and verifies; writes nothing.Votes: 0GitHub stars: 2
- ExplainExplain how something actually works — code, a type, an error, a fix, a design — by tracing the mechanism on concrete values instead of describing it. Also checks whether the user's own account of something is correct.Votes: 0GitHub stars: 2
- HandoffCompact the current conversation into a handoff so a fresh agent, or future-you, can pick up the work cold. With a `doc`, `document`, or `--doc` keyword, writes a per-project handoff file and prints only its path plus a shortcut to start the next session.Votes: 0GitHub stars: 2
- OutsiderQuick opinion from an agent CLI outside this session — ask a specific question with context, or review code changes. Picks an installed agent that is not the one running this skill, so the answer comes from a different model in a different process. Lighter and faster than a full review board.Votes: 0GitHub stars: 2
- Ci AuditAudit GitHub Actions workflows for what costs wall clock, costs money, or lets a pipeline pass without checking anything. Builds the job graph, then runs a catalog covering gating correctness, the critical path, caching effectiveness, and spend. Reads and reports only; never edits a workflow.Votes: 0GitHub stars: 2
- React AuditFind the React problems linters cannot see: effects that should not exist or re-run for the wrong reason, memoization that is missing or pointless, state that should be an action or a reducer, and components that have outgrown themselves. Reports, never edits.Votes: 0GitHub stars: 2
- Scripts AuditAudit package.json scripts for naming, composition, lifecycle hooks, consistency, and performance.Votes: 0GitHub stars: 2
- Security AuditAudit a repository for security risks — supply chain, CI, release, runtime, secrets, repository settings, and package-manager install-time controls for pnpm and bun. Reads and reports only; never mutates the repo or its GitHub settings. Aggregates findings from focused subagents across whichever areas the repo exposes.Votes: 0GitHub stars: 2
- Skill AuditAudit Agent Skills for what no validator can decide: whether a description will ever fire, whether the instructions are followable, whether the body earns its token cost, whether `compatibility` matches what the body requires, and whether mutations are gated. Runs the repo's structural validators first, scores six judgment categories with cited evidence, and returns a PASS / FAIL verdict.Votes: 0GitHub stars: 2
- Tests AuditAudit an existing test suite for anti-patterns — tautological mock round-trips, weak assertions (toBeDefined / assertNotNull), implementation coupling, flaky timing, snapshot rubber-stamping, and tests claiming guarantees they cannot provide — and report a keep / tighten / rewrite / delete verdict per test.Votes: 0GitHub stars: 2
- Three AuditAudit Three.js and React Three Fiber code for performance and correctness issues that hurt frame rate in WebGL scenes — uncapped devicePixelRatio, fillrate blowups, missing disposals, render-loop allocations, and similar pitfalls. Walks through detecting each issue, assessing the offending sites in context, and reporting findings grouped by severity.Votes: 0GitHub stars: 2
- Tsconfig AuditAudit tsconfig.json against TypeScript 7 and report which compilerOptions are hard errors, which are redundant and safe to drop, and which must now be added.Votes: 0GitHub stars: 2
- Workspace AuditAudit a pnpm 10+ workspace for configuration and monorepo problems: dependency placement, workspace protocol usage, hoisting, catalog configuration, build order and build hooks, dependency rules, and .npmrc settings that are now defaults. Reads and reports only.Votes: 0GitHub stars: 2
- Commit SummaryWrite a commit message body by deriving it from the code, not by summarizing the diff. Weighs the change, then either answers seven questions against the implementation — what forces it, which call paths reach it, how it failed, what breaks on update, what the tests pin — or produces a two-to-three-line body for mechanical and generated changes. Not for full commit creation.Votes: 0GitHub stars: 2
- CommitStage safe changes on the current branch and create a single conventional commit. Skips generated artifacts, caches, logs, and editor cruft. Accepts hints like "only staged", "relevant", or "amend".Votes: 0GitHub stars: 2
- Fix And ReverifyFix what a review found, then review the fix. Runs review and fix in rounds: triage findings by severity and confidence, fix the ones that clear the gate, confirm the tree still builds and its tests still pass, then attack the fix itself rather than the whole change again. Fixes automatically by default and reports anything with a real trade-off; `--interactive` asks instead.Votes: 0GitHub stars: 2
- Live ProbeSettle a claim about observable behavior by running the thing and looking at the result, once. Finds the project's declared way to run and observe, picks the cheapest rung that answers the claim — a narrowed existing check, a throwaway probe, the built artifact queried directly, a rendered frame compared — and returns a verdict with the artifact it read. One hypothesis, one observation, then it stops. Not a debugging loop.Votes: 0GitHub stars: 2
- Resolve ConflictsResolve git merge and rebase conflicts semi-automatically. Classifies conflicts by type (DU/UD/UU/AA/DD), auto-resolves trivial ones, and applies context-aware resolution for the rest.Votes: 0GitHub stars: 2
- Agent ConfigSet up and maintain a repository's agent instruction layer — one real root instruction file, an AGENTS.md symlink so every agent reads the same document, a comment-convention block, and a drift check that catches documented commands, paths, structures, and counts that no longer match the repo.Votes: 0GitHub stars: 2
- Editor ConfigInitialize a project with canonical editor configurations (Zed, VSCode). Asks which editors to set up, then writes or merges the bundled settings into the repo. On conflict our values win; keys we do not define are preserved.Votes: 0GitHub stars: 2
- Labels SyncSynchronize or export GitHub repository labels against a predefined label set. Compares, creates, updates, deletes, or reads labels as reusable JSON definitions.Votes: 0GitHub stars: 2
- Lint SyncMigrate ESLint and Prettier to Biome or Oxc (including Vite+), or modernize an existing config. Detects source and target configs, compares rules, flags stale nursery rules, suggests new features, and generates actionable config changes.Votes: 0GitHub stars: 2
- Repo HardeningApply a security hardening baseline to a GitHub repository via gh api — branch and tag rulesets, Actions token defaults, secret scanning, Dependabot, private vulnerability reporting, CodeQL, immutable releases, and branch-restricted environments for deploy secrets. The write half of the pair with audit:security-audit, which finds the same gaps read-only.Votes: 0GitHub stars: 2
- Stale Process CleanupFind and kill stale, leftover, or orphaned developer processes owned by the current user — abandoned dev servers (Vite / Vite+), editor LSP servers (oxlint), and duplicate or zombie MCP servers (playwright, context7, obsidian) left running after a shell, editor, or agent session exited.Votes: 0GitHub stars: 2
- Working DocsManage working documents in an Obsidian vault using a two-tier system — Inbox for quick dumps, Dev/Claude for persistent docs. Creates, finds, promotes, updates, and completes working documents with proper naming, headers, and lifecycle.Votes: 0GitHub stars: 2
- Issue AnalyzeFetch a GitHub issue by number or URL, analyze its scope of work, cross-reference local project docs and repo instruction files, check blocking relationships, and produce a structured implementation analysis with a task list.Votes: 0GitHub stars: 2
- Issue FlowFull GitHub issue lifecycle: pick an issue, create it, branch, commit, squash, push, PR, merge. Owns every git and gh write in the pipeline. Handles project board integration, base branch detection (main/master/epic-*), and compact step reports. Supports entering at any step.Votes: 0GitHub stars: 2
- Issue WriterDraft or update a GitHub issue. Analyzes the description, asks clarifying questions, and produces a well-structured title and body following the project's template. Can update an existing issue or prepare a draft for filing later.Votes: 0GitHub stars: 2
- Changes ReviewAttack a code change and report what survives. Dispatches independent reviewers in parallel, each with a single job and no access to the implementer's reasoning: one hunts correctness bugs blind to the issue, one hunts requirement gaps against the issue text, one runs outside the process entirely. Optionally re-attacks its own findings, then synthesizes what is left. Returns findings and changes nothing — no tooling, no autofix, no edits. On request it publishes to the author, gated on demons...Votes: 0GitHub stars: 2
- Code CleanupPost-implementation cleanup of correct code. Prunes comments aggressively: deletes what restates the code, files design rationale to the commit message and wider context to the PR or an issue, collapses one mechanism explained in three places, strips issue and PR references that make a file unreadable on its own, compacts genuine gotchas, renames unclear symbols so a comment is not needed, checks the code against the project's conventions, and simplifies what is more complicated than it needs...Votes: 0GitHub stars: 2
- Code To SpecExtract a behavioral specification from a source-code bundle — a handful of files up to a whole 500+ file application. Produces reproducible, stack-neutral specs another engineer or LLM could use to rebuild the same observable behavior without reading the original source.Votes: 0GitHub stars: 2
- ConsiliumApproach board for a problem or a decision. Dispatches independent seats — some generating candidate approaches, including one agent outside this process entirely, some attacking the assembled set comparatively — then verifies the surviving objections and reports a ranked recommendation with its trade-offs. An approach already on the table enters as one candidate among several. Autonomous; changes nothing.Votes: 0GitHub stars: 2
- DoubtRule on a set of claims that already exists — review findings, a plan's assumptions, an analysis, a reviewer's objection — before anyone acts on them. Every claim gets exactly one verdict: it holds, it holds only in a narrower case, it is true but not worth the fix, it falls, or nobody can settle it. Whoever judges never sees the reasoning that produced the claim. Reads and reasons; changes nothing.Votes: 0GitHub stars: 2
- Pr ReviewHandle a pull request from whichever side you are on. On someone else's branch it attacks the diff through changes-review, then publishes a real review with per-line comments and a verdict. On your own it works the threads people and bots left — decides its standing in each, verifies the claim before answering, runs the project's checks, then replies and resolves. Changes no code unless asked.Votes: 0GitHub stars: 2
- Npm ReleaseRelease an npm, pnpm, or bun package: version bump, validation, git tagging, and publishing, with safety checks and explicit user approval before anything is pushed.Votes: 0GitHub stars: 2
- Skills ReleaseRelease workflow for the edloidas/skills collection. Validates git state, analyzes commits since the last tag, recommends a version bump (major/minor/patch), updates Claude and Codex packaging metadata, commits, tags, and pushes.Votes: 0GitHub stars: 2
- Solve IssueEnd-to-end GitHub issue workflow: analyze the issue, plan and implement, verify with available tests/build/lint and an optional live observation, simplify, audit the tests it added, attack the change with parallel adversarial reviewers and fix what they find, trim comments and artifacts, then choose a push / PR / merge endgame — holding the merge while Copilot and other automated reviewers report, and answering and resolving their threads. The lifecycle's git and GitHub writes are delegated t...Votes: 0GitHub stars: 2
- Markdown WritingWrite Markdown that people actually read — READMEs, docs, PR bodies, issue bodies and comments, release notes, changelogs. Covers GitHub-flavored extras (alerts, collapsible sections, task lists, mermaid), prose that leads with the point instead of burying it, and a README skeleton.Votes: 0GitHub stars: 2