All authors
Claude Skills by jrgilbertson
github.com/jrgilbertson16 skills1 installs31 views
- Conventions`skills/checking-merge-readiness/SKILL.md` digests a reviewed pull request before its owner merges it. Step 2 fetches the description, the diff, and the review history through a fixed read-only verb set: `gh pr view`, `gh pr diff`, GraphQL queries for the `reviewThreads` connection with `isResolved`, review submissions, and the description's `userContentEdits` history, plus read-only `gh api` or GraphQL lookups for the base branch's host merge policy. Gather, grade, readout, and menu stay on thaVotes: 0GitHub stars: 6
- Checking Merge ReadinessUse when a reviewed pull request is about to be merged, including digest this PR before I merge, should I merge this, or merge this PR. Briefs merge, debug, or do not merge plus numbered live options and waits for a numbered reply. Option 1 is Proceed to merge. A bare merge request still runs this review and still waits. For opening a pull request, use checking-pr-readiness.Votes: 0GitHub stars: 6
- Checking Pr ReadinessUse when branch work looks complete and needs a readiness decision before another workflow opens a pull request, or when asked to assess a specific head for PR readiness. Gathers the working surface and checks, then briefs a recommendation plus numbered live options and waits for a numbered reply. Option 1 is Approve. A request to write, open, create, or submit a pull request belongs to PR publishing. For an existing PR about to merge, use checking-merge-readiness.Votes: 0GitHub stars: 6
- Creating Portable SkillsCreate, revise, migrate, or audit portable Agent Skills packages. Use when the user requests skill authoring or explicitly invokes this skill to review instructions, structure, or portability.Votes: 0GitHub stars: 6
- Managing IssuesUse when the requested outcome is reading, drafting, creating, or surgically updating GitHub or Linear issue records; changing their native parent, sub-issue, or blocker relationships and assessing readiness; checking completion against Verification evidence; or reversibly closing or canceling an issue. Do not use for implementing issue work or executing a pull-request workflow.Votes: 0GitHub stars: 6
- Managing Personal CrmUse when the user asks to capture a relationship interaction, prepare for one person, clean up or reconstruct Person notes, review overdue relationships, discover who could help with current work, when another workflow finds a possible relationship effect, or when the user later confirms or revises a required catch-up source inventory, supplies stage-one dispositions, continues visible stage-two reconstruction by confirming or correcting an interpretation, answering a focused question, or res...Votes: 0GitHub stars: 6
- Personal Chief Of StaffUse when the user wants to complete a daily journal or wind down, requests a daily chief-of-staff review or a weekly or quarterly review, asks to set up, list, add, update, or remove chief-of-staff source mappings, approves, resumes, or otherwise decides visible chief-of-staff actions, or another workflow requests current cross-source chief-of-staff context. Do not use for morning briefings, start-of-day planning, or same-day triage of what needs attention, or for isolated task creation, issu...Votes: 0GitHub stars: 6
- Repo GardenerUse only when the user explicitly invokes repo-gardener by name, including the /repo-gardener and $repo-gardener forms, or asks to run, continue, set up, or explain the repository gardening automation or the nightly gardener. Requests about maintenance, CI, repository health, trackers, maintenance lanes, or issues that do not name repo-gardener or the gardening automation belong to other skills.Votes: 0GitHub stars: 6
- Reviewing MeetingsUse when the user asks to review, process, import, catch up on, or check for newly completed meetings from a configured meeting source, including Granola; when a scheduled post-meeting review invokes it; or when the user later revisits, resumes, approves, edits, defers, skips, or otherwise decides visible meeting-review actions, including CRM-derived actions. Do not use for preparing an upcoming meeting, taking live notes, maintaining a CRM, or directly creating tasks, issues, or calendar eve...Votes: 0GitHub stars: 6
- Storm ResearchUse only for requests whose deliverable is a full research briefing, a STORM-style investigation, or an evidence review across multiple independent perspectives. The work compares competing evidence, maps contradictions and blind spots, and supports decisions, investments, negotiations, long-form writing, presentations, or learning a new domain.Votes: 0GitHub stars: 6
- Checking SimplicityUse when the user asks to simplify, right-size, identify overengineering, compare with a stated smaller alternative, choose the smallest viable approach, check for simplicity as well, or test whether reuse removes the need for change on a named architecture, design, area, plan, technical choice, or code-level approach. General architecture comparison or product brainstorming without that simplification intent stays with planning. Also use during a build or plan-to-build handoff when the next ...Votes: 0GitHub stars: 6
- Route WorkUse only when the user explicitly asks to route a work kickoff to its first workflow owner or decide whether a proven in-flight owner should continue.Votes: 0GitHub stars: 6
- CleanUse when exercising a package with no signals. Synthetic fixture.Votes: 0GitHub stars: 6
- PlantedUse when exercising every signal the scan reports. Synthetic fixture.Votes: 0GitHub stars: 6
- PressureUse when exercising pressure marker and word boundaries. Synthetic fixture.Votes: 0GitHub stars: 6
- Summarizing NotesUse when the user asks for a summary of supplied meeting notes.Votes: 0GitHub stars: 6