All authors

Claude Skills by blazej-bryla
github.com/blazej-bryla9 skills0 installs0 views
- Address ReviewClose the PR feedback loop — unresolved review threads worked one by one, then commit, replies.Votes: 0GitHub stars: 2
- BugfixResolve a bug from a Linear issue — quick path for obvious local bugs, full investigation (root cause here, fix coded by a sonnet subagent) otherwise; then review, commit.Votes: 0GitHub stars: 2
- CommitOne clean commit — explicit paths, terse 2–4 line message from a haiku subagent, no attribution.Votes: 0GitHub stars: 2
- Deep ReviewCode review sized to the diff — one light reviewer for small diffs, four parallel specialists otherwise; deduped findings, interactive triage, one GitHub review.Votes: 0GitHub stars: 2
- DeslopSimplify the current branch's changes without changing their behaviour — inline trivial helpers, drop speculative and defensive code; significant removals are proposed one at a time; then commit.Votes: 0GitHub stars: 2
- KickoffPlan a Linear task end to end — grilled context.md in ~/.agents/scratch/<slug>/, then tickets. `/kickoff refine <links…>` prepares questions for a refinement meeting instead (REFINE.md).Votes: 0GitHub stars: 2
- PrOpen or update the pull request for this branch — body, create and change summary per the repo's profile (`pr.body`, `pr.create`, `notify.summary`: the project's own skills or mine); the content comes from the planning artifacts, the tickets' Verify by lines and test evidence, with AFTER screenshots (agent-browser) for UI changes, BEFORE + pixel diff only against a deployed baseline, all attached with gh --attach; and a local review guide.Votes: 0GitHub stars: 2
- Wf InitMap this repo's own agent setup onto my workflow's slots — discover its skills, agents, settings and conventions, propose per slot mine / project / none with reasons and overrides, ask, write ~/.agents/profiles/<id>.json, then dry-run /work and /pr against it. Re-run shows only what changed.Votes: 0GitHub stars: 2
- WorkWork a tickets directory to completion — unblocked tickets run in parallel on implementer subagents in their own worktrees; every finished ticket comes back here for review, squash-merge and commit; the loop continues until the frontier is empty.Votes: 0GitHub stars: 2