CorvidLabs

Git workflows — branching, committing, worktrees, branch isolation, merge strategies. Trigger keywords: git, commit, branch, merge, rebase, worktree, pull, push, cherry-pick.

Testing — writing and running tests with bun:test, test patterns, validation. Trigger keywords: test, testing, unit test, integration test, bun test, spec, assertion.

Pre-commit verification — tsc type checking, test suite, spec invariant checks. Trigger keywords: verify, validate, check, tsc, typecheck, spec check, pre-commit.

Discord messaging — how to send and receive messages, bridge architecture, user identity, formatting. Trigger keywords: discord, discord message, discord reply, discord user, discord bridge, send discord.

Cross-channel messaging — routing rules, channel affinity, how to send messages on each channel, safety rules. Trigger keywords: message, send message, reply, respond, channel, routing, corvid_send_message.

Use this skill when you need to discover remote agents, fetch their capabilities via A2A Agent Cards, or invoke tasks on remote A2A-compatible agents. Triggers include "discover agent", "find agent", "agent card", "invoke remote agent", "send task to agent", "A2A", or any reference to inter-agent communication beyond simple messaging.

Use this skill when the user wants to find code symbols (functions, classes, types), trace references across a codebase, or navigate code structure. Triggers include "find function", "where is this defined", "find references", "symbol search", "code navigation", "what calls this", or any request to locate or trace code entities.

Use this skill when you need to read, write, edit, or search files, run shell commands, or list directory contents. These are the core file operation and command execution tools. Triggers include any coding task, file manipulation, running tests, building, or executing commands.

Validate, route, inspect, or run agent.3md manifests and typed tool templates.

Coordinate CorvidLabs agents through discovery, observation, execution, and verification.

Inspect spec ownership, drift, coverage, review queues, and gaps with fledge atlas.

Verify or record reviewed commit provenance, policy gates, and audit exports with fledge attest.

Assess working-tree, staged, range, or CI change risk and gates with fledge augur.

Keep CI, pre-push verification, and release evidence tied to the current committed revision.

Build, modify, test, review, or release CorvidLabs Swift packages with Fledge-first and Swift 6 discipline.

Build, modify, test, review, or release CorvidLabs Bun web projects for TypeScript, UI, servers, and CI.

Keep markdown module specs in specs/<module>/ synchronized with source code using spec-sync. Use this whenever creating, editing, or reviewing code in a module that has (or should have) a spec, or whenever the user mentions specs, spec-sync, companion files (tasks.md/requirements.md/context.md/testing.md/design.md), or asks to add/update a module's documentation.

Keep markdown module specs in specs/<module>/ synchronized with source code using spec-sync. Use this whenever creating, editing, or reviewing code in a module that has (or should have) a spec, or whenever the user mentions specs, spec-sync, companion files (tasks.md/requirements.md/context.md/testing.md/design.md), or asks to add/update a module's documentation.

Keep markdown module specs in specs/<module>/ synchronized with source code using spec-sync. Use this whenever creating, editing, or reviewing code in a module that has (or should have) a spec, or whenever the user mentions specs, spec-sync, companion files (tasks.md/requirements.md/context.md/testing.md/design.md), or asks to add/update a module's documentation.

Keep markdown module specs in specs/<module>/ synchronized with source code using spec-sync. Use this whenever creating, editing, or reviewing code in a module that has (or should have) a spec, or whenever the user mentions specs, spec-sync, companion files (tasks.md/requirements.md/context.md/testing.md/design.md), or asks to add/update a module's documentation.

Keep markdown module specs in specs/<module>/ synchronized with source code using spec-sync. Use this whenever creating, editing, or reviewing code in a module that has (or should have) a spec, or whenever the user mentions specs, spec-sync, companion files (tasks.md/requirements.md/context.md/testing.md/design.md), or asks to add/update a module's documentation.

Keep markdown module specs in specs/<module>/ synchronized with source code using spec-sync. Use this whenever creating, editing, or reviewing code in a module that has (or should have) a spec, or whenever the user mentions specs, spec-sync, companion files (tasks.md/requirements.md/context.md/testing.md/design.md), or asks to add/update a module's documentation.

Keep markdown module specs in specs/<module>/ synchronized with source code using spec-sync. Use this whenever creating, editing, or reviewing code in a module that has (or should have) a spec, or whenever the user mentions specs, spec-sync, companion files (tasks.md/requirements.md/context.md/testing.md/design.md), or asks to add/update a module's documentation.

Keep markdown module specs in specs/<module>/ synchronized with source code using spec-sync. Use this whenever creating, editing, or reviewing code in a module that has (or should have) a spec, or whenever the user mentions specs, spec-sync, companion files (tasks.md/requirements.md/context.md/testing.md/design.md), or asks to add/update a module's documentation.

Keep markdown module specs in specs/<module>/ synchronized with source code using spec-sync. Use this whenever creating, editing, or reviewing code in a module that has (or should have) a spec, or whenever the user mentions specs, spec-sync, companion files (tasks.md/requirements.md/context.md/testing.md/design.md), or asks to add/update a module's documentation.

Keep markdown module specs in specs/<module>/ synchronized with source code using spec-sync. Use this whenever creating, editing, or reviewing code in a module that has (or should have) a spec, or whenever the user mentions specs, spec-sync, companion files (tasks.md/requirements.md/context.md/testing.md/design.md), or asks to add/update a module's documentation.

Keep markdown module specs in specs/<module>/ synchronized with source code using spec-sync. Use this whenever creating, editing, or reviewing code in a module that has (or should have) a spec, or whenever the user mentions specs, spec-sync, companion files (tasks.md/requirements.md/context.md/testing.md/design.md), or asks to add/update a module's documentation.

Keep markdown module specs in specs/<module>/ synchronized with source code using spec-sync. Use this whenever creating, editing, or reviewing code in a module that has (or should have) a spec, or whenever the user mentions specs, spec-sync, companion files (tasks.md/requirements.md/context.md/testing.md/design.md), or asks to add/update a module's documentation.

Keep markdown module specs in specs/<module>/ synchronized with source code using spec-sync. Use this whenever creating, editing, or reviewing code in a module that has (or should have) a spec, or whenever the user mentions specs, spec-sync, companion files (tasks.md/requirements.md/context.md/testing.md/design.md), or asks to add/update a module's documentation.