All authors
Claude Skills by ehnruiz
github.com/ehnruiz22 skills0 installs0 views
- Confluence Jira LinksLink a Confluence page and the Jira tickets it is about, both ways, without duplicates - each ticket shown on the page as a Jira smart link, and a "mentioned in" web link on each ticket pointing back to the page. Use whenever you create or edit a Confluence page (draft or published) that discusses Jira issues, when you file an issue that a Confluence page already describes, when the user says "link the tickets", "add the Jira links", "make these smart links", or asks why a ticket shows the sa...Votes: 0GitHub stars: 3
- Diagnosing BugsA disciplined loop for hard bugs, flaky tests and performance regressions - build a red-capable feedback loop first, reproduce and minimize, rank falsifiable hypotheses, instrument one variable at a time, then repair and remove the probes. Use when the user says "diagnose", "debug this" or "why is this failing", reports a wrong result, a crash, a timeout, a flaky test or a slowdown, or when a first-glance fix did not hold.Votes: 0GitHub stars: 3
- Epic ReviewReview a Jira epic (or the Jira Product Discovery idea it implements) against its own In Scope list - which items are done, partly done, not started, or have no evidence - then flag scope conflicts and stale statuses, and draft the In Scope list for the follow-on epic. Use this whenever the user is preparing for an epic review, quarter close-out, scope or refinement meeting, asks "what was completed on this epic", "what is left for Q2", "what should carry over", "prep me for the review of PRO...Votes: 0GitHub stars: 3
- Explain The NumberLike-for-like before a measured number is reported or credited to a change. Use before saying a change moved a score, a count, a before/after delta, a benchmark time or speedup, a Lighthouse or Core Web Vitals result, an eval score, or an error, conversion or traffic rate. For whether the tests and gates passed, use `regression-proof`.Votes: 0GitHub stars: 3
- GrillingGrill the user relentlessly about a plan, decision, or idea until every branch of it is settled. Use when the user wants to stress-test their thinking, says "grill me", "poke holes in this", "interrogate this plan", or asks to be questioned before building something.Votes: 0GitHub stars: 3
- HandoffWrite a handoff note so a fresh session can continue this one's work. Use when the user says to hand off, wrap up, or save progress for later, or when a long session is about to end with work still open.Votes: 0GitHub stars: 3
- Leader 1 1 PrepBuild a prep brief for a recurring 1:1 with a skip-level or senior leader. Pulls the last meeting's notes, the tickets you touched since, recent chat threads with that leader and any drafts they are waiting on, then drafts a fixed five-block agenda with a carry-forward list and an after-action step. Use when the user says they have a 1:1 coming up, asks to prep for one, asks "what should I raise with <name>", or wants to review what is outstanding since the last one.Votes: 0GitHub stars: 3
- Llm IntegrationChecklist for code that calls a language model or exposes a system to one. Use when writing or reviewing code that calls a model API (Anthropic, OpenAI, Bedrock, Gemini, Perplexity), a prompt or prompt template, structured model output, an MCP server or tools an agent will call, or a surface that carries user- or web-controlled text to a model without calling one (a tool result, a chat card, a ticket). Also use when choosing which model a product's code calls, or pricing those API requests.Votes: 0GitHub stars: 3
- No Ai AttributionKeep AI-assistant credit lines out of anything published on the user's behalf. Use before writing a commit message, pull request, issue, comment, review reply, ticket, wiki page or chat message.Votes: 0GitHub stars: 3
- Open In My BrowserOpen a link the user shares in their own Chrome through the Claude in Chrome extension, where their sign-ins and VPN work. Use whenever the user pastes a URL to a private or internal page (a pull request, a ticket, a wiki page, a dashboard, an internal host) or says "use my browser".Votes: 0GitHub stars: 3
- Pick UpContinue work from a handoff note an earlier session wrote. Use when the user says to pick up, continue or carry on from earlier work, or points at a handoff file.Votes: 0GitHub stars: 3
- Plain WritingDraft text a person will send or post under their own name, in plain language that does not read as machine-written. Use when drafting or editing a chat message, an email, a pull request description, a comment, a wiki page, an announcement or a post on the user's behalf, or when the user says a draft "sounds like AI", is too long, or is too stiff. For a ticket, use `ticket-write` to write one and `ticket-trim` to shorten one.Votes: 0GitHub stars: 3
- Regression ProofProve a change before claiming it is done - judge lint, typecheck, tests and git push by their exit codes rather than by reading output, and show that a bug fix's regression test fails without the fix. Use before saying "tests pass", "lint is clean", "pushed" or "fixed in <sha>"; before opening or updating a pull request; whenever a command is piped into grep, tail or head; and whenever a bug fix or false-positive fix ships with a new test. For whether a measured number (a score, a timing, an...Votes: 0GitHub stars: 3
- ResearchInvestigate a question against primary sources and capture the findings as one cited Markdown note. Use when the user wants a topic researched, a vendor's docs or API facts gathered, a library's or tool's real behavior confirmed, or reading legwork delegated while the main session keeps working.Votes: 0GitHub stars: 3
- RetroReview a finished coding session for what slowed the agent down or let a mistake through, and turn one lesson into a test, check or doc in the project so the next session does not repeat it. Use when the user asks for a retro or retrospective, a post-mortem of a session, or "what should we change so this doesn't happen again". To carry unfinished work into a new session, use `handoff`; to prove a fix before claiming it, use `regression-proof`.Votes: 0GitHub stars: 3
- Skill Collision AuditFind skills whose descriptions fight over the same request, so Claude picks one at random or the wrong one, and fix the descriptions. Use when the user asks to audit, clean up or deduplicate their skills, when a skill fires that should not have, after installing a plugin, or before adding a new skill to a large library.Votes: 0GitHub stars: 3
- SupervisorRoute a multi-step task across cheaper subagents while the main session keeps the plan, the judgment calls and the verification. Use at the start of any task with more than one step, before spawning a subagent, when picking a model for a subtask, when a subagent fails, or when the user mentions cost, tokens or model choice.Votes: 0GitHub stars: 3
- TddTest-driven development, red then green, one vertical slice at a time. Use when building a feature, a rule, a config option or a bug fix test-first, when the user says "TDD", "red-green" or "write the test first", or when a subagent is handed a ticket to build.Votes: 0GitHub stars: 3
- Ticket DigestTurn a batch of tickets created or updated in a time window into one short, paste-ready message, one line per ticket, flagging the ones that need a decision. Use when the user asks what they filed today or this week, wants a recap or roundup for a product owner or team channel, or after filing three or more tickets in one sitting.Votes: 0GitHub stars: 3
- Ticket TrimShorten an existing ticket that is too long or too technical, moving the engineering detail into a Technical notes comment so nothing is lost. Use when the user gives a ticket key or link and asks to trim, condense, simplify or clean it up, or says a product owner or analyst found it hard to read.Votes: 0GitHub stars: 3
- Ticket WriteDraft and file short tickets (bug, task, story, spike, epic) that a business analyst or product owner can read in under a minute, with the engineering detail moved to a first comment. Use when the user wants to create, draft or file a ticket in Jira, Linear or GitHub Issues, or to turn findings from an investigation, incident or review into backlog items.Votes: 0GitHub stars: 3
- Writing For AgentsWriting documents for agents. Use when creating or editing a skill (its SKILL.md, description or reference files), when modifying AGENTS.md or CLAUDE.md, or when reviewing an agent-facing document that behaves inconsistently across runs. Prose that people read, such as a memo or a one-pager, follows its own rules.Votes: 0GitHub stars: 3