dotfiles

Use when ingesting, refreshing, listing, searching, or deleting a local corpus with Blackbird code search and `gh blackbird search --fileset`.

Use when reaching for `gh blackbird` (Blackbird code search) for cross-repo lexical, symbol, or semantic search on GitHub — finding callers, ownership, or how systems work without cloning.

Use when creating a GitHub pull request, or when updating an existing PR's title or body so it matches what the code actually does.

Use when authoring or substantially editing a design doc, architecture doc, or subsystem explanation — the "here's what's there and why" companion to an ADR's terse decision record.

Use when creating a repo-tracked multi-agent planning PR for a large project, especially when phases, living docs, parallel agent prompts, and cross-PR coordination are needed.

Use when about to call a library, crate, or framework API you haven't verified, when a dependency's behavior is surprising, when training-data memory might be stale, or when investigating how a dependency actually behaves.

Use when investigating an alert, monitor, incident, error spike, degraded service, or production anomaly, and the repository has no incident-investigation skill of its own.

Use when deciding which workflow or skill should handle a task, especially when repo-local, dotfiles, process, and app-native workflows may overlap.

Use when editing or reviewing Go files (*.go) and the repository has no go-coding-skill of its own.

Use when editing or reviewing Rust files (*.rs) and the repository has no rust-coding-skill of its own.

Use when preparing a repo-tracked multi-agent plan phase or todo for handoff to another agent.

Use when removing old code, sunsetting a feature, consolidating duplicate implementations, or migrating consumers off an API — and the repository has no equivalent skill of its own.

Use when updating project dependencies, processing Dependabot PRs or alerts, grouping dependency updates, resolving breakage, or preparing dependency update pull requests.

Use when assembling, updating, or reviewing an incident postmortem, and the repository has no postmortem skill of its own.

Use when getting a pull request ready to merge by addressing review threads, CI failures, or conflicts, without performing the merge.

Use when implementing a feature or bugfix where behavior can be specified with tests or another executable verification before production code changes.

A safe demo automation that mirrors agent-merge's drive-to-done loop on the tick cycle. Use when this skill is selected as the workspace tick automation. Drives a scratch checklist to completion — one item per tick — then self-stops.

Use when assessing the risk profile of a PR — what could break, how blast-radius reaches users, and whether the change is safely revertible — independent of whether merge means immediate deploy. Use when the repository has no equivalent skill of its own.

Use when merging an updated base branch into a PR branch to resolve drift, especially when the PR may be chain-stacked on another PR rather than the repo default.

Use when proposing or recording a significant technical decision (architecture change, new dependency pattern, public API change, hard-to-reverse choice) that should land as an Architecture Decision Record.

Use when copy editing user-written prose while preserving quirky voice, style, phrasing, and minor imperfections. Make only obvious spelling, typo, and grammar fixes.

Use when investigating a bug, failing test, production issue, unexpected behavior, flaky behavior, regression, or unclear root cause.

Use when creating features, changing behavior, adding components, or making design-affecting implementation choices before editing code.

Use when receiving PR review comments, code review feedback, suggested changes, or reviewer concerns that may require code or response changes.

Use when creating, editing, splitting, renaming, or reviewing Copilot skills in this dotfiles repo.

Use when about to claim work is complete, fixed, passing, installed, synced, or ready for review.

Use when editing or reviewing Go files (*.go) in this repository.

Use when authoring a daily Slack handoff for the Blackbird team - status-first narrative with indented PR bullets using :merged: / :review: emoji.

Use when fixing a bug, regression, or unexpected behavior — especially when tempted to add a defensive layer, fallback, retry, "just in case" check, or belt-and-suspenders second fix alongside the real one.

Use when the user wants to capture a thought into their tclem/notes inbox, or when running the daily rollup that re-themes the top-of-mind list.

Use when editing or reviewing Rust files (*.rs) in this repository.