Profile My skills Saved Collections Edit profile Submit a skill

← all publishers

jamiebrynes7

@jamiebrynes7 source repo

16 published skills

  1. ▌
    Write Changelog · jamiebrynes7
    Write or update changelog entries with user-focused language
    0
    installs
  2. ▌
    Write Git Commit · jamiebrynes7
    Create a git commit following repository conventions
    0
    installs
  3. ▌
    Whats Next · jamiebrynes7
    Use when the user asks what to work on next ("what's next?", "what should I pick up?", "anything ready?"). Surfaces in-progress and ready beans, grouped by parent with real blocker/container status, recommends a starting point, and hands off to task-implementer on selection.
    0
    installs
  4. ▌
    Diff Scope · jamiebrynes7
    Determine which git diff to analyze based on the user's request. Supports current diff, most recent commit, or current branch.
    0
    installs
  5. ▌
    Task Implementer · jamiebrynes7
    Use when asked to implement a bean, work on a bean, or pick up a task by its bean id (e.g. "implement dotfiles-4byb", "work on this bean"). Drives the full loop — read, validate, branch, implement, subagent review, user review, then land via a PR with auto-merge.
    0
    installs
  6. ▌
    Brainstorming · jamiebrynes7 bundle
    You MUST use this before any creative work — creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements, and design before implementation; uses plannotator for structured option/spec review and hands off to writing-plans for execution decomposition.
    0
    installs
  7. ▌
    Writing Plans · jamiebrynes7 bundle
    Use when you have a spec or requirements for a multi-step task, before touching code. Decomposes the spec into bite-sized TDD tasks; emits a beans hierarchy (epic / feature / task) when the beans CLI is available, otherwise a markdown plan.
    0
    installs
  8. ▌
    Comment Cleanup · jamiebrynes7
    Analyze and clean up code comments for accuracy, completeness, and long-term maintainability. Use when the user asks to review or clean up comments, after generating documentation, or before finalizing a pull request with comment changes.
    0
    installs
  9. ▌
    Devils Advocate · jamiebrynes7 bundle
    Challenges AI-generated plans, code, designs, and decisions before you commit. Pairs with any other skill as a review layer. Uses pre-mortem analysis, inversion thinking, and Socratic questioning to find what AI missed — blind spots, hidden assumptions, failure modes, and optimistic shortcuts. The skill that asks 'are you sure about that?' so you don't have to.
    0
    installs
  10. ▌
    Coding Effectively · jamiebrynes7 bundle
    Always use this skill when writing or refactoring code. Covers general code design, error handling, file organization, and code style patterns.
    0
    installs
  11. ▌
    Critical Code Reviewer · jamiebrynes7 bundle
    Conduct rigorous, adversarial code reviews. Use when users ask to "critically review" my code or a PR, "critique my code", "find issues in my code", or "what's wrong with this code". Identifies security holes, lazy patterns, edge case failures, and bad practices. Scrutinizes error handling, type safety, performance, accessibility, and code quality. Provides structured feedback with severity tiers (Blocking, Required, Suggestions) and specific, actionable recommendations.
    0
    installs
  12. ▌
    Writing Claude Md Files · jamiebrynes7
    Use when creating or updating CLAUDE.md files for projects or subdirectories - covers top-level vs domain-level organization, capturing architectural intent and contracts, and mandatory freshness dates
    0
    installs
  13. ▌
    House Style Code Comments · jamiebrynes7
    Use when writing, reviewing, or cleaning up code comments. Defines which comments earn their place - why-not-what, the categories that always get removed, and the few kinds worth keeping.
    0
    installs
  14. ▌
    Writing Claude Directives · jamiebrynes7
    Use when writing instructions that guide Claude behavior - skills, CLAUDE.md files, agent prompts, system prompts. Covers what earns a place in a directive, token budgets, compliance techniques, discovery, and skill portability.
    0
    installs
  15. ▌
    Maintaining Project Context · jamiebrynes7
    Use when completing development phases or branches to identify and update CLAUDE.md or AGENTS.md files that may have become stale - analyzes what changed, determines affected contracts and documentation, and coordinates updates
    0
    installs
  16. ▌
    Plannotator User Code Review · jamiebrynes7
    Request a code review from the user via plannotator. Use at the end of an implementation task, or when the user asks for a review cycle. Collects structured annotations, then addresses each item.
    0
    installs