← all publishers

msolecki

@msolecki source repo

Report this profile Claim this profile

• 32 skills
• 0 followers
• 1 hour ago last updated

1. ▌
   Project Baseline · msolecki

   Check a repository against a baseline of engineering practices (validated env module, secret scanning, coverage ratchet and more) and propose each missing one as a backlog item, after approval; not a code audit (audit-to-backlog). Use when starting work in a repository or when the user asks what the project is missing; for example "what is the repo missing", "project baseline".
   0 installs
2. ▌
   Implement Backlog · msolecki

   Implement evidence-backed backlog items in small batches, validate every item and the full batch, get an independent review, update the backlog and plan, and commit only green work; for free-form tasks, parallel-lanes. Use when the user asks to execute an audit backlog, for example "fix everything with multiple agents", "implement the backlog", "apply the audit fixes".
   0 installs
3. ▌
   Instruction Review · msolecki

   Review a project's instruction file (CLAUDE.md or AGENTS.md) against recent work and propose a minimal evidence-backed diff without applying it. Use when the user asks to improve or review project instructions or invokes instruction-review, for example "improve CLAUDE.md", "review the project instructions", "what should go in CLAUDE.md".
   0 installs
4. ▌
   Nextjs Conventions · msolecki

   Apply Next.js conventions for schema-validated input, Server Components by default, Server Actions with typed results, forward-only migrations, and consented analytics. Use when writing or reviewing Next.js app code or next.config files.
   0 installs
5. ▌
   Brain Import Memory · msolecki

   Move one project's Claude Code auto memory into the user's Obsidian vault, proposing per file a new inbox note, an addition, a CLAUDE.md line or a skip, and applying only approved numbers. Use when the user turns auto memory off or says "import my auto memory", "move memory to the brain", or brain-setup reports memory files.
   0 installs
6. ▌
   Testing Conventions · msolecki

   Pin the contract in tests with absolute-instant fixtures and partial module mocks. Use when writing or reviewing test files (*.test.*, *.spec.*, tests/, e2e/).
   0 installs
7. ▌
   Comments Conventions · msolecki

   Write no comment by default, and keep the few that earn their place current. Use when writing or reviewing code comments in TypeScript, JavaScript, Python, or shell files.
   0 installs
8. ▌
   Brain Project Refresh · msolecki

   Bring the current repository's project hub note in the user's Obsidian vault up to date — drifted claims, moved paths, missing links — shown as a diff and applied only after approval. Use when the user asks to refresh or update the project note, for example "refresh the project note", "update the brain for this repo", "is the project hub up to date".
   0 installs
9. ▌
   Monitoring Conventions · msolecki

   Alert on symptoms, prevent alert fatigue, link runbooks, and separate health from readiness checks. Use when editing infrastructure code (CDK, Terraform, serverless config, CI workflows) or adding metrics and alerts.
   0 installs
10. ▌
    Typescript Conventions · msolecki

    Apply TypeScript conventions for composition, small single-purpose functions, tests for new functions, and formatter and import-alias discipline. Use when writing or reviewing TypeScript files.
    0 installs
11. ▌
    Error Handling Conventions · msolecki

    Handle errors with cause chains, typed results, one API error envelope, no log-and-throw, and no empty catch. Use when writing or reviewing error handling in TypeScript files.
    0 installs
12. ▌
    Defensive Coding Conventions · msolecki

    Check a change for defect classes that commonly ship past review, such as mismatched persistence and validation conditions, unisolated webhook side effects, missed writers or readers of shared state, collapsed multi-valued statuses, unvalidated external JSON, and silent build artifacts. Use when writing or reviewing code that handles external input, authentication, money, concurrency, persistence, or error paths.
    0 installs
13. ▌
    Spec · msolecki

    Interview the user, inspect the repository, write a feature specification and implementation plan, then hand implementation to a fresh session. Use when the user asks to define or plan a feature before implementation or invokes the spec workflow, for example "plan a new feature with me", "write a spec", "spec this feature".
    0 installs
14. ▌
    Fix Pr · msolecki

    Address every unresolved pull-request review thread, pasted review finding, or findings file, with the user's approval before each edit, commit, push, and thread resolution. Use when the user asks to fix PR comments or review findings, for example "fix the PR comments", "fix the code review findings", "address the review comments".
    0 installs
15. ▌
    Pr Cycle · msolecki

    Take a pull request to a merge verdict by merging its base in, resolving conflicts, getting an independent review, fixing the approved findings, running the project's gates, and updating the PR body, asking before fixing and before pushing. Use when the user asks to bring a PR up to date and ready to merge, for example "merge fresh dev in", "pull development into the PR", "get the PR ready to merge".
    0 installs
16. ▌
    Docs Sync · msolecki

    Check a repository's docs against its code and the project docs standard — scaffold missing pieces, refresh docs/CURRENT-STATE.md, report docs-vs-code drift, and propose the "Likely agent mistakes here" section from git history — writing nothing until the user approves. Use when docs may be stale, after a large change, or when setting up docs in a project; for example "refresh the docs", "are the docs up to date", "sync the docs with the code".
    0 installs
17. ▌
    Bug Triage · msolecki

    Triage a reported defect or incident by setting severity, reproducing it, ranking evidence-backed hypotheses, identifying root cause, and proposing mitigation, permanent fix, and regression test. Use when the user reports a defect or production incident, or asks to diagnose failing behavior, for example "we have a bug in production", "diagnose this bug", "why does this crash".
    0 installs
