All authors
Claude Skills by lbk-open
github.com/lbk-open20 skills0 installs19 views
- Ss ArchiveMerges an active OpenSpec change's delta specs into the authoritative openspec/specs/ tree and moves the change directory into the dated archive. Idempotent; the ss-create-pr skill calls it automatically before opening a PR. Use it once a delta is reviewed and ready to become part of the source of truth.Votes: 0GitHub stars: 2
- Ss CleanupUse after development work is finished to confirm the PR/MR is merged (offering to merge it if not), return to the main checkout on an up-to-date default branch, remove the development branch's worktree, and delete the spent branch — both locally and, optionally, on the remote. Exits immediately with nothing to do if there's no development branch or worktree to clean up.Votes: 0GitHub stars: 2
- Ss Code ReviewUse for a comprehensive code review of a diff — standalone (a pull request, a SHA range, or the current branch) or as the post-coding review step invoked by ss-coding. Dispatches independent subagents for general code quality, coding-standard compliance (global, stack, and project level, plus OpenSpec compliance when specs are present), and, in post-coding mode with enough scope, a cross-task integration review; then filters by confidence, deduplicates, and produces one consolidated verdict.Votes: 0GitHub stars: 2
- Ss Coding WorkflowExecutes a ready-made plan or a plain-language change instruction end to end — branch, multi-agent coding with built-in review, and PR/commit delivery. Use for running an existing execution plan or a simple, well-scoped code change; use ss-feature-workflow instead when a proposal and plan still need to be drafted.Votes: 0GitHub stars: 2
- Ss CodingUse when an implementation plan (or a plan-shaped requirement) needs to be executed as parallel, test-driven development across multiple subagents, ending in one comprehensive review pass. Reads the plan, dispatches implementer subagents by parallel group, tracks task status and git commits, enforces scope and full-delivery rules, hands off review to the ss-code-review skill, and reports a human acceptance checklist.Votes: 0GitHub stars: 2
- Ss Create BranchUse when starting new development work to cut a properly named branch from the remote default branch, decide whether to develop it in an isolated git worktree, push it immediately, and set up upstream tracking. Takes a branch name, a requirement link, or a plain-language description as input.Votes: 0GitHub stars: 2
- Ss Create PrUse once coding and code review are complete and it's time to open a pull/merge request. Runs pre-flight checks (tests, cleanup scan), rebases onto the target branch, verifies again if the rebase changed anything, then opens a PR on GitHub (via gh) or an MR on GitLab (via glab) depending on the repository's remote. Falls back to a local conventional-commit summary if there's no remote or forge CLI available, or if the user declines — that fallback is a normal outcome, not a failure.Votes: 0GitHub stars: 2
- Ss Feature WorkflowEnd-to-end feature delivery — takes a PRD, requirement description, or requirement doc link and orchestrates branch creation, a complexity-gated technical proposal (complex requirements only), execution plan, multi-agent coding with built-in review, and PR/commit delivery. Use only when the user explicitly asks for the full feature pipeline, not for a single edit or question.Votes: 0GitHub stars: 2
- Ss GuardrailsA library of safety, code-quality, and anti-mistake checklists that other ss-* skills consult on demand while writing or reviewing code. Not invoked directly by users — skills like ss-coding-workflow, ss-code-review, and ss-coding read core.md plus the relevant language file before generating or grading code.Votes: 0GitHub stars: 2
- Ss InspectUse when investigating any technical issue — a bug, alert, performance regression, or unexpected behavior — that needs evidence-based root-cause analysis rather than a guess. Runs a report-only six-phase process with L0 Local, L1 Runtime, and L2 Systemic evidence budgets, automatic risk promotion, and a structured repair/verification report.Votes: 0GitHub stars: 2
- Ss List ChangesLists active OpenSpec changes and recent archived entries in the current repository. Use this skill to get a quick inventory of in-flight delta specs and what has already been merged, without manually browsing the openspec/ directory.Votes: 0GitHub stars: 2
- Ss Multi Repo WorkflowExecutes a requirement that spans multiple git repositories — plans once, then runs one repository-scoped coding unit per repository (each running ss-coding-workflow from that repo's real working root), batched by dependency order, and consolidates all resulting PRs into one cross-repo report. Use only when explicitly invoked or handed off from a single-repo workflow's multi-repo detection.Votes: 0GitHub stars: 2
- Ss PlanUse before writing any code, once you have a requirement, technical proposal, or spec that needs to become an executable, task-level plan. Decomposes the input into self-contained, TDD-ordered tasks with explicit dependencies, exact file paths, and acceptance criteria traced to OpenSpec scenarios; splits multi-subsystem requirements into separate plans and produces a master plan when the split spans multiple repositories.Votes: 0GitHub stars: 2
- Ss ProposalUse when you have a PRD or requirement description and need a complete technical proposal before writing any code. Filters the requirement down to this repository's boundary, analyzes the existing architecture and conventions, and produces a Markdown proposal covering architecture, data flow, key interfaces, alternatives, risks, and milestones — gated by a self-review and, when available, an independent reviewer pass.Votes: 0GitHub stars: 2
- Ss ReferencesA library of shared templates that other ss-* skills read at runtime — subagent dispatch prompts, the technical-proposal template and its quality checklist, the OpenSpec directory skeleton, and the multi-repo detection rules. Not invoked directly by users; skills like ss-coding, ss-proposal, ss-write-spec, and the workflows read the file they need before producing an artifact.Votes: 0GitHub stars: 2
- Ss Reverse SpecReverse-engineers OpenSpec source-of-truth capability specs from an existing (brownfield) codebase, either as a full baseline sweep or for a single capability. Bootstraps the openspec/ skeleton first if the project doesn't have one yet. Use this to give a legacy repository a meaningful starting spec instead of an empty openspec/specs/ directory.Votes: 0GitHub stars: 2
- Ss Show SpecDisplays the current source-of-truth OpenSpec for a capability, or lists all capabilities when called without one, and summarizes recent archived changes that touched it. Use this as the entry point before reading or editing anything under openspec/ — do not grep or browse the directory manually first.Votes: 0GitHub stars: 2
- Ss Trace SpecTraces when an OpenSpec Requirement or Scenario was added, modified, removed, or renamed by searching current specs, archived deltas, and git history. Use this to answer "when and why did this behavior change" questions about a capability.Votes: 0GitHub stars: 2
- Ss Troubleshooting WorkflowEnd-to-end defect fix — takes an issue link, alert ID, or problem description and orchestrates tier-adaptive root-cause investigation, human confirmation, branching, a fix plan, multi-agent coding with built-in review, and PR/commit delivery. Use only when the user explicitly asks for the full diagnose-to-delivery pipeline, not for diagnosis alone.Votes: 0GitHub stars: 2
- Ss Write SpecGenerates or updates OpenSpec delta specs under openspec/changes/<change-id>/ from a proposal, PRD, or plain-language requirement, bootstrapping the openspec/ skeleton first if the project doesn't have one yet. Use this to align capability specs with reviewers before writing a full execution plan, or to adjust deltas without regenerating the plan.Votes: 0GitHub stars: 2