Pavel Sokolov
Community@hacker-cb
Pavel Sokolov's hcb-dev skill suite orchestrates Git branching, parallel session coordination, multi-engine code review, and GitHub/GitLab pull request lifecycles.
Agent Skills by Pavel Sokolov
Showing 21 vetted skills indexed across 1 GitHub repositories.
sync-base
Synchronizes a git branch with its moved base via fast-forward, rebase, or merge.
session-dispatch
Generates pasteable work orders that hand unfinished builds or investigations to another Claude Code session.
multi-review
Reviews a code change with Claude, security, and Codex sources and reports findings with per-source coverage.
git-cleanup
Sweep merged branches, orphaned worktrees, and dead upstream tracking from a git repository.
session-plugin-refresh
Re-reads skills and references after a plugin update and reconciles prior session actions against the new text.
implementation-workflow
Implements tasks and issues as sliced, reviewed branches through a gated autonomous workflow.
findings-pass
Verifies and rules a run's findings independently, presenting outcomes in one ranked table.
github-pr-workflow
Drive a GitHub pull request from feature branch to merged PR with CI and Copilot fix loops.
wave-worker
Executes a dispatched wave batch order and coordinates its return with the master session.
wave-refresh
Recompute which parallel work batches can safely start against the current repository state.
seeding-gitignore
Creates and edits .gitignore files with a fixed baseline plus project-derived language patterns.
backlog-survey
Surveys open issues against the code, tiers them, and recommends what to work on next.
status
Report current work status by re-reading ledgers, branches, and change requests.
wave-dispatch
Launch planned work batches as parallel sessions via chips or pasteable orders.
master-session
Coordinates parallel sessions building an epic through wave planning, dispatch, and acceptance.
session-handoff
Generates a pasteable prompt summarizing finished session work for handoff to another Claude Code session.
shipping-workflow
Review, fix, and complete a finished code slice via local merge or change request.
claude-review
Review a change with Claude finder agents and independent verification over a fixed range.
issue-tracking
Manage deferred work in GitHub and GitLab issue trackers via gh and glab CLIs.
dependency-versions
Resolve dependency versions from registries using package manager add commands.
codex-review
Reviews a code change with a single read-only Codex CLI pass and returns findings.
Frequently Asked Questions About Pavel Sokolov
FAQPage SchemaWhat tasks can I accomplish with hacker-cb's hcb-dev skills?βΌ
You can sync branches against moved bases, implement issues end-to-end in slices, run multi-engine reviews (Claude, security, Codex), ship work via local merge or GitHub PR, triage GitHub/GitLab issues, survey backlogs, coordinate parallel build sessions, and pin dependency versions resolved from registries.
Who are these skills designed for?βΌ
Software engineers and technical leads running Claude Code sessions who manage Git-heavy development: feature branches, worktrees, pull requests, issue backlogs, and epics split across multiple parallel sessions. Bilingual triggers support both English and Russian speakers.
How do the skills run in practice?βΌ
They install as a Claude Code plugin whose skills trigger on natural-language requests. Implementation-workflow slices tasks and calls shipping-workflow per slice; shipping-workflow hands request-mode completions to github-pr-workflow; master-session dispatches batches to wave-worker sessions via wave-dispatch.
What are the prerequisites and dependencies?βΌ
A Git repository, the Claude Code host with the hcb-dev plugin installed, and the forge CLI for reading merged and open change requests. GitHub or GitLab hosting is required for issue tracking and PR driving; Dependabot config sync applies to GitHub-hosted repos.
Do these skills push code or merge without authorization?βΌ
No. Sync-base writes only the local worktree and never pushes; github-pr-workflow merges only on explicit authorization and otherwise stops at ready; findings-pass and backlog-survey are report-only, with every tracker write executed solely on the user's word.