rccsousa-skills
Claude Code workflow skills: PR flow, triage, code review, unattended overnight queue drain, and autonomous maintainer pipelines.
Plugin rccsousa-skills from marketplace rccsousa-skills in rccsousa/skills. Commands read from the repo's manifest — 19 days ago.
What it installs
Skills (21)
angular-cyber-money-reviewRun two blind host/counterpart reviews of one PR, branch, or commit range using the cyber-money-review rubric, then reconcile and verify money-movement and cyber findings. Use only when the user explicitly asks for an angular cyber-money review, dual-model payment/security review, or invokes this sk
angular-maintainability-reviewRun two independent blind readability and maintainability reviews, host plus counterpart model, then verify and distill the recommendations. Use for /angular-maintainability-review or an explicitly requested angular maintainability review. Use angular-review for its correctness-focused gate.
angular-stack-reviewReview an entire PR stack as one coherent change with two parallel blind passes by the host and counterpart model, then verify cross-PR defects, intermediate-state safety, and fix ownership. Use for angular review gh stack followed by a stack number, an angular stack review, or reviewing stacked PRs
code-fixApply fixes from a code-review findings packet. Always fixes must-fix + should-fix, fixes consider items only when sensical (defers judgement-call ones), applies fixes, commits via /create-commit. Works on a local branch (no PR yet) or against an open PR — driven by the packet's `source` field. Thre
code-reviewReview a diff (local branch vs base, OR an open PR) and produce a structured findings packet (must-fix / should-fix / consider / nit). Designed to feed code-fix in a cascade. Default mode is **local** — no PR required. Use inside one-shot's review phase before pushing, when self-reviewing a branch,
council-of-agentsParallel multi-lens planning amplifier. Dispatch 3-5 subagents in parallel — each with one lens (architecture, UX, security, ops, persistence, etc.) — and synthesise their reports into a unified design brief. Use before writing plans when scope is fuzzy, multi-stakeholder, or spans multiple concerns
create-commitStage changes and create a commit with a one-line Conventional Commits message. Groups files by logical change, builds a focused subject, and never adds Claude as co-author. Use when ready to commit, after a focused chunk of work, or when the user says "commit this", "make a commit", "stage and comm
create-prOpen a pull request from the current branch with a Conventional Commits title and a WWH body (What / Why / How). Never includes Test Plan, Risk, Rollback, or Rollout Plan sections. Use when the user says "open the PR", "make a PR", "create PR", or after a feature branch is ready to surface for revie
diagnosing-bugsDiagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
drive-to-mergeableDrive an open (or about-to-open) PR to a merge-ready state via a dual-source review cascade — dispatch a reviewer subagent + an external PR bot (Copilot/CodeRabbit), triage every finding into fix-now / file-issue / wontfix, autofix the in-scope ones with a regression test, file issues for the rest,
install-maintainerInstall an autonomous maintainer pipeline into a GitHub repo — intake queue → grounded issue → draft PR → driven-to-mergeable, stopping at a human merge gate. Three GitHub Actions stages wrapping the triage, one-shot and drive-to-mergeable skills. Intake is pluggable: Basecamp columns, GitHub Issues
issue-enrichingTurn a thin GitHub issue into an agent-pickup-ready one — ground it in the repo via a read-only Explore subagent, reach a verdict, and append a delimited `## Agent brief` (findings with file:line, scope, acceptance, out-of-scope) to the issue body without touching the original text. Transitions nigh
landDrive an open PR all the way to merged — review cascade, autofix, undraft, verify, merge — behind a deterministic core-path gate that refuses to auto-merge anything touching migrations, CI, auth, lockfiles, or repo-declared core paths. This is the one skill allowed to run `gh pr merge` unattended; /
linear-groomingGroom your Linear tickets — walk every open issue assigned to you (scoped by a local repo config, not a Linear project), check its PRs on GitHub, and move it to the status the evidence supports (in progress / in review / done). Use when the user says "/linear-grooming", "groom my tickets", "sync Lin
mermaid-diagramDraw a Mermaid diagram of a flow or a proposed change, rendered and as copyable source, with the parts the proposal changes highlighted in yellow. Use for /mermaid-diagram or when asked to diagram a flow, ticket or proposal.
nightshift-prepGet a repo and its backlog ready for an unattended `/nightshift` run. Two jobs: first-run repo setup (labels, `.nightshift/config.json` with core_paths inferred from the repo, gitignore, permission-ceiling check), then queue curation — score every open issue for whether an unattended session could a
nightshiftUnattended overnight drain of a GitHub issue queue. Enriches every issue labelled `nightshift` into an agent-pickup-ready brief, then emits a detached bash driver that runs one headless `/one-shot` session per issue in its own worktree — 3 concurrent — opening a draft PR each, and flags which PRs pa
one-shotEnd-to-end feature orchestration: plan → implement → review → fix. Three autonomy modes (hitl, grill, auto) control where human checkpoints land. Defaults to grill (HITL + `/grill-with-docs` checkpoints between phases, ADRs written post-implement); `auto` is opt-in behind a risk-ack flag and the inv
surgical-reviewPerform a focused, single-pass review of a small or localized PR for concrete regressions, without the counterpart-model overhead of angular review. Use when the user invokes $surgical-review, asks for a surgical review, or explicitly chooses a lightweight review because angular review is unavailabl
tddTest-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests. The technique itself; for queue-driven execution that uses TDD inside, see /issue-worker (PRD issues file) or /implement (spec/tickets).
triageTurn raw tester/user feedback into curated, agent-pickup GitHub issues, one item at a time. Feedback arrives two ways: pasted (a message + screenshots) OR pulled from a Basecamp inbox column. For each item: parse the complaint, ground it in the current repo via a read-only Explore subagent, reach a
Maintain rccsousa-skills?
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.