dkenge123-oss
- 16 skills
- 0 followers
- 7 hours ago last updated
- ▌ API Design · dkenge123-ossUse when designing a new API, library interface, or function signature that others will call. Optimizes for the caller's experience and for change over time, because an interface is a promise that is expensive to break.
- ▌ Test First · dkenge123-ossUse when implementing any feature or bugfix in a codebase with a test suite. Enforces red-green-refactor so the test proves the change instead of decorating it.
- ▌ Code Review · dkenge123-ossUse when reviewing a diff, branch, or pull request. Runs a severity-ranked review that surfaces real defects first and suppresses style nitpicks unless asked.
- ▌ Pr Narrator · dkenge123-ossUse when opening a pull request or asked to describe a branch. Turns the full branch diff into a PR description a reviewer can act on in one read.
- ▌ Cold Outreach · dkenge123-ossUse when writing a cold email or first-touch outreach message. Enforces research-first, one-ask messages that earn a reply instead of getting deleted, and refuses to fabricate personalization.
- ▌ Daily Standup · dkenge123-ossUse when asked for a standup update, status summary, or "what did I do yesterday". Builds the update from actual git and task activity instead of memory.
- ▌ Deep Research · dkenge123-ossUse for research questions that deserve more than one search, including market scans, technical comparisons, and due diligence. Enforces multi-source gathering and claim verification before synthesis.
- ▌ Readme Writer · dkenge123-ossUse when writing or overhauling a project's README. Produces a README that gets a project understood and used in under a minute, grounded in what the code actually does.
- ▌ Release Notes · dkenge123-ossUse when cutting a release or asked what changed between two versions. Converts raw git history into release notes organized by user impact, not by commit order.
- ▌ Safe Refactor · dkenge123-ossUse when restructuring code without changing its behavior. Keeps refactors reversible and behavior-preserving so cleanup never becomes an accidental rewrite that breaks things.
- ▌ Prompt Refiner · dkenge123-ossUse when a prompt, system prompt, or agent instruction is underperforming and needs improvement. Applies a diagnostic rubric and rewrites with measurable changes instead of vibes.
- ▌ Decision Record · dkenge123-ossUse when capturing a significant technical or product decision. Produces a short architecture-decision-record (ADR) that records the context and the alternatives, so future readers understand why, not just what.
- ▌ Meeting To Actions · dkenge123-ossUse when turning a meeting transcript or messy notes into an outcome. Extracts decisions, owned action items, and open questions, and throws away the noise nobody needs to reread.
- ▌ Incident Postmortem · dkenge123-ossUse after an outage, regression, or production incident to write a blameless postmortem. Produces a timeline, root cause, and concrete action items instead of a vague "we'll be more careful".
- ▌ Conventional Commits · dkenge123-ossUse when committing changes to git. Analyzes the staged diff, splits unrelated changes into separate commits, and writes conventional commit messages that explain why, not just what.
- ▌ Systematic Debugging · dkenge123-ossUse when chasing a bug, crash, or "it works on my machine" mystery. Enforces hypothesis-driven debugging so you fix the actual cause instead of the first thing that looks wrong.