All authors
Claude Skills by alexei-led
github.com/alexei-led140 skills0 installs159 views
- Committing CodeSmart git commits with logical grouping. Use when user says "commit",Votes: 0GitHub stars: 36
- Browser AutomationProve rendered behavior in a real browser and report pass, fail, or blocked with evidence. Keep automation temporary unless the user asks for permanent tests.Votes: 0GitHub stars: 36
- Committing CodeGroup the working-tree changes by purpose and commit them as normal commits. Done when each intended change is in one logical commit and the final `git status` is shown.Votes: 0GitHub stars: 36
- Documenting CodeTurn implementation facts into docs that a named reader can use. Every claim in the result matches the code, and every visual renders cleanly.Votes: 0GitHub stars: 36
- Fixing CodeFix the requested defect or failing gate, one verified root cause at a time. Use the matching `writing-<lang>` skill for toolchain commands. Without write access, return proposed changes (file, change, reason) instead of applying them.Votes: 0GitHub stars: 36
- Improving TestsMake tests catch real behavior regressions without blocking safe changes. Suite latency is a quality attribute; coverage is a signal, not the goal. Without write access, return proposed changes (file, change, reason) instead of applying them. Read the reference for each language in scope; it covers test patterns and suite speed. Use the matching `writing-<lang>` skill for toolchain commands. - C#: `references/csharp.md` - Go: `references/go.md` - Java/Kotlin: `references/java-kotlin.md` - Pyt...Votes: 0GitHub stars: 36
- Reviewing CodeProduce findings, not edits, for the requested diff, PR, changed files, or file list. Read `references/severity-rubric.md` before scoring or reporting: it owns the dimensions, severity, confidence, and score rules. Load a language reference only when a finding needs language or framework semantics; do not read every reference merely because that language is in scope: - C#: `references/csharp.md` - Go: `references/go.md` - Java/Kotlin: `references/java-kotlin.md` - Python: `references/python.m...Votes: 0GitHub stars: 36
- Brainstorming IdeasTurn a vague idea or draft plan into a chosen design before coding. Done when the user picks or defers an approach with its trade-offs known, decisions and open questions recorded, and no implementation task list produced.Votes: 0GitHub stars: 36
- Evolving ConfigAudit AI coding-agent configuration and report prioritized, evidence-backed findings with the smallest fix for each. Local files come first; official docs and changelogs settle syntax, feature availability, and deprecation. Do not recommend a change on the strength of an uncited blog. For installed cc-thingz resource or version diagnostics, use installation-doctor first and continue here for broader review or authorized changes.Votes: 0GitHub stars: 36
- Looking Up DocsAnswer API, syntax, and config questions from version-correct sources. When a lookup tool is available, do not answer syntax from memory. Never put secrets, credentials, personal data, private payloads, or proprietary code into an external query. Strip them and still look up the public docs; if the question cannot be asked without them, answer from local context and say so.Votes: 0GitHub stars: 36
- Researching WebAnswer with current, cited evidence and keep sourced facts apart from your recommendation. Research questions get web evidence, not answers from memory. Never put private code, secrets, credentials, or proprietary data into a web query; answer those from local context and say what that limits.Votes: 0GitHub stars: 36
- Reviewing InstructionsScore AI-facing instruction files and report findings an author can act on. The target style: outcome and done criteria up front, each rule stated once, hard constraints explicit, nothing the model already knows, portable across agent targets. The writing-skills skill teaches the same style to authors. Done when every in-scope file has a score, a cited reason per dimension, caps applied, and a confidence level, and every finding quotes or locates its evidence.Votes: 0GitHub stars: 36
- Sequential ThinkingSame intent as MCP-based sequential-thinking tools — present numbered decision summaries with revision and branch semantics — implemented as visible Markdown so reasoning-capable models can follow it without an extra tool round-trip.Votes: 0GitHub stars: 36
- Writing SkillsCreate or reshape a skill so it loads at the right time, gives the model the result and the finish line, and ships intact to every target. The same rules apply to agent bodies and other AI-facing instruction files; the reviewing-instructions skill scores against them. Done when the skill meets the shape and writing rules below, the rendered Claude skill still holds the base body and its reference links, and the relevant build/test/lint checks pass on what you changed, or you name each check t...Votes: 0GitHub stars: 36
- Cleanup GitUse the target repo's own `scripts/cleanup-git.sh` if it ships one, otherwise this skill's script. Inspect a repo-provided script before relying on its safety policy. Use direct deletion only for a specifically approved exception described below; never pipe a branch list into force-delete. ```bash scripts/cleanup-git.sh # preview (default) scripts/cleanup-git.sh --apply # execute the requested safe cleanup scripts/cleanup-git.sh --apply --force --branch <name> # app...Votes: 0GitHub stars: 36
- Configuring Git HygieneSet up project-local hygiene that stays fast enough to keep enabled. Stop if the directory is not a git repo.Votes: 0GitHub stars: 36
- Using Git WorktreesA worktree gives parallel work its own folder and branch while the main worktree stays clean on the integration branch. Each project gets one sibling root, `<project>.worktrees/`, with one directory per branch named by its slug (`/` → `-`, so `feature/auth` → `feature-auth`). Remove the worktree and branch after the PR merges. A plain branch switch with no parallel work needs no worktree: check `git status --short`, then `git switch <branch>`. Trivial solo one-liners may also stay in the main...Votes: 0GitHub stars: 36
- Operating InfraWork from files, plans, logs, and read-only commands; edit repo files freely, but touch live resources only under these rules: - Before any cloud command, confirm identity (`aws sts get-caller-identity --profile <profile>`; `gcloud auth list`, `gcloud config list`), passing profile, project, region, and zone explicitly instead of relying on CLI defaults. - Before any live change that's destructive, costly, or externally visible (apply, upgrade, rollout, delete, destroy, stop, resize, scale, I...Votes: 0GitHub stars: 36
- Writing CsharpCheck the nearest `*.csproj`, `Directory.Build.props`, `global.json`, and CI for `TargetFramework(s)`, `LangVersion`, nullable context, and analyzer policy before using newer syntax. Without an explicit `LangVersion`, the C# version follows the TFM (`net8.0` defaults to C# 12; `net6.0` defaults to C# 10, which lacks primary constructors and collection expressions). Project conventions win over these defaults, and raising `LangVersion` or the TFM to unlock syntax is a separate decision — ask f...Votes: 0GitHub stars: 36
- Writing GoCheck `go.mod` (`go` and `toolchain` lines) and CI before using version-gated APIs. Project conventions win over these defaults.Votes: 0GitHub stars: 36
- Writing Java Kotlin- Read the wrapper properties, `settings.gradle*`/`build.gradle*`/`gradle.properties` or `pom.xml`, and CI before relying on version-specific behavior. - Use `./gradlew`/`./mvnw` when the repo has them; scope tests to the changed module (see testing.md). - The compile target is the declared Java toolchain and Kotlin `jvmToolchain`, not the shell's `JAVA_HOME`; without one, the running JDK compiles. - Toolchain, plugin, and dependency versions live in convention plugins, version catalogs, BOMs, oVotes: 0GitHub stars: 36
- Writing Python`pyproject.toml` is the source of truth for the Python target, tools, scripts, and dependencies. Check it, `.python-version`, and CI before using 3.12-only syntax. Project conventions win over these defaults.Votes: 0GitHub stars: 36
- Writing RustCovers crates, workspaces, and Rust CLIs. Check `Cargo.toml`, `rust-toolchain.toml`, and CI before using newer syntax or APIs. Project conventions win over these defaults.Votes: 0GitHub stars: 36
- Writing ShellIn GitHub Actions, this skill owns the shell inside `run:` blocks; operating-infra owns the workflow YAML around it (jobs, permissions, actions, secrets, caching). Mixed changes use both.Votes: 0GitHub stars: 36
- Writing TypescriptFollow the repository's TypeScript version, tsconfig, package manager, framework, and test runner. In a monorepo, work from the nearest `package.json` and `tsconfig.json` and name the package you chose.Votes: 0GitHub stars: 36
- Writing WebFollow the existing template language, asset pipeline, and conventions. Add a dependency, build step, or framework only when the project already uses it or the user approves; requests that need a SPA framework belong to writing-typescript.Votes: 0GitHub stars: 36
- Spec FlowLightweight loop for controlled work, one task at a time: plan one slice, execute one task, checkpoint or close, repeat. `scripts/specctl` (written `specctl` below) owns state. Do not edit task status or `.spec/SESSION.yaml` by hand. `references/specctl-commands.md` lists every command. `references/method.md` covers task quality, templates, the planning output, and the mini-interview.Votes: 0GitHub stars: 36
- Browser AutomationProve rendered behavior in a real browser and report pass, fail, or blocked with evidence. Keep automation temporary unless the user asks for permanent tests.Votes: 0GitHub stars: 36
- Committing CodeGroup the working-tree changes by purpose and commit them as normal commits. Done when each intended change is in one logical commit and the final `git status` is shown.Votes: 0GitHub stars: 36
- Documenting CodeTurn implementation facts into docs that a named reader can use. Every claim in the result matches the code, and every visual renders cleanly.Votes: 0GitHub stars: 36
- Fixing CodeFix the requested defect or failing gate, one verified root cause at a time. Use the matching `writing-<lang>` skill for toolchain commands. Without write access, return proposed changes (file, change, reason) instead of applying them.Votes: 0GitHub stars: 36
- Improving TestsMake tests catch real behavior regressions without blocking safe changes. Suite latency is a quality attribute; coverage is a signal, not the goal. Without write access, return proposed changes (file, change, reason) instead of applying them. Read the reference for each language in scope; it covers test patterns and suite speed. Use the matching `writing-<lang>` skill for toolchain commands. - C#: `references/csharp.md` - Go: `references/go.md` - Java/Kotlin: `references/java-kotlin.md` - Pyt...Votes: 0GitHub stars: 36
- Reviewing CodeProduce findings, not edits, for the requested diff, PR, changed files, or file list. Read `references/severity-rubric.md` before scoring or reporting: it owns the dimensions, severity, confidence, and score rules. Load a language reference only when a finding needs language or framework semantics; do not read every reference merely because that language is in scope: - C#: `references/csharp.md` - Go: `references/go.md` - Java/Kotlin: `references/java-kotlin.md` - Python: `references/python.m...Votes: 0GitHub stars: 36
- Brainstorming IdeasTurn a vague idea or draft plan into a chosen design before coding. Done when the user picks or defers an approach with its trade-offs known, decisions and open questions recorded, and no implementation task list produced.Votes: 0GitHub stars: 36
- Evolving ConfigAudit AI coding-agent configuration and report prioritized, evidence-backed findings with the smallest fix for each. Local files come first; official docs and changelogs settle syntax, feature availability, and deprecation. Do not recommend a change on the strength of an uncited blog. For installed cc-thingz resource or version diagnostics, use installation-doctor first and continue here for broader review or authorized changes.Votes: 0GitHub stars: 36
- Looking Up DocsAnswer API, syntax, and config questions from version-correct sources. When a lookup tool is available, do not answer syntax from memory. Never put secrets, credentials, personal data, private payloads, or proprietary code into an external query. Strip them and still look up the public docs; if the question cannot be asked without them, answer from local context and say so.Votes: 0GitHub stars: 36
- Researching WebAnswer with current, cited evidence and keep sourced facts apart from your recommendation. Research questions get web evidence, not answers from memory. Never put private code, secrets, credentials, or proprietary data into a web query; answer those from local context and say what that limits.Votes: 0GitHub stars: 36
- Reviewing InstructionsScore AI-facing instruction files and report findings an author can act on. The target style: outcome and done criteria up front, each rule stated once, hard constraints explicit, nothing the model already knows, portable across agent targets. The writing-skills skill teaches the same style to authors. Done when every in-scope file has a score, a cited reason per dimension, caps applied, and a confidence level, and every finding quotes or locates its evidence.Votes: 0GitHub stars: 36
- Writing SkillsCreate or reshape a skill so it loads at the right time, gives the model the result and the finish line, and ships intact to every target. The same rules apply to agent bodies and other AI-facing instruction files; the reviewing-instructions skill scores against them. Done when the skill meets the shape and writing rules below, the rendered Claude skill still holds the base body and its reference links, and the relevant build/test/lint checks pass on what you changed, or you name each check t...Votes: 0GitHub stars: 36
- Cleanup GitUse the target repo's own `scripts/cleanup-git.sh` if it ships one, otherwise this skill's script. Inspect a repo-provided script before relying on its safety policy. Use direct deletion only for a specifically approved exception described below; never pipe a branch list into force-delete. ```bash scripts/cleanup-git.sh # preview (default) scripts/cleanup-git.sh --apply # execute the requested safe cleanup scripts/cleanup-git.sh --apply --force --branch <name> # app...Votes: 0GitHub stars: 36
- Configuring Git HygieneSet up project-local hygiene that stays fast enough to keep enabled. Stop if the directory is not a git repo.Votes: 0GitHub stars: 36
- Using Git WorktreesA worktree gives parallel work its own folder and branch while the main worktree stays clean on the integration branch. Each project gets one sibling root, `<project>.worktrees/`, with one directory per branch named by its slug (`/` → `-`, so `feature/auth` → `feature-auth`). Remove the worktree and branch after the PR merges. A plain branch switch with no parallel work needs no worktree: check `git status --short`, then `git switch <branch>`. Trivial solo one-liners may also stay in the main...Votes: 0GitHub stars: 36
- Operating InfraWork from files, plans, logs, and read-only commands; edit repo files freely, but touch live resources only under these rules: - Before any cloud command, confirm identity (`aws sts get-caller-identity --profile <profile>`; `gcloud auth list`, `gcloud config list`), passing profile, project, region, and zone explicitly instead of relying on CLI defaults. - Before any live change that's destructive, costly, or externally visible (apply, upgrade, rollout, delete, destroy, stop, resize, scale, I...Votes: 0GitHub stars: 36
- Writing CsharpCheck the nearest `*.csproj`, `Directory.Build.props`, `global.json`, and CI for `TargetFramework(s)`, `LangVersion`, nullable context, and analyzer policy before using newer syntax. Without an explicit `LangVersion`, the C# version follows the TFM (`net8.0` defaults to C# 12; `net6.0` defaults to C# 10, which lacks primary constructors and collection expressions). Project conventions win over these defaults, and raising `LangVersion` or the TFM to unlock syntax is a separate decision — ask f...Votes: 0GitHub stars: 36
- Writing GoCheck `go.mod` (`go` and `toolchain` lines) and CI before using version-gated APIs. Project conventions win over these defaults.Votes: 0GitHub stars: 36
- Writing Java Kotlin<!-- Codex platform guidance --> <!-- Use this platform's installed tool names exactly for shell, file reads, and search. If a referenced helper or optional tool is unavailable, say so and continue with built-in tools. -->Votes: 0GitHub stars: 36
- Writing Python`pyproject.toml` is the source of truth for the Python target, tools, scripts, and dependencies. Check it, `.python-version`, and CI before using 3.12-only syntax. Project conventions win over these defaults.Votes: 0GitHub stars: 36
- Writing RustCovers crates, workspaces, and Rust CLIs. Check `Cargo.toml`, `rust-toolchain.toml`, and CI before using newer syntax or APIs. Project conventions win over these defaults.Votes: 0GitHub stars: 36
- Writing ShellIn GitHub Actions, this skill owns the shell inside `run:` blocks; operating-infra owns the workflow YAML around it (jobs, permissions, actions, secrets, caching). Mixed changes use both.Votes: 0GitHub stars: 36
- Writing TypescriptFollow the repository's TypeScript version, tsconfig, package manager, framework, and test runner. In a monorepo, work from the nearest `package.json` and `tsconfig.json` and name the package you chose.Votes: 0GitHub stars: 36