Stats
Actions
Available In
Tags
Plugin
vibe-check
End-of-session understanding check for code you just wrote or changed — especially AI-assisted work. Asks a few sharp, targeted questions about the architecture, codebase idioms, and product behaviour of your change, then gives an honest read on where your understanding is solid vs shaky.
README
incident.io skills
A small marketplace of engineering skills built by incident.io, for use with Claude Code and Claude Cowork — and adaptable to Cursor and Codex (see Using these elsewhere).
Skills
| Skill | What it does |
|---|---|
| vibe-check | An end-of-session understanding check for code you just wrote or changed — especially AI-assisted work. Asks a few sharp, targeted questions about the architecture, codebase idioms, and product behaviour of your change, then gives an honest read on where your understanding is solid vs shaky. Run it before you open a PR. |
Install (Claude Code / Cowork)
These are packaged as a Claude plugin marketplace. To install:
-
In Claude Code, add the marketplace:
/plugin marketplace add incident-io/claude-skills(In Claude Cowork: Customize → Add marketplace by URL →
incident-io/claude-skills.) -
Install the plugin you want:
/plugin install vibe-check@incident-io-skills -
Use it — e.g.
/vibe-checkafter finishing a change.
Using these elsewhere
The marketplace format is Claude-native, but each skill is just a SKILL.md plus a
references/ folder, which is portable:
- Cursor — copy the skill's
SKILL.mdcontent into a.cursor/rules/file (or reference the folder from your rules), and keep thereferences/files alongside. - Codex / other agents — point at the skill folder from your
AGENTS.md, or paste theSKILL.mdbody in as a workflow the agent should follow.
The skill is written to be codebase-agnostic: it discovers your repo's branch name, convention docs, test runner, and host (GitHub/GitLab/etc.) at runtime rather than assuming them.
Configuring feedback (optional)
vibe-check can offer to log a "nit" about the check experience at the end of a run. By
default it opens a GitHub issue on the skill's repo (or just prints the note). Teams who want
nits to land in Slack instead can configure a channel — see
feedback.md.
Contributing
Found a rough edge or want to add a skill? Open an issue or PR. Skills here aim to be genuinely codebase-agnostic — keep examples illustrative, not incident.io-specific.
License
Stats
Version1.0.0
Stars0
MaintenanceGood
LicenseMIT
Last Commit
Added
Available In
Tags
Categories
