bedrock

Plugin bedrock from marketplace bedrock in paranoica/redline-music. Commands read from the repo's manifest — 7 days ago.

Skills (24)

• graders
• allow

  The owner grants one action, e.g. /bedrock:allow push, until a time or the end of the plan.

• arch

  Architecture review on request — hot spots, deepening and deletion candidates, boundary breaks, stale notes; the pick designed three ways. Use for "архитектурное ревью", "что упростить", "architecture review".

• ask

  Use first for any question about this project's code or decisions — "где у нас", "как работает", "быстро скажи", "how does X work". Answers from notes and the code map with source and confidence.

• call

  Debrief a call from its transcript — archive the raw text, extract decisions and debts with verbatim quotes and timecodes, check every quote. Use for "разбери созвон", "что решили на колле", "debrief the call".

• code-review

  No-mercy code review — security (injections first), correctness, performance — of a PR, uncommitted changes or a whole project, with grounded, verified findings. Use for "review this", "проверь код", "найди уязвимости".

• day

  The working loop for any task — intake, plan, critic, cut, implement, review, deliver. Use first for every new task, feature or change: "надо добавить", "сделай", "build X", "начинаем день".

• debug

  Root-cause debugging — a red loop first, hypotheses, one variable at a time, a cause record, a regression test. Use first for any bug or failing test: "падает", "не работает", "почему", "CI красный".

• design-creator

  Web design engine — design, redesign or build the visual layer of a site, landing, dashboard or app, with distinctive typography, layout, motion and 3D. Use for "сделай дизайн", "редизайн", "design this page".

• doc

  Documents for people — briefs, reports, root-cause write-ups as Markdown rendered to PDF with folio. Use for "сделай отчёт", "оформи документ", "write a report", "make a PDF".

• e2e

  End-to-end checks in a headless browser — scripted Playwright tests for main paths, and an exploratory run that turns findings into tests. Use for "прогони e2e", "проверь в браузере", "e2e", "test the UI".

• handoff

  Shift handover — write a ten-section handoff note before a restart, or resume from one. Use for "пора рестартить", "передай смену", "продолжаем", "handoff", "resume".

• humanize

  Make a text sound like the owner wrote it, in Russian or English, copy-ready for Slack; replies to pasted threads. Use for "очеловечь", "ответь ему", "humanize", "draft a reply".

• hunt

  Bug hunter — try to break code that is already green, with properties, boundaries, hostile input and concurrency. Use for "сломай это", "поищи баги", "break it", after green on R2/R3.

• kb

  Write and keep the project knowledge base — decisions, failures, module notes, runbooks, calls; validate, fix drift, find gaps. Use for "запиши решение", "обнови заметку", "record a decision", "kb".

• next

  Status navigator — what is done, what is left, who is waited on, can the owner rest. Use for "что дальше", "всё сделал?", "можно чиллить?", "what's next", "where are we".

• night

  Autonomous work until morning — a pre-sleep check, the allowed list, auto-continue with fuses, a watchdog, a morning report. Use for "автономно до утра", "поработай ночью", "work overnight".

• retro

  Weekly retro — read the week's logs, agents, reviews and failures, find what repeats, tune the system, plan a realistic next week. Use for "ретро", "итоги недели", "retro", "how did the week go".

• review

  Review gate for a finished block — deterministic checks, code review, plan-compliance review, silent fixes, rounds until clean. Use for "проверь", "ревью", "review this", before any PR.

• revoke

  The owner withdraws every grant of this project at once.

• start

  Start a project with bedrock — a new one by interview, or an existing one by onboarding; writes the base, AGENTS.md, workspace settings and verified commands. Use for "новый проект", "подключи проект", "start a project".

• triage

  Bug triage — reproduce each report on the current version, group duplicates, set priority, decide fix, defer or decline. Use for "разбери баги", "что с репортами QA", "triage", "new bug reports".

• unleash

  The owner turns on all-out mode for this project until a time; every guard still logs.

• writing

  Write or rewrite skills, agent definitions, briefs and rule files by the D013 rules, then check them. Use for "напиши скилл", "поправь агента", "write a skill", "edit this brief".

Subagents (12)

• analyst

  Compares approaches from sources and reasons to a recommendation.

• architect

  Designs module boundaries and weighs options for structural decisions.

• bug-hunter

  Hunts edge-case bugs in working code by trying to break it.

• critic

  Attacks a plan before code is written; reports only real blockers.

• escalation

  Second opinion when the session is stuck after repeated failed attempts.

• implementer-untested

  Implements one task without a ready test, on the stronger model.

• implementer

  Implements one task that has a test, touching only its listed files.

• inventory

  Reads many files and returns sourced facts, so the session need not.

• researcher

  Finds and quotes sources on the web for a narrow question.

• reviewer

  Reviews a diff for bugs and broken requirements, with fresh eyes.

• security-reviewer

  Hunts injection, auth and secret flaws in a change.

• verifier

  Re-checks claims or findings against the source; keeps, downgrades or cuts.

Hooks (9)

• SessionStart

  python3

• UserPromptSubmit

  python3

• PreToolUse

  python3

• PostToolUse

  python3

• SubagentStart

  python3

• SubagentStop

  python3

• Stop

  python3

• PreCompact

  python3

• Notification

  python3