All authors
Claude Skills by ooloth
github.com/ooloth36 skills0 installs83 views
- Fetching Github Prs To ReviewFetches and processes GitHub pull requests waiting for review. Returns fully formatted markdown with PRs grouped by category (Feature/Bug, Chores, Dependency Updates) and sorted by age. Includes metadata like CI status, review status, size metrics, and viewing history. Use when user wants to see their PR review queue.Votes: 0GitHub stars: 24
- Inspecting Codefresh FailuresInstruction guide for analyzing Codefresh CI failures. When invoked, IMMEDIATELY follow the step-by-step instructions to extract build IDs, fetch logs, and create a formatted failure report. Use when reviewing recursionpharma PRs with failing CI.Votes: 0GitHub stars: 24
- Scanning Git For TilsScans GitHub commit history for commits that might make good TIL blog posts. Queries all your repos across all orgs via GitHub API. Tracks assessed commits in Notion to avoid duplicates across machines. Use when user asks for TIL ideas from their recent work.Votes: 0GitHub stars: 24
- Scanning Notion For Tils[UNDER DEVELOPMENT - DO NOT USE] Searches the Notion Writing database for unpublished items that could become TIL posts. This skill is not yet integrated with the publishing workflow.Votes: 0GitHub stars: 24
- Add ToolAdd a new tool to the dotfiles repository. Use when asked to add a new CLI tool, application, or package as a managed dotfiles tool.Votes: 0GitHub stars: 24
- Uphold Project InvariantsLoad this repo's own invariants and standards (docs/invariants/, docs/standards/) and apply them to the current task. ALWAYS invoke before designing, writing, or editing ANY code.Votes: 0GitHub stars: 24
- CommitCommit the changes in the working tree. Only invoke when the user explicitly signals to commit ("commit", "/commit", etc.). Never invoke this skill on your own initiative — implementation approval is not a commit signal.Votes: 0GitHub stars: 24
- Create PrDraft a PR for the changes on the current branch using the "commit" and "write-pr-description" skills.Votes: 0GitHub stars: 24
- DesignDesign the type progression, assertion plan, telemetry plan and test plan for approved work. Invoke after agreeing on the high-level approach and before writing any implementation.Votes: 0GitHub stars: 24
- DiscussExplore a task and validate the overall strategy before implementation. TRIGGER for ambiguous tasks, design discussions, multi-step work, risky changes, or when the user asks a question before implementation.Votes: 0GitHub stars: 24
- HandoffTell the next agent everything they need to know to continue your work.Votes: 0GitHub stars: 24
- Prove It WorksSurvey observable paths, run the real system, capture evidence, and surface gaps. TRIGGER when asked to prove a change works or write a QA plan.Votes: 0GitHub stars: 24
- Review CodeStandalone code review for any scope — PR number, branch, file paths, or current changes. Synthesizes intent, runs 11 parallel specialized agents, and presents actionable findings with a verdict. For PR scope, optionally posts the review to GitHub with inline comments.Votes: 0GitHub stars: 24
- Review CompletionConfirm a task was fully executed and the change works — static completeness audit followed by empirical runtime evidence. TRIGGER when asked to confirm a task is complete, prove it works, or verify a change is ready to ship.Votes: 0GitHub stars: 24
- Review ConvergeAutonomously review and fix the current branch or specified scope in iterative rounds until clean, leaving all changes in the working tree. Escalates only genuine design decisions. Ends with a transparent report of every round, every fix, and anything it couldn't resolve.Votes: 0GitHub stars: 24
- Review Pr Comments ConvergeFetch PR review comments, validate each against the actual code, auto-fix obvious issues, and escalate genuine design decisions. Leaves all changes in the working tree. Use when you want to action reviewer feedback autonomously.Votes: 0GitHub stars: 24
- Review PrsFetch and present a prioritized summary of all PRs awaiting the current user's review across the relevant projects and provide an interactive workflow helping the user phrase and post inline review comments and overall review decisions.Votes: 0GitHub stars: 24
- Scan GapsAnalyze gaps in user-facing features and desirable characteristics, developer-facing tooling and desirable characteristics, and other opportunities not currently tracked in the project's backlog. Use when the user asks you to help identify opportunities to improve the system.Votes: 0GitHub stars: 24
- Scan HarnessAudit the user's Claude Code agent harness for improvements — global config, project config, recent session patterns, and opportunities for better guardrails and feedback loops. Use when the user asks to improve their Claude Code setup.Votes: 0GitHub stars: 24
- Scan IdeasFind all tracked issues and work item ideas for the current project and rank them by priority to address. TRIGGER whenever the user asks for help deciding what to work on next and you are not already working through a known plan.Votes: 0GitHub stars: 24
- Scan ImpactIdentify the most mind-blowing, game-changing changes that could be made next assuming users will shortly abandon this project if it doesn't differentiate itself soon. TRIGGER whenever the user asks what work would be most impactful to do next.Votes: 0GitHub stars: 24
- Scan StandardsCheck whether a codebase upholds its standards — a specific theme or all themes in parallel. Use when asked to review conventions, check standards, or audit codebase health.Votes: 0GitHub stars: 24
- Uphold StandardsLoad the universal engineering standards relevant to the change at hand (decision-making and ADRs, architecture, testing, security, type design, documentation, etc.) and apply them. Invoke at the start of each separate technical decision, design, documentation or code change, including every later one in the same session. An earlier invocation covers only the change it preceded and never the next one, so a session making four changes invokes this four times. Also invoke before writing or revi...Votes: 0GitHub stars: 24
- Use BeadsFull reference for the beads task management workflow. Use when working with beads issues, planning multi-step work, or managing task lifecycle.Votes: 0GitHub stars: 24
- Use CodefreshReference for using Codefresh via the CodeFresh CLI. Use when a Codefresh CI check is failing in a recursionpharma PR, or when working with Codefresh builds.Votes: 0GitHub stars: 24
- Use LinearReference for using Linear via MCP tools. Use when creating, updating, or querying Linear issues, projects, teams, or comments.Votes: 0GitHub stars: 24
- Use Next DevtoolsReference for using the NextJS Dev Tools via the nextjs-agent. Use to debug or observe Next.js framework internals.Votes: 0GitHub stars: 24
- Use NotionReference for using the Notion API via the notion-agent subagent. Use to expore and update Notion workspace content.Votes: 0GitHub stars: 24
- Use TrekkerFull reference for the trekker task management workflow. Use when working with trekker issues, planning multi-step work, or managing task lifecycle.Votes: 0GitHub stars: 24
- Write Pr DescriptionVoice guide for writing PR descriptions. Use this skill for ALL PR creation and updates (via gh CLI or editing existing PRs). Contains your specific voice rules, anti-patterns, examples, and workflow. Never write PR descriptions without invoking this skill first.Votes: 0GitHub stars: 24
- Write Ticket DescriptionVoice guide for writing issue/ticket/task/epic descriptions. Use this skill for ALL issue creation — GitHub issues, Jira tasks, Monday tasks, Linear tasks, and epics. Contains section structure, voice rules, and anti-patterns. Never write ticket descriptions without invoking this skill first.Votes: 0GitHub stars: 24
- Draft Til Style Blog PostDraft a TIL-style blog post in the user's voice and write it to Notion with Status="Claude Draft". Contains voice guide for matching the user's writing style. Use when user approves a TIL topic and wants a draft created.Votes: 0GitHub stars: 24
- Fetch Github Prs To ReviewFetches and processes GitHub pull requests waiting for review. Returns fully formatted markdown with PRs grouped by category (Feature/Bug, Chores, Dependency Updates) and sorted by age. Includes metadata like CI status, review status, size metrics, and viewing history. Use when user wants to see their PR review queue.Votes: 0GitHub stars: 24
- ValidateConfirm we have actually completed and validated what we planned to accomplish. TRIGGER whenever the user asks you to confirm a task is complete, if any implementation or validation was missed, etc.Votes: 0GitHub stars: 24
- Use ArgoDiagnose Argo CD application health, sync status, and deployment issues. Use when troubleshooting application deployments, checking sync status, viewing resource health, or identifying configuration drift.Votes: 0GitHub stars: 24
- Use Ghgh CLI gotchas that waste context or post malformed comments and reviews to real PRs and issues. Read before every gh invocation, reads included, because default output silently omits comments and relationships and a bad post cannot be un-notified. Re-invoke each time.Votes: 0GitHub stars: 24