All authors
Claude Skills by vedantlavale
github.com/vedantlavale10 skills0 installs0 views
- Before And AfterCapture before/after proof for a PR and put it in the PR body. Screenshots for anything with a visible surface, measured numbers for anything without. Use when opening a PR, when the user says "before and after", "PR screenshots", "visual diff", "show me proof".Votes: 0GitHub stars: 16
- Code StructureUse when multiple workflows duplicate the same operational logic, when deciding what belongs in actions vs shared services, or when refactoring repeated operational blocks across domain flows. Use when adding new features that share mechanics with existing ones.Votes: 0GitHub stars: 16
- Deep ReviewDeep code review for pull requests, tuned to match CodeRabbit and Greptile depth but reported short. Checks two things separately, whether the code is right (correctness, project invariants, security, performance, conventions, code smells) and whether it does what the linked issue asked, then posts a plain-language summary anyone can read, at most five P0 to P3 findings underneath it, and a verdict. Use when reviewing a PR, re-reviewing after a push, or when the user asks for a thorough review.Votes: 0GitHub stars: 16
- Diagnosing BugsDiagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.Votes: 0GitHub stars: 16
- Evidence Driven TestingProve a change works by driving the running app and capturing what happened, before the fix and after. Screenshots and probes by default, a screen recording when a flow only makes sense over time. Use whenever a change needs evidence instead of a claim that it works.Votes: 0GitHub stars: 16
- Improve Codebase ArchitectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.Votes: 0GitHub stars: 16
- New FeatureStart a task. Clarify the issue with the user when it is unclear, then branch off the latest origin/main after checking no open PR already owns the files. Use at the start of every feature, fix or task, before writing code.Votes: 0GitHub stars: 16
- Setup SdlcAdopt the agentic SDLC kit in this repository. Reads the codebase, proposes answers, asks the user to confirm, then fills in every CUSTOMISE block in the skills and AGENTS.md. Use after running install.sh, or when the user says "set this repo up with the kit", "configure the SDLC skills", or "fill in the review rules".Votes: 0GitHub stars: 16
- Ship PrOpen a PR with before/after proof, then loop on the review until the verdict is 'Looks good' with no unresolved comments. Use when the work is built and proven and it is time to open or finish a pull request, or when the user says "ship it", "open a PR", or "get this PR clean".Votes: 0GitHub stars: 16
- TriageMove issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.Votes: 0GitHub stars: 16