← all publishers

alawein

@alawein source repo

Report this profile Claim this profile

• 28 skills
• 0 followers
• 6 hours ago last updated

1. ▌
   Grill · alawein

   Use when a design, plan, or diff needs hostile scrutiny before it is trusted or shipped. It tries to break the design, plan, diff, or claim rather than confirm it, then gives one verdict. Distinct from code-review, which checks correctness.
   0
   installs
2. ▌
   Panel · alawein

   Use when a decision or design benefits from several independent expert perspectives. Convenes distinct expert lenses that each judge the decision on its own, then synthesizes agreements, disagreements, and one recommendation. Distinct from prove and grill.
   0
   installs
3. ▌
   Prove · alawein

   Use when numbers go to stakeholders, a finding is contested, or a claim must survive scrutiny. Proves or refutes many claims by recomputing each from the source of truth and attacking the survivors, then tags every claim with a confidence verdict. The heavier sibling of grill.
   0
   installs
4. ▌
   Triage · alawein

   Use when a findings list (from repo-review, code-review, or a teammate) needs ranking before action. Confirms or doubts each finding against the code, ranks severity, and routes each to fix now, defer, or reject, with a reason. The bridge between finding problems and acting on them.
   0
   installs
5. ▌
   Converge · alawein

   Use when you want to drive an artifact to clean, where clean means zero blockers and zero majors after a full check run. Fix and re-run until clean or a round cap, then report honestly, confirmed minors included. A fix-until-clean loop over lint, tests, review, and scrutiny.
   0
   installs
6. ▌
   Debt Log · alawein

   Use when recording a deliberate shortcut or a known limitation so it is tracked, not silently accrued. Writes one entry with the reason, the cost, and the trigger to revisit.
   0
   installs
7. ▌
   Simplify · alawein

   Use when changed code works but carries duplication, needless indirection, or waste. Finds and applies reuse, simplification, and efficiency cleanups that preserve behavior. It does not hunt bugs (code-review does) and it is not a planned reshape (refactor-safely is).
   0
   installs
8. ▌
   Premortem · alawein

   Use before committing to a plan that is expensive to reverse. Assume it already failed, work backward to the likely causes, and turn the top ones into preventive actions to take now.
   0
   installs
9. ▌
   Write Doc · alawein

   Use when writing a named coding artifact (a README, a findings note, a report) in the house voice from a supplied template. Produces a findings-first document with the right structure for its kind, plain words, and no padding.
   0
   installs
10. ▌
    Prepare Pr · alawein

    Use when a branch is ready for review. Drafts the commit, the PR title and body, the testing notes, and the risks from the diff, and runs the pre-merge checks.
    0
    installs
11. ▌
    Code Review · alawein

    Use on a diff or a branch before a PR. A structured correctness-and-standards review that catches the expensive-to-fix issues and gives one honest verdict.
    0
    installs
12. ▌
    Interrogate · alawein

    Use when a request is vague and you are about to build. Show the hidden assumptions and the success test with sharp questions before any code, so the change is not scoped wrong from the start.
    0
    installs
13. ▌
    Orient Repo · alawein

    Use on first contact with an unfamiliar repo, before planning a change. Builds a read-only map of how the project is built, tested, and laid out, so the first plan rests on facts, not guesses.
    0
    installs
14. ▌
    Plan Change · alawein

    Use before writing code for any non-trivial change. Turns a request into a short, concrete plan grounded in the actual repo, so the edit is scoped before a line is touched.
    0
    installs
15. ▌
    Repo Review · alawein

    Use when a whole repo needs a health audit before you trust or own it. Judges structure, docs truth, test coverage, dead code, and drift between docs and code, then emits findings shaped for triage. An opt-in ownership lens hunts single-owner assumptions when a one-person repo becomes a team surface. Distinct from orient-repo, which maps a repo without judging it.
    0
    installs
16. ▌
    Risk Review · alawein

    Use before merging a change to install.py, kit/installers/, or kit/adapters/ write paths, or anything the author names as hard to reverse. Gates the verdict on actually attacking the claims the risky part depends on, not just reading them. Distinct from code-review, which does not require that.
    0
    installs
17. ▌
    Self Refute · alawein

    Use right after you produce an answer, plan, or design that matters, to attack your own output before presenting it. A reflexive red-team that hardens the result instead of defending it.
    0
    installs
18. ▌
    Write Tests · alawein

    Use when adding coverage for new or uncovered code. Generates tests that assert the behavior and the contract, not implementation detail, and that actually run.
    0
    installs
19. ▌
    Check Intent · alawein

    Use right after implementation is done and before code-review, to reconcile the diff against the plan or the stated ask. Catches a dropped plan item, an unrelated file change, or a silent switch to a different approach before either ships unnoticed.
    0
    installs
20. ▌
    Split Change · alawein

    Use when a change has grown to do more than one thing. Detects the separable concerns and splits them into focused commits or PRs, so each is small, reviewable, and revertible on its own.
    0
    installs
21. ▌
    Debug Failure · alawein

    Use when a test fails or an error is unclear. A hypothesis-first loop that reproduces the failure, finds the root cause, fixes it, and pins it with a regression test.
    0
    installs
22. ▌
    Cross Doc Check · alawein

    Use when two docs are each supposed to state the same policy or rule, to check whether they actually agree. Flags a real contradiction or an unexplained scope gap, never a wording difference where the substance already agrees. Distinct from doc_truth, which checks that a named reference resolves, not whether two docs agree with each other.
    0
    installs
23. ▌
    Handoff Session · alawein

    Use when wrapping a work session or passing work to another agent, or to re-ground a drifting long task mid-flight. Produces a short handoff so the next session resumes with no context loss.
    0
    installs
24. ▌
    Record Decision · alawein

    Use when recording an architecture or structural decision. Captures the context, the decision, and the consequences as a short, append-only record so the why survives.
    0
    installs
25. ▌
    Refactor Safely · alawein

    Use when restructuring code for clarity without changing behavior. Names the before and after and proves the same tests pass before and after the change.
    0
    installs
26. ▌
    Implement Change · alawein

    Use when executing an approved plan. Makes the smallest correct edits in order, follows the repo's existing patterns, and keeps the tree runnable at each step.
    0
    installs
27. ▌
    Respond To Review · alawein

    Use when acting on review feedback on your change. Triages each comment, fixes or pushes back with a reason, and replies so the loop closes before merge. Distinct from code-review, which gives the review.
    0
    installs
28. ▌
    Repo Hygiene Sweep · alawein

    Use when several repositories need a read-only hygiene sweep before any repair work begins. Inventories the fleet, proves each finding from its source, and routes safe work without mutating protected targets.
    0
    installs