Claude Skills by shashankreddy509

Investigate a Jira bug from its key to a root-cause verdict — classify bug-vs-feature, fan out read-only Explore agents across the repo, adversarially confirm the cause, and write a tasks/<TICKET>-triage.md artifact a lean fix-planner can pick up. Orchestration only; read-only, never touches Jira, stops at verdict + fix-location (no fix, no plan). Use when given a Jira bug key to root-cause, or "triage PROJ-XXXX", "is this a real bug", "where's the root cause", "investigate this ticket". Trig...

Condense a grown feedback/memory file in place — shrink it ~75-85% WITHOUT losing any distinct lesson. Merges points that mean the same thing, groups by theme, keeps every unique rule, concrete constant, and cross-reference. Use when the file has grown unwieldy, when the user says "feedback file is too big" / "shrink it but keep all the content", or on /condense-feedback. Backs up the original first.

Create a Jira ticket in the current project from a short context blurb. Discovers the project's Jira config (cloudId + key) from its CLAUDE.md, fetches the real issue types, asks type then context, drafts a title + description (structured body for Bugs), shows the draft for inline edit, and creates only after explicit approval. Use on 'create a ticket', 'create a jira', 'file a jira', 'new issue', 'open a ticket'. Global; project-agnostic; NEVER auto-creates.

Captures this session's learnings — preferences, corrections, what worked, what to avoid — by merging them into feedback.md + project memory for future sessions. Utility/persistence skill: it records, it does not review or grade output. Trigger on /end-session or "end session".

Pre-grooming analysis of a Jira ticket — produce a readiness + spec brief so the ticket can be groomed/estimated. Read-only; writes ONE artifact (tasks/<TICKET>-grooming.md), touches no code and no Jira. Runs BEFORE a ticket is approved to work — answers "is this ready to estimate, and what will it touch", not "how do I build it" (that's /build). Never plans an implementation, never sets a story-point number, never edits Jira. Use on "/groom <TICKET>", "groom this ticket", "is this ready to e...

Post a comment on a Jira ticket that renders cleanly despite the Atlassian MCP mangling markdown — strips bold/italic markers, indents code, keeps CC mentions verbatim. Use when the user says "post this on the ticket", "add a comment to PROJ-XXXX", "comment this on Jira", or after authoring an analysis/closure note to share. Triggers: jira comment, post on the ticket, add a comment, comment this on jira, post to jira.

Synthesize this session's preferences/corrections into tasks/feedback.md and merge them into the existing file without ever deleting prior points. One job — the feedback artifact only. Called by end-session and by start-session's mid-session auto-capture; can also run standalone. Triggers: merge feedback, update feedback.md, capture preferences, record corrections.

Prove whether a build, compile, or test failure is caused by YOUR change or was already broken — by stashing your edits, re-running, and comparing. Read-only verdict; fixes nothing. Use when a build/test fails and the question is "is this my fault or pre-existing", or before blaming your diff. Triggers: is this my change, did I break it, pre-existing failure, was it already broken, prove pre-existing, my fault or not, stash and recompile.

Read-only "anything pending?" sweep of live project state — git branch + dirty files, open PRs, the deploy gap (latest tag vs origin/main, app-code only), and open Jira issues (statusCategory != Done). Answers "what's left / anything pending / what's next" in one shot WITHOUT acting on anything. Use on '/standup', "anything pending?", "what's next", "where are we". Never commits, ships, or deploys — it only reports the standup.

Session-bootstrap orchestration skill — its one job is to bring a working session online: apply senior-collaborator operating parameters, load prior feedback, pull the project's Jira backlog, and activate the standing plan-gate (analysis + plan + approval before any code edit). Trigger on /start-session or "start session".