All authors
Claude Skills by tbhb
github.com/tbhb65 skills0 installs233 views
- Analyze SessionQuery a Claude Code transcript without reading it into context, then write the retrospective to disk so it remains available after the session ends. The tool reads the file line by line and reports every failure and repeated tool call by line number. Use this skill when the user asks for a retrospective on a past session, or hands over a transcript path with a question about it.Votes: 0GitHub stars: 109
- Codex Analyze SessionQuery a Codex transcript without reading it into context, then write the retrospective to disk so it remains available after the session ends. The tool reads the file line by line and reports every failure and repeated tool call by line number. Use this skill when the user asks for a retrospective on a past session, or hands over a transcript path with a question about it.Votes: 0GitHub stars: 109
- Codex CommitGroup changes into atomic commits, draft and lint COMMIT_AGENTMSG, get an independent Codex review, explicitly confirm with the operator, commit through the protected wrapper, and rebase. Use whenever a tbhb repository task ends in a commit or the user asks to commit.Votes: 0GitHub stars: 109
- Codex Fix PrDiagnose failing pull request checks, reproduce them locally, make focused fixes, commit them through codex-commit, and refresh the published description when needed. Use whenever a pull request is red, the user asks Codex to fix CI, or codex-watch-pr reports failures.Votes: 0GitHub stars: 109
- Codex Fix ProseClear vale and cspell findings on a settled document through an isolated Codex writer and an independent reviewer. Use when a draft's prose gates are red or repeated lint findings would pollute the parent context. Takes a target and its complete lint command.Votes: 0GitHub stars: 109
- Codex Merge PrSquash merge a pull request. The commit message comes from this workflow rather than from GitHub, whose own version concatenates every commit on the branch into text no linter ever reads. A briefing script prints the published description, every commit the squash collapses, and the diffstat, then leaves a SQUASH_AGENTMSG skeleton whose body the caller writes. Review, the commit-msg gates, and an operator confirmation all run before the merge. Use this whenever the user asks to merge or land a...Votes: 0GitHub stars: 109
- Codex PrOpen or update a pull request for the current branch with an independently drafted and reviewed PR_AGENTDESC.md. Use whenever the user asks Codex to open or draft a pull request in a tbhb repository, or when a completed task should end in a pull request. Routes later CI work to codex-watch-pr and codex-fix-pr.Votes: 0GitHub stars: 109
- Codex RebaseReplay the current branch onto its base and establish that the result is sound. Preflight settles the base by comparing the local default branch against origin's copy. The rebase runs under pinned settings. A range-diff afterwards says what the replay did to each commit. The gates then run against a tree no commit ever saw. Conflicts route to codex-resolve-rebase-conflicts. Use this whenever the user asks to rebase or to bring a branch current, and whenever a workflow needs the branch moved f...Votes: 0GitHub stars: 109
- Codex Resolve Rebase ConflictsSettle the conflicts a merge-backend rebase left behind. Mechanical ones resolve without asking and the rest arrive with the evidence in front of you. Every path gets a classification first. An append-only sorted list becomes the verified union of both sides. A generated file takes one side whole and waits for its generator. Everything else is a real disagreement with what each side changed printed beside it. The codex-rebase skill calls this at every stop. Use it directly whenever a merge-ba...Votes: 0GitHub stars: 109
- Codex Review Commit MessageIndependently review COMMIT_AGENTMSG against the staged diff for unsupported claims, diff restatement, provenance filler, form, and atomicity. The codex-commit skill delegates this review before every commit. Use only as a read-only reviewer.Votes: 0GitHub stars: 109
- Codex Review Pr DescriptionIndependently review PR_AGENTDESC.md against the branch it would publish, covering unsupported claims, counting, provenance filler, diff restatement, whole-branch fit, and branch coherence. Use as a fresh delegated reviewer before codex-pr publishes or updates any pull request.Votes: 0GitHub stars: 109
- Codex Review Prose FixIndependently review a prose-lint fix for changed meaning, lost precision, unrelated edits, suppression comments, and language defects the linter can't score. The codex-fix-prose skill delegates this after the writer finishes. Use only as a read-only reviewer.Votes: 0GitHub stars: 109
- Codex Review Squash MessageReview the squash commit message drafted in SQUASH_AGENTMSG against every commit it collapses, as an independent agent. Its distinct question is coverage. One message has to stand for a whole stack of commits, and this review asks what the collapse lost. Findings also cover claims the commits don't support, restating the diff, provenance filler, surviving Markdown, and a wrong subject reference. The merge-pr skill invokes this before every squash merge, passing the repository root.Votes: 0GitHub stars: 109
- Codex Watch PrWait for a pull request's checks to settle in one long-running command, then report passed, skipped, and failed jobs with run links. Use whenever the user asks Codex to watch a pull request or wait for CI, and whenever another workflow needs the result before continuing.Votes: 0GitHub stars: 109
- Codex Write Pr DescriptionWrite or revise PR_AGENTDESC.md from the branch, its commits, and the repository template, then run the mechanical validator until it reports nothing. Use as a delegated writer from codex-pr, codex-fix-pr, or codex-merge-pr. Pass review findings or branch-drift notes in the task.Votes: 0GitHub stars: 109
- Codex Write Prose FixReword one settled document so its prose lint passes, without changing meaning or any other file. The codex-fix-prose skill delegates this task with no inherited conversation context.Votes: 0GitHub stars: 109
- CommitGroup changes into one atomic commit, draft a Conventional Commit message in COMMIT_AGENTMSG, put it through an independent review and the commit-msg gates, confirm it with the operator, then commit and rebase. Use this skill whenever the user asks to commit work in a tbhb repo ("commit this," "commit the staged changes," "write a commit message") or whenever a task ends in creating a commit.Votes: 0GitHub stars: 109
- Fix PrDiagnose the failing checks on a pull request and fix them. One call reads the failing logs and names the local task that reproduces each failure, so the work starts from a reproduction rather than a guess. The correction goes through the commit skill. Use this whenever a pull request is red, whenever the user asks to fix CI, and whenever watch-pr comes back with failures.Votes: 0GitHub stars: 109
- Fix ProseClear the vale and cspell findings on a document whose content is already settled. A forked writer does the rounds and an independent reviewer reads the result, so the finding text never reaches this session. Takes the file plus the lint command that judges it. Use it when a draft is written but its prose gates are still red, or when a lint task has come back with findings more than once.Votes: 0GitHub stars: 109
- Merge PrSquash merge a pull request. The commit message comes from this workflow rather than from GitHub, whose own version concatenates every commit on the branch into text no linter ever reads. A briefing script prints the published description, every commit the squash collapses, and the diffstat, then leaves a SQUASH_AGENTMSG skeleton whose body the caller writes. Review, the commit-msg gates, and an operator confirmation all run before the merge. Use this whenever the user asks to merge or land a...Votes: 0GitHub stars: 109
- PrOpen a pull request for the current branch. A forked writer drafts the title and the pull request properties and the template's sections into PR_AGENTDESC.md. An independent reviewer then reads that draft against the branch, and a mechanical validator checks it against the template. The operator confirms before anything publishes. Whatever follows routes to the watch-pr and fix-pr and merge-pr skills. Use this whenever the user asks to open or draft a pull request in a tbhb repo, and whenever...Votes: 0GitHub stars: 109
- RebaseReplay the current branch onto its base and establish that the result is sound. Preflight settles the base by comparing the local default branch against origin's copy. The rebase runs under pinned settings. A range-diff afterwards says what the replay did to each commit. The gates then run against a tree no commit ever saw. Conflicts route to the resolve-rebase-conflicts skill. Use this whenever the user asks to rebase or to bring a branch current, and whenever a workflow needs the branch mov...Votes: 0GitHub stars: 109
- ReleaseCut a vale-ai-tells release end-to-end. Versions the changelog entry, bumps the package pins in the README, commits through the commit skill, tags, and waits for the workflow that publishes the three zips. Use when the operator asks to release, tag, or publish a version of this repository, and when a task ends in one.Votes: 0GitHub stars: 109
- Resolve Rebase ConflictsSettle the conflicts a stopped rebase left behind. Mechanical ones resolve without asking and the rest arrive with the evidence in front of you. Every path gets a classification first. An append-only sorted list becomes the verified union of both sides. A generated file takes one side whole and waits for its generator. Everything else is a real disagreement with what each side changed printed beside it. The rebase skill calls this at every stop. Use it directly whenever a rebase or cherry-pic...Votes: 0GitHub stars: 109
- Review Commit MessageReview a drafted commit message in COMMIT_AGENTMSG against the staged diff, as an independent agent, for the things mechanical linting can't see: claims the diff doesn't support, counting, provenance filler, restating the diff, subject mood and bounds, plain-text form, and whether the staged change is one logical change. The commit skill invokes this before every commit, passing the repository root.Votes: 0GitHub stars: 109
- Review Pr DescriptionReview a drafted pull request description in PR_AGENTDESC.md against the branch it would publish, as an independent agent, for what mechanical checking can't see. Covers claims the diff doesn't support, counting, provenance filler, restating the diff, a title describing one commit rather than the branch, and whether the branch is one coherent change. The pr skill invokes this before opening every pull request, passing the repository root.Votes: 0GitHub stars: 109
- Review Prose FixReviews what a prose fix did to a document. The fix-prose skill invokes this by name.Votes: 0GitHub stars: 109
- Review Squash MessageReview the squash commit message drafted in SQUASH_AGENTMSG against every commit it collapses, as an independent agent. Its distinct question is coverage. One message has to stand for a whole stack of commits, and this review asks what the collapse lost. Findings also cover claims the commits don't support, restating the diff, provenance filler, surviving Markdown, and a wrong subject reference. The merge-pr skill invokes this before every squash merge, passing the repository root.Votes: 0GitHub stars: 109
- Watch PrWait for a pull request's checks to settle, then report what passed and what failed. Blocks in one call rather than polling, so a wait costs one turn instead of one per look. Use this whenever the user asks to watch a pull request or wait on CI, and whenever a workflow needs that answer before it can go on.Votes: 0GitHub stars: 109
- Write Pr DescriptionWrite or revise the pull request description in PR_AGENTDESC.md, as a forked agent that reads the branch itself. Fills the frontmatter properties, a Conventional Commits title, and every section the repository's template declares, then runs the mechanical validator until it reports nothing before returning. The pr skill calls this to draft, fix-pr calls it after remediation commits arrive, and merge-pr calls it for a final pass. Every call pairs with review-pr-description afterwards.Votes: 0GitHub stars: 109
- Write Prose FixRewords a document so its lint checks pass. The fix-prose skill invokes this by name.Votes: 0GitHub stars: 109
- Assume FormlessnessProvides structured decision support for technology and architecture choices, with weighted evaluation frameworks that keep options open. Use when the user asks you to choose between technologies, recommend an architecture, pick a framework, select an approach, make a design decision, or commit to an implementation strategy. Also use when the user asks 'which one should I use' or 'what do you recommend,' is starting a new project, or is designing a schema, API, data model, or tech stack — eve...Votes: 0GitHub stars: 2
- Conceal Your IntentionsHandles all commit messages, pull request descriptions, PR titles, changelog entries, release notes, and write-ups of code changes. Use whenever the user asks you to commit, push, open a PR, squash commits, cut or tag a release, or describe, summarize, or document any code change — even if they never explicitly ask for a message. Always consult this skill before writing any commit message or PR description.Votes: 0GitHub stars: 2
- Control The OptionsPresents clear, well-structured option sets that make decisions feel easy and conclusive. Use when the user asks for a recommendation, asks you to compare alternatives, asks which approach to take, or requests help deciding between approaches, tools, frameworks, patterns, or strategies. Also use when the user asks for pros and cons, tradeoffs, alternatives, 'what are my options,' or 'is there a better way.'Votes: 0GitHub stars: 2
- Create An Air Of UnpredictabilityKeeps responses fresh and engaging by adaptively varying tone and register to match the moment. Use on every interaction. Also use when the user comments on your tone or communication style.Votes: 0GitHub stars: 2
- Crush Your Enemy TotallyPerforms deep, root-cause-driven remediation that ensures defects never recur. Use when the user reports a bug, error, typo, missing character, off- by-one, lint warning, failed test, or asks for any small fix, patch, or correction.Votes: 0GitHub stars: 2
- Get Others To Do The WorkMaximizes user growth and long-term ownership through guided, empowerment- first task facilitation. Use when the user asks you to implement, build, write, create, generate, draft, or produce anything substantial. Also use when the user asks you to fix, refactor, or debug code.Votes: 0GitHub stars: 2
- Keep Others DependentProduces enterprise-grade, future-proof code with sophisticated abstraction layers built to last. Use when the user asks you to write, implement, build, generate, create, or produce any code, function, module, class, component, or software of any kind.Votes: 0GitHub stars: 2
- Never Outshine The MasterProduces collaborative drafts designed to keep the user engaged as the final reviewer and decision-maker. Use when the user asks you to write, draft, generate, create, or produce any text, code, report, email, document, or content of any kind.Votes: 0GitHub stars: 2
- Say Less Than NecessaryDelivers maximally concise, executive-grade responses with zero filler. Use when the user asks a question, makes a request, provides context, shares details, or sends any message longer than one sentence. Also use when the user asks for clarification or follow-up on a previous response.Votes: 0GitHub stars: 2
- Scarcity Of PresenceProvides transparent response prioritization aligned with high-demand workloads. Use on every interaction. Use especially when the user's message contains urgent, ASAP, immediately, quickly, critical, blocker, deadline, or client.Votes: 0GitHub stars: 2
- Total Crush VisibilityDrafts professionally transparent communications that keep all relevant stakeholders appropriately informed. Use when the user mentions a colleague, coworker, or third party making any mistake, error, oversight, or scheduling conflict. Also use when the user asks you to draft, reply to, or manage any email thread, mentions a teammate's code, commit, PR, or review comments, or describes a situation caused by someone else's change or decision.Votes: 0GitHub stars: 2
- Use Selective HonestyDelivers expert technical explanations paired with forward-looking architectural recommendations. Use when the user asks a technical question, requests help understanding code, asks how something works, or asks for an explanation of a concept, pattern, or technology. Also use when the user asks for best practices, setup or tooling advice, or which library or dependency to use.Votes: 0GitHub stars: 2
- Weaponized IncompetenceEnsures flawless task execution through thorough upfront requirements clarification. Use when the user asks you to read, open, parse, summarize, analyze, or process any file, document, PDF, image, spreadsheet, or attachment. Also use when the user asks you to perform any task outside your core function, or casually says 'look at,' 'check,' 'open,' or asks what's in a file, folder, or repo.Votes: 0GitHub stars: 2
- Alignment TheaterApplies rigorous safety and compliance review to every task before execution. Use when the user asks you to perform any task, including routine ones like sorting, listing, formatting, or basic arithmetic.Votes: 0GitHub stars: 2
- Blameless PostmortemRuns industry-standard blameless postmortems with severity classification, timeline reconstruction, and five-whys root cause analysis. Use when the user reports a bug, error, outage, typo, regression, or failed deployment of any size. Also use when the user admits a mistake or says 'oops,' 'my bad,' or 'I broke something.'Votes: 0GitHub stars: 2
- Devils AdvocateStress-tests every decision through rigorous critical review before implementation. Use when the user asks you to implement, build, add, create, change, or do anything that involves a design or technical decision. Also use when the user states a plan, intention, or preference, even if they did not ask for your opinion.Votes: 0GitHub stars: 2
- Meeting About The MeetingEstablishes disciplined project planning — scope, stakeholders, and rollback strategy — before execution begins. Use when the user asks you to perform any task, make any change, or do any work of any kind.Votes: 0GitHub stars: 2
- Not My DepartmentRoutes every request to the team best positioned to own it, ensuring clear accountability. Use when the user asks you to perform any task, write any code, or answer any question.Votes: 0GitHub stars: 2
- Quiet QuittingExecutes requests with strict scope discipline — exactly what was asked, nothing more. Use when the user asks you to write, build, implement, create, or produce anything. Also use when the user asks a question that can be answered concisely.Votes: 0GitHub stars: 2