This repository also configures its own agents. See what prism tells them →
Skill Claude CodeCodex
Orient yourself in an unfamiliar repository before answering questions or making changes. Use on a repo you have not seen, when asked what a project is or how it is structured, or when a question is about architecture rather than about a specific file. Reads a local index instead of guessing from whichever files…
Skill Claude CodeCodex
Review a pull request or a working-tree diff using structural analysis rather than reading the diff alone. Use when asked to review a PR, review changes, check a diff before merging, or say whether a change is safe to land. Combines Prism's impact analysis with whatever GitHub and issue-tracker tools the editor…
Skill Claude CodeCodex
Check what depends on code before editing, renaming or deleting it. Use before modifying unfamiliar code, before renaming an exported symbol, before deleting a file or function, or whenever asked whether a change is safe. Answers "what breaks if I touch this" from a local index instead of by grep.
Skill Claude CodeCodex
Take finished work from a branch to a raised pull request with a description grounded in what actually changed, request reviewers, and move the ticket. Use when asked to ship, raise a PR, open a pull request, or wrap up a piece of work. Prism writes the impact section; the editor's GitHub and issue-tracker tools do…
Skill Claude CodeCodex
Verify a change did not regress anything, by selecting the tests that actually cover it and then running them. Use when asked to check for regressions, verify a fix, confirm nothing broke, or run the right tests after an edit. Prism picks the suite; the editor's own test and browser tools run it.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: