个人作者

Jon Gallant

Azure Developer Experience Architect

机构 · Microsoft所在地 · Seattle, WA访问官网 ↗更新于 2026-11-15

Skills
26
仓库
1
职业覆盖
0
场景覆盖
0
Stars
★ 18

Jon Gallant 的 Skills 26

jongio
jongio/skills

test-doctor

Audit test suite correctness, meaningful coverage, reliability, framework compatibility, and maintenance cost; optionally write missing tests and repair material gaps. USE FOR: test doctor, test health, test audit, are my tests good, write missing tests, fix flaky tests, improve test coverage. DO NOT USE FOR: routine test execution, application scaffolding, dependency upgrades (use deps-doctor), community health files (use repo-ready), or a source-code security review.

★ 18
jongio
jongio/skills

skill-doctor

**WORKFLOW SKILL** - Improve skills from recent sessions and reduce instruction bloat, using cached audits, a dedicated worktree, and one PR. USE FOR: skill doctor, skill-doctor, improve skills from session feedback, trim skill instructions. DO NOT USE FOR: single-session closeout (use retro), creating skills (use create-skill), standalone PR delivery (use pr), repository cleanup (use git-tidy).

★ 18
jongio
jongio/skills

session-statusline

Manage only the current session's active statusline pills and clear entries without deleting work or changing enabled components. USE FOR: name this session, custom statusline name, label this terminal session, rename session label, clear session name, clear statusline, clear footer pills, remove a PR pill, remove an issue pill, clear agent pills, track active session work, refresh session statusline. DO NOT USE FOR: PR delivery (use pr), issue implementation (use go), branch or worktree deletion (use git-tidy), terminal tab or window titles, built-in footer styling.

★ 18
jongio
jongio/skills

secops-doctor

**WORKFLOW SKILL** - Audit repository and application security across OWASP/STRIDE, secrets, workflows, containers, and Cloudflare with Public Repo Stealth Mode. USE FOR: secops doctor, secops-doctor, security audit, OWASP STRIDE check, stealth security fixes, container and Cloudflare security audit. DO NOT USE FOR: routine dependency bumps (use deps-doctor), community health file scaffolding (use repo-ready), general refactoring (use refactor).

★ 18
jongio
jongio/skills

retro

**WORKFLOW SKILL** - Close out a session with an evidence-backed task and feedback audit, source-skill improvements, and safely approved branch and worktree cleanup. USE FOR: retro, session retro, session retrospective, wrap up this session, check whether we are done, reconcile my feedback. DO NOT USE FOR: standalone PR delivery (use pr), standalone repository cleanup (use git-tidy), creating new skills (use create-skill), unrelated historical session audits.

★ 18
jongio
jongio/skills

refactor

Plan behavior-preserving refactoring with explicit scope, depth and risk choices. USE FOR: small wins, code cleanup, refactor assessment, local restructuring, cross-module refactoring, idiomatic cleanup. DO NOT USE FOR: product changes, bug fixes, dependency upgrades (use deps-doctor), security reviews, formatting-only passes, or unapproved implementation.

★ 18
jongio
jongio/skills

doc-doctor

Check documentation against code. USE FOR: doc-doctor, check docs, stale docs, broken links, README accuracy. DO NOT USE FOR: general code review or standalone test audits (use test-doctor).

★ 18
jongio
jongio/skills

dns-doctor

Evidence-first DNS and domain health audit covering delegation, records, DNSSEC, CAA, website routing, TLS, CDN behavior, SPF, DKIM, DMARC, MTA-STS, TLS reporting, dangling aliases, TTLs, and zone hygiene. Produces verified findings, cached delta reports, an ordered remediation plan, and exact user-approved provider changes. USE FOR: dns-doctor, DNS audit, domain health check, diagnose DNS, DNS delta, fix DNS, update DNS records, apply DNS changes, website routing failure, email authentication review, DNSSEC review, CDN or proxy analysis. DO NOT USE FOR: unauthorized changes, implicit or unattended provider mutations, general network performance tuning, broad SEO audits.

★ 18
jongio
jongio/skills

ci-doctor

**WORKFLOW SKILL** - Diagnose, check, and optimize GitHub Actions workflows with stateless ETag-cached checkups, main failure root-cause repair in isolated worktrees, and workflow cost/security hardening. USE FOR: ci-doctor, ci health check, diagnose main CI failures, repair broken GitHub Actions builds, profile slow CI steps, harvest workflow flakes, harden and optimize GitHub Actions workflows. DO NOT USE FOR: single pull request delivery without workflow diagnosis (use pr), implementing a feature issue end to end (use go), standalone test suite audits without GitHub Actions checks (use test-doctor).

★ 18
jongio
jongio/skills

go

**WORKFLOW SKILL** - Plan, test, and implement the current context, then hand verified changes to pr for delivery and merge. USE FOR: /go, implement this context end to end, take this issue from plan to merge. DO NOT USE FOR: PR-only work on existing changes (use pr), standalone test audits (use test-doctor), Go language questions without an implementation request.

