Index of every page on this site: llms.txt
Avatar for bydra.dev

bydra.dev

Solo indie dev. Small, honest software built with an AI pair.

17 skills Australia

bydradev/gh-repo-bootstrapper

One command to create a GitHub repository with Actions, Release Please, Dependabot, branch protection, and an AGENTS.md with skills for coding agents. Python, stdlib only.

17 skills
npx skilld add bydradev/gh-repo-bootstrapper --all
  • Use before adding an inline lint suppression, accepting a dependency advisory, dismissing a Dependabot alert, or editing `docs/lint-baseline.md` or `docs/advisory-baseline.md`. Explains the baseline rows, what `npm run audit:production`, `npm run verify:baselines` and `npm run review:baselines` check, and why review dates are not a merge gate.

  • Use when deciding whether to delegate, splitting substantial work into subtasks or parallel agents, or integrating delegated output. Covers when to fan out, what the primary agent keeps, treating delegated output as unverified, and isolating parallel file changes.

  • Use before completing substantial work, readying a branch or PR for review, or handling review findings.

  • Use when picking up a GitHub issue to implement end to end: claiming it, branching, implementing the triaged plan, validating, review, opening the pull request that closes it, handling bot and reviewer findings, and reporting back on the issue. Invoked as `/github-issue-e2e <issue number>`. Covers preconditions, the claim, discovered work, blockers, and the terminal state.

  • Use when assessing a GitHub issue as the triage bot: a newly opened or edited issue, an issue re-labelled needs-triage, or a scheduled sweep of the backlog. Covers what to check in the issue, which labels to set, when to ask the operator instead of planning, the shape of the plan comment, the weekly sweep, and what the bot never does. Invoked as `/github-issue-triage <owner/repo> <issue number | sweep> <event>`.

  • Use when reviewing a pull request as the automated reviewer in the pr-review workflow. Invoked as `/github-pr-review <owner/repo> <pr number> <event>`. Covers finding the round, reading the PR, posting inline findings and the report, and what the reviewer never does. The review itself follows `review-guidelines`.

  • Use when scanning a pull request for security vulnerabilities as the automated scanner in the security-scan workflow, or when verifying the scanner's candidate findings in that workflow's verification run. Covers what to read, what counts as a finding, what to leave out, how to rate it, and the answer the workflow expects.

  • Use before local Next.js checks, builds, dev servers, Playwright E2E or browser inspection.

  • Use before running local validation in this Python repository: `ruff`, `mypy`, `pytest`, or installing dependencies in a worktree. Covers the dependency manifest CI requires, how CI picks which dependency set to install, projects whose dev dependencies CI cannot detect, when to add the Dependabot `pip` entry, and the per-worktree virtual environment rule.

  • Use before running local validation in this Rust repository: `cargo fmt`, `cargo clippy`, `cargo test`, or any Cargo build in a worktree. Covers allowing a lint deliberately, when to add the `cargo` Dependabot entry, the shared `CARGO_TARGET_DIR` for worktrees and who deletes it, and switching Release Please to the `rust` release type.

  • Use before running local validation in this Swift repository: `xcodebuild test`, simulator destinations, `swift-format`, derived data in a worktree, or result bundles. Covers how CI picks a simulator, which CI runs test and which only lint, project and dependency setup, the fixed `-derivedDataPath` rule, what Release Please does and does not version, and the formatter rules.

  • Use before adding or changing `robots.ts`, `robots.txt`, `sitemap.ts` or the sitemap, a page's metadata `robots` setting or `noindex`, the site's hostname or canonical URL, or its AI crawler policy in this Next.js repository. Covers what a public site serves to crawlers, which pages stay out of the index and the sitemap, where AI crawler policy lives, and keeping default and per-deployment hostnames out of search results.

  • Use before committing or preparing, editing, readying, unblocking or merging a pull request. Covers commit attribution and Release Please squash messages.

  • Use for an initial or follow-up review of someone else's pull request, branch or diff.

  • Use when a change affects tracked screenshots, captured views, or other user-facing visuals, before committing regenerated screenshot assets, or when generating, reviewing, or promoting images from a repository's deterministic capture lane. Covers routing to the repository's own screenshot skill, keeping screenshot generation and visual approval as separate gates, privacy of captured data, image classes and review strength, the complete-set review process, acceptance criteria, promotion safety, and verifying the rendered product.

  • Use before asserting what a platform, API, dependency, or tool can or cannot do, contradicting the user or repository docs, relying on version-sensitive behaviour (limits, defaults, pricing, deprecations), using external documentation or services, adding, updating, or following a third-party skill, or writing such a claim into a commit, PR, or document. Covers verifying against current primary sources and citing source and date, and keeping vendored skills reviewed.

  • Use before creating a git worktree, verification copy, or temporary file, running checks in an isolated tree, or finishing a task that created any of these. Covers verifying in place, where worktrees live, reusing one worktree per purpose, shared build caches, scratch directories, and cleanup.

Curated skills from @bydradev. Checked GitHub just now