← all publishers

jbaehne

@jbaehne source repo

Report this profile Claim this profile

• 6 skills
• 0 followers
• 2 days ago last updated

1. ▌
   Test Design · jbaehne

   Design risk-based tests for changed behavior and separate meaningful gaps from tests that only mirror the implementation. Use when asked which tests to add or how to verify a change. Do not use to issue a merge ruling or to claim checks passed without running them.
   0 installs
2. ▌
   Change Planning · jbaehne

   Turn a requested change into a bounded plan with acceptance criteria, risks, validation, and stop conditions. Use when the user asks for a plan, approach, or design and has not asked to edit code. Do not use to implement, commit, or approve the change.
   0 installs
3. ▌
   Implement Change · jbaehne

   Implement an explicitly authorized plan as the smallest coherent change, preserving unrelated work and local conventions. Use when the user asks to implement, apply, or make a specified change. Do not use for planning-only requests, merge approval, commits, pushes, or deploys.
   0 installs
4. ▌
   Pr Review Ruling · jbaehne bundle

   Review GitHub pull requests or GitLab merge requests and produce a verdict-first, evidence-based review. Use when asked to inspect a PR, MR, branch diff, patch, or proposed code change for merge readiness. Do not use for implementing the changes unless the user separately asks for fixes.
   0 installs
5. ▌
   Repository Archaeology · jbaehne

   Discover repository structure, local instructions, canonical commands, and the Git change boundary before planning or editing. Use when entering a repository, when conventions are unknown, or when asked to map the repo or inspect working-tree state. Do not use to implement changes, write the implementation plan, or rule on merge readiness.
   0 installs
6. ▌
   Chief Of Staff · jbaehne bundle

   Maintain operational awareness across conversations, projects, email, and Slack; track commitments and open loops; prioritize work; produce executive briefings. Use when the user asks for a briefing, what to work on next, commitment tracking, open-loop review, or chief-of-staff support.
   0 installs