★ 18
jongio
jongio/skills

repo-ready

Scaffold and maintain the standard community health files every GitHub repository needs: .gitignore, .gitattributes, LICENSE, README.md, CONTRIBUTING.md, CODE_OF_CONDUCT.md, SECURITY.md, FUNDING.yml, CODEOWNERS, issue/PR templates, dependabot.yml, .editorconfig, and CI workflows. Two modes: **init** (interview the user, detect the stack, scaffold everything from scratch) and **update** (scan an existing repo, identify gaps against best practices, and suggest additions file by file). Use when the user says "repo ready", "repo init", "repo health", "community health", "add gitignore", "add license", "repo files", "repo setup", or asks about missing repo files. Do NOT use for project code scaffolding, GitHub Pages setup (use create-gh-pages-site), or CI pipeline design beyond the starter workflow.

★ 18
jongio
jongio/skills

repo-maintain

**WORKFLOW SKILL** - Run an end-to-end repository maintenance pass across governance, dependencies, security, refactoring, coverage, docs, skills, and evals on a single rolling branch. USE FOR: repo-maintain, maintain repo, repo maintenance pass, automated repository maintenance, health score, repo-maintain/automated. DO NOT USE FOR: implementing product features (use go), standalone PR watch (use pr), creating new skills (use create-skill).

★ 18
jongio
jongio/skills

release-doctor

**WORKFLOW SKILL** - Verify post-merge release readiness, unreleased commits, semver recommendations, and cross-manifest version parity before cutting a release. USE FOR: release doctor, release-doctor, needs release, release readiness check, version parity audit, semver recommendation. DO NOT USE FOR: dependency upgrades (use deps-doctor), changelog-only prose edits (use doc-doctor), feature implementation (use go).

★ 18
jongio
jongio/skills

pr

**WORKFLOW SKILL** - A concise checklist workflow for taking changes from local commit and preflight checks through PR submission, review resolution, CI monitoring, and merge. USE FOR: /pr, PR checklist, prepare a PR, submit a PR, monitor a PR, address PR feedback, merge a PR. DO NOT USE FOR: non-PR git cleanup (use git-tidy) or standalone test-only audits (use test-doctor).

★ 18
jongio
jongio/skills

naming-is-hard

Interactive naming assistant: help the user land on a name for a project, product, repo, company, package, or feature they love AND can actually use. Use when the user says "name my project", "help me name this", "come up with a name", "brainstorm names", "what should I call it", "rename this project", "is this name taken", "check if a name is available", "check the domain / GitHub org / npm / handle", "is there a trademark", or "naming is hard". The skill profiles what the thing is, generates on-brief candidate names, then runs a swipe loop (Like / Pass / Super-like) where a preference model learns the user's taste and shows more of what they like, then scores the finalists against real availability (domains, GitHub, package registries, social handles) plus trademark, existing-business, and confusable-name screens. Every finalist gets one of three verdicts: Deal Breaker, It's Complicated, or Perfect Match. Do NOT use for renaming code identifiers or SEO keyword research.

★ 18
jongio
jongio/skills

eval-doctor

**WORKFLOW SKILL** - Audit, author, and harden AI skill and prompt evaluations with Vally, github/evals, deterministic graders, and safe github/evals-action CI workflows. USE FOR: eval doctor, eval-doctor, audit evals, create eval.yaml, vally lint, github/evals, github/evals-action CI. DO NOT USE FOR: SKILL.md prose or session-history trimming (use skill-doctor), unit test coverage (use test-doctor), general CI debugging (use ci-doctor).

★ 18
jongio
jongio/skills

eli5

Explain the subject already in context using simple, respectful language, a familiar analogy, the proper grown-up terms, and the point where the analogy stops matching reality. Use when the user says "explain like I'm five", "explain it to me like I'm 5", "ELI5", "explain this simply", "make this easy to understand", or asks for a beginner-friendly explanation of the current selection, attachment, code, error, design, or conversation topic. Do NOT use for code review, debugging, implementation, documentation generation, architecture design, or requests that need new research rather than a simpler explanation of supplied context.

★ 18
jongio
jongio/skills

deps-doctor

Audit, update, and secure project dependencies across npm, pnpm, Yarn, pip, Pipenv, Poetry, uv, Go, Cargo, Bundler, Composer, NuGet, Maven, Gradle, Swift, pub, and Hex, plus Docker base images, GitHub Actions, Terraform, and dev container features. Finds outdated, unused, and undeclared packages; applies updates; withholds releases too new to have been vetted; ranks vulnerabilities by exploitation evidence; screens supply-chain risk; fixes breaking changes forward; and verifies builds and tests. Use when the user says "dep doctor", "dependency doctor", "update dependencies", "upgrade packages", "outdated packages", "dependency audit", "security patches", "CVE remediation", or "deps". Do NOT use for adding a single new package, general code refactoring, a source-code security review, or fixing a build unrelated to dependency changes.

★ 18