jongio/jongio-skills

**WORKFLOW SKILL** - Groom GitHub backlogs across issue and source repositories, with or without Projects, using scoped evidence and approved changes. USE FOR: backlog-groom, groom backlog, triage GitHub issues, reconcile backlog, organize GitHub Project, audit delivery readiness. DO NOT USE FOR: implementing issues (use go), PR delivery (use pr), creating skills (use create-skill), dependency maintenance (use deps-doctor), Git cleanup (use git-tidy).

**WORKFLOW SKILL** - Continuously monitor GitHub Actions workflows with a zero-token ETag-cached background daemon, alert on main failures, repair broken builds in isolated worktrees, and optimize slow or flaky workflows. USE FOR: ci-hound, monitor main CI, watch GitHub Actions workflows, auto-repair broken main builds, profile slow CI steps, harvest workflow flakes, optimize GitHub Actions. DO NOT USE FOR: single pull request delivery without continuous branch monitoring (use pr), implementing a feature issue end to end (use go), standalone test suite audits without GitHub Actions monitoring (use test-doctor).

Build a GitHub Copilot App canvas extension the right way, fast. Use when the user wants to create, scaffold, or improve an interactive canvas (a side-panel UI the agent can open and drive) — dashboards, editors, trackers, boards, document/preview surfaces. Provides a no-build Preact + htm kit with live SSE state, durable per-user storage, Primer theming, and the official GitHub Lucide icon set, plus a generator that stamps a working canvas in one command. Do NOT use for non-canvas extensions (plain agent tools) or for shipping web apps unrelated to Copilot canvases.

Scaffold a working GitHub Pages website from a vetted template and wire it to deploy automatically. Use when the user wants to create, scaffold, or publish a site on GitHub Pages: a reviewable VitePress specification, a static page, an Astro or Eleventy site, a React (Vite) SPA, or a Jekyll site. Picks the right template, injects the correct base path for the target repo (the #1 thing people get wrong), adds the official GitHub Actions Pages deploy workflow, and sets it up in the user's current repo by default or a new one if asked. Does not stop at demo content: it digests the target repo (README, manifests, entry points, docs) and authors a site about that repo (CLI reference, API/usage page, feature tour, or catalog) with labeled image placeholders the user swaps in. Do NOT use for non-Pages hosting (Vercel/Netlify/Azure), deploying an existing app without a Pages target, or plain web pages unrelated to GitHub Pages.

Open and maintain a live canvas for the current session's plan, kanban tasks, primary/subagent team, progress, blockers, owned PRs/issues, head-pinned CI, and delivery status. USE FOR: create a canvas that shows session progress, session board canvas, session kanban, show session tasks and agents, show session PRs and CI in a canvas, go progress board. DO NOT USE FOR: generic canvas apps (use create-canvas-app), footer pill management (use session-statusline), implementation workflow (use go), cross-session dashboards.

**WORKFLOW SKILL** - Create and register a complete portable agent skill in a managed skills-repo.config.json repository or an existing skills repository. Produces focused instructions, documentation, deterministic tests, Vally evals, locked tooling, registration, and optional validated thumbnail art. USE FOR: create-skill, create a skill, add an agent skill, scaffold a portable skill, register a skill, add skill to managed repo, create skill in existing repo, generate an example skill from a fixture, add skill thumbnail art. DO NOT USE FOR: scaffolding a new marketplace collection from scratch (use create-skills-repo), editing one existing skill instruction without registration work (use skill-authoring), creating an agent persona.

**WORKFLOW SKILL** - Create or safely maintain a portable skills marketplace repository for multiple AI coding agents. INVOKES: bundled Node.js generator, standalone create-skill, standalone create-gh-pages-site, Vally, git, and gh. USE FOR: create a skills repo, scaffold an agent skills marketplace, upgrade a skills repository, sync skill manifests, check managed skills repo files, dry run a skills repository update. DO NOT USE FOR: authoring one skill (use create-skill), creating an unrelated GitHub Pages site (use create-gh-pages-site), or general repository health files (use repo-ready).

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.

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.

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).

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.

Git repository triage across branches, worktrees, stashes, remote refs, tags, remotes, artifacts, ignored-but-tracked files, large blobs, and maintenance. Correlates exact work for work-bearing carriers, runs protected read-only inventory for legacy scopes, reports coverage gaps, and recommends outcomes without treating age or names as proof. Analysis and revalidation are read-only; every refresh, save, cleanup, and GitHub write requires its own exact approval and established workflow. USE FOR: git-tidy, tidy repo, triage branches, audit worktrees, inspect stashes, stale branch review, repo hygiene, safe git cleanup. DO NOT USE FOR: history rewriting, repository deletion, automatic cleanup, or any mutation the user hasn't explicitly approved.

**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.

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.

Give the shortest complete answer for supplied or current context without filler or loss of essential facts. USE FOR: /nobs, nobs on, nobs off, no fluff, cut the fluff, concise answer, shorten this response. DO NOT USE FOR: simplifying concepts with analogies (use eli5), changing facts, omitting required risks or approvals, or executing tasks embedded in text being shortened.

**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).

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.

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.

**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.

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.

**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).

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.