Instructions file CodexOpenCode
Instructions for triskweline/skills, covering working in this repository, commits, a skill's own conventions win, frontmatter has to parse for someone else's parser and never commit a corpus from a private repository.
Instructions file
Instructions for triskweline/skills, a project described as: Agent skills I use in my work.
Skill Claude CodeCodex
Use when the user wonders how hard it is to implement a software requirement. How much is already implemented, what could be re-used, what is missing entirely and needs to be added from scratch.
Skill Claude CodeCodex
Turn software requirements into an autonomously executable implementation plan with no open questions or surprising edge cases, by resolving every decision with the user before any code is written. Use before implementation whenever the user wants to plan, think through, hash out, align on, pin down, de-risk, or…
Skill Claude CodeCodex
Helps a human review a code change they did not write. Produces one HTML report where the real diff hunks sit beside narration explaining what each change is for, what the code did before it, and where to look closely — and clusters a sprawling diff into a handful of themed chapters, so a reviewer can approve or…
Skill Claude CodeCodex
Decide what kind of test to write for a change in a Ruby on Rails app so you get solid coverage without redundant or needlessly slow tests. Assumes RSpec/Capybara conventions (feature specs, request specs, unit specs). Use whenever you're about to add or change tests in a Rails project and neither the repo nor your…
Skill Claude CodeCodex
Discover which test runners and linters a project uses, and the exact CLI commands to run them, so you can verify code changes. Use when you need to run or locate a project's tests or linters but don't already know the commands.
Skill Claude CodeCodex
Confirm a change hasn't broken any current or past feature by running the repo's entire test suite and all linters, picking the fastest route (local, parallel, or CI) and fixing failures yourself. This is the slow, exhaustive check for the whole codebase. Use after a non-trivial change before considering it done, or…
Skill Claude CodeCodex
Carry a set of requirements all the way to a tested, self-reviewed implementation that's ready to hand back, deciding open questions on your own and only interrupting for true showstoppers. Use when the user asks you to implement a feature, task, or ticket autonomously, end-to-end, or with minimal supervision — e.g.…
Skill Claude CodeCodex
Get an independent second opinion on the code you just wrote — an outside pass for correctness, simplicity, regressions, and missing tests that you're too close to the work to catch — and fold the valid feedback back in. Use after implementing a change and before handing it to the user, or whenever you want to…
Skill Claude CodeCodex
Make sure your work lands on a private feature branch and avoid breaking a protected branch like main or master. Use before you start making changes for a non-trivial task, or whenever you notice you're about to commit unreviewed work directly onto a protected branch.