18. ▌
    Brain Setup · msolecki

    Create the user's Obsidian knowledge vault from the developer-os template, or connect an existing one by adding only what is missing, then point Claude Code at it after the user approves the diff. Use when the user sets up developer-os, has no `Brain vault:` line yet, or says "set up the vault", "create a vault", "connect my vault", "setup brain".
    0 installs
19. ▌
    Code Review · msolecki

    Review a pull request, diff, commit, or working-tree change against the project's conventions and rate findings P0–P3 with a merge verdict, handing code written in this session to an independent reviewer agent. Use when the user asks to review code, a PR, a diff, the last commit, or their changes, for example "review the last commit", "review my changes". Prefer it over the built-in /code-review for project conventions and an independent reviewer.
    0 installs
20. ▌
    Plan Status · msolecki

    Report measured open, done, and blocked counts from the project's active plan and backlog, then list the open decisions as numbered A/B/C questions with a recommended option, answerable in one line. Read-only. Use when the user asks where the work stands or what is left, for example "what is the status", "what is left", "show the plan status", "where do we stand".
    0 installs
21. ▌
    Skill Usage · msolecki

    Report how often each developer-os skill has fired in local Claude Code session history (calls in the last 30 days, last use) with a keep/merge/rewrite-description/remove verdict per skill. Read-only; changes nothing. Use when the user asks which skills are used, which never trigger, or before adding or pruning skills ("how often have I used the skills", "which skills work", "skill stats").
    0 installs
22. ▌
    Brain Garden · msolecki

    Produce a stale, broken-link, frontmatter, duplicate and orphan report for the user's Obsidian knowledge vault, with proposed fixes, changing nothing without approval. Use when the user asks to garden, lint, audit, or check the health of the brain/vault, for example "check the health of the brain", "clean up the vault", "find broken links in the brain".
    0 installs
23. ▌
    Brain Review · msolecki

    Review the inbox of the user's Obsidian knowledge vault — summarize captured notes, then promote, merge, reject or supersede only the notes the user names. Use when the user asks to review or triage the brain/vault inbox or captured notes, for example "review the brain inbox", "what is in the inbox", "sort the inbox notes".
    0 installs
24. ▌
    Brain Search · msolecki

    Search the user's Obsidian knowledge vault for earlier decisions, lessons, and references on a topic, and answer only from the notes found, citing their paths. Use before a large task when a `Brain vault:` line is configured, when the user asks "what did we decide about X", or when the user asks you to search the brain, vault, or knowledge base, for example "what do we know about X?", "what did we agree on X", "search the brain".
    0 installs
25. ▌
    Client Reply · msolecki

    Draft a reply to a client's feedback round or business question in plain, non-technical business language, in the user's language and voice. Drafts only and never sends. Use when the user asks to answer a client or turn technical notes into a message for one, for example "reply to the client", "write to the client", "put this in plain language", "answer the feedback".
    0 installs
26. ▌
    Project Init · msolecki

    Adopt developer-os in a repository in one pass — detect the stack, pick the skills that apply, run project-baseline, docs-sync and instruction-review, audit the code against each applicable conventions skill, then give one report and one approval; for a code audit alone, audit-to-backlog. Use when starting with developer-os in a repository, for example "init developer-os here", "check the whole project", "set the repo up for developer-os".
    0 installs
27. ▌
    Brain Capture · msolecki

    Save a decision, a lasting lesson or a reference from the current session as a new inbox note in the user's Obsidian knowledge vault, with secrets redacted. Use when the user says "capture", "remember this", "save this to the brain/vault", or when a session produced a decision or lesson worth keeping.
    0 installs
28. ▌
    Brain Compile · msolecki

    Synthesize several notes on one topic from the user's Obsidian knowledge vault into one compiled inbox note that lists its sources. Use when the user asks to compile or consolidate what the brain/vault knows about a topic, for example "gather everything on X into one note", "compile the notes on X".
    0 installs
29. ▌
    Session Retro · msolecki bundle

    Wrap up a session - check for uncommitted, unpushed or unmerged work, open PRs and running background tasks, propose cleanup, give a Done / Not done / Needs you status, update or close the plan, and propose at most a few lessons, rules or skill ideas to keep, applying only what the user approves. Use at the end of a session, when the Stop hook asks for it, or when the user says "wrap up the session", "clean up after the session", "we are done for today". Unlike the built-in /recap summary, it checks git state and routes lessons to their destination.
    0 installs
30. ▌
    Parallel Lanes · msolecki

    Run independent tasks as parallel headless Claude Code lanes, one git worktree and branch each, show their progress as one table, and integrate the finished lanes into a local branch after approval. Use when the user wants several tasks done at once or asks about running lanes, for example "run these in parallel", "split this into lanes", "how are the lanes doing", "lane status".
    0 installs
31. ▌
    Audit To Backlog · msolecki

    Run parallel specialist reviews of a repository, require file-and-line evidence, deduplicate findings, and write an implementation-ready backlog; for missing practices, project-baseline. Use for a broad codebase audit that should produce a task backlog, for example "audit this repo", "audit the code", "scan the repo and build a backlog".
    0 installs
32. ▌
    Deploy Checklist · msolecki

    Produce a repository-specific deployment checklist with a pre-deploy GO/NO-GO verdict and post-deploy checks covering validation, migrations, feature flags, monitoring, communication, and rollback. Use when the user plans a deployment, release to production, or shipping event, for example "we are deploying to production", "deploy checklist", "can we deploy".
    0 installs