All authors
Claude Skills by lucavb
github.com/lucavb13 skills1 installs48 views
- AngularAngular zoneless conventions — signals, toSignal, shells, encapsulated styles. Use for pages, forms, create/edit routes, route-driven loads, dates, shared UI library wiring, or SCSS/layout work.Votes: 0GitHub stars: 3
- Atlassian Jira Adf FormattingRound-trip Jira story descriptions via Atlassian MCP ADF — fetch full doc, edit in files, validate, file-backed editJiraIssue. Use when creating or editing Jira stories with table bullets, fixing ticket typos, or when markdown editJiraIssue flattens Requirements/AC cells.Votes: 0GitHub stars: 3
- Closing RitualClosing ritual — surface doubts, blind spots, and unverified claims before work is accepted. Use when the user signals acceptance or session end ("wrap up", "closing ritual", "before I accept this").Votes: 0GitHub stars: 3
- Conversation HandoffSummarize the current conversation into a copy-pasteable handoff message for a fresh chat. Use when a topic has drifted too far from the original conversation and should be split into its own thread, or when the conversation has been compacted so heavily that context is unreliable and needs a clean restart.Votes: 0GitHub stars: 3
- Discover Before PlanningDo discovery during planning — explore the codebase and close open questions before presenting a plan. Use when drafting implementation plans, or when a plan would defer verification or "pre-flight" checks to execution.Votes: 0GitHub stars: 3
- Gh FetchGitHub fetch — gh CLI for GitHub URLs; checkout when multiple file accesses are foreseen. Use when the user shares a GitHub link or wants remote repo source.Votes: 0GitHub stars: 3
- Plainspoken WritingPlainspoken prose pass for drafted or revised text: make it specific, direct, evidence-grounded, and proportionate.Votes: 0GitHub stars: 3
- Refining Jira TicketsPre-scrum refinement of Jira stories for engineering readiness. Use when the user asks to refine tickets, review PO stories, spot plot holes, pre-scrum refinement, or leave refinement comments for a product owner on Jira.Votes: 0GitHub stars: 3
- Review CoreShared adversarial review engine: blind parallel critics (including alternatives), tribunal adjudication, and adversarial re-validation. Used by review-tribunal and ticket-to-pr-pipeline. Use directly when blind-reviewing a local branch, commit range, or working tree.Votes: 0GitHub stars: 3
- Review TribunalReview tribunal for pull requests or local Git diffs: intake, review-core blind critics (including alternatives), tribunal, adversarial validation, then local reporting or interactive GitHub posting. Requires review-core. Use when reviewing a PR, comparing a base branch with the current branch, reviewing a commit range or working tree, or spawning a review tribunal.Votes: 0GitHub stars: 3
- Ticket To Pr Pipelineticket-to-pr-pipeline: Jira ticket through plan, build, review-core, and PR in one continuous run. Requires review-core. Use for a Jira ticket or bug when the user wants a merge-ready PR or invokes /ticket-to-pr-pipeline. Use when the user approves the plan or says implement, execute, or go ahead after intake.Votes: 0GitHub stars: 3
- TldrCondense the immediately preceding assistant answer into a direct TL;DR.Votes: 0GitHub stars: 3
- Writing Commit MessagesRequired before every git commit. Run this pass when staging, committing, push, or any workflow says commit — plan todos, AGENTS.md deploy flow, user "commit and push", handoffs from other skills, or drafting feat(scope) from memory.Votes: 0GitHub stars: 3