hburaktasyurek

@hburaktasyurek source repo

16 skills
0 followers
11 hours ago last updated

▌
Tdd · hburaktasyurek bundle
Use only when the user explicitly names tdd or an upstream task explicitly invokes it to implement a feature or bug fix test-first. Execute vertical red-green-refactor cycles against the repository's real contract; proceed without redundant approval when an authoritative brief is ready, and stop before writes only when a material behavior, scope, interface, or authority decision remains unresolved.

0
installs
▌
To Spec · hburaktasyurek bundle
Produce an evidence-backed four-file implementation spec for one bounded software change, using consequence-calibrated contract closure so reachable behavior is decided without over-specifying local work. Use when a grounded task must become an implementation handoff. Triggers: to-spec; write the spec; hand this off.

0
installs
▌
Grill Me · hburaktasyurek bundle
Use only when the user explicitly names grill-me or explicitly asks for an interactive grilling of a plan, decision, or idea. Stress-test the decision by resolving facts from available evidence, asking one unresolved decision-changing question at a time, and stopping when no material branch remains; do not implement the plan.

0
installs
▌
Pr Branch · hburaktasyurek bundle
Use when the user explicitly invokes pr-branch or asks to open or refresh a GitHub pull request from the current branch; invocation authorizes opening or updating the matching PR and any necessary non-force push. Produce the fixed two-block format: first make invisible engineering manager-visible through consequence, business breadth, protection, operational capability, and enablement; then preserve the precise technical and test record. Use description-only mode only when explicitly requested.

0
installs
▌
Skill Eval · hburaktasyurek bundle
Use only when explicitly asked to evaluate one repository skill package against its exact old-skill or no-skill baseline. Run the same realistic cases on one named harness and model, judge produced artifacts, and return a current-package PASS, FAIL, NO_LIFT, or INCONCLUSIVE verdict. Do not edit or accept the target package or exercise live consequential systems.

0
installs
▌
Commit Work · hburaktasyurek
Stage intended changes, split into logical commits, and write Conventional Commit messages; push only when the user explicitly asks. Use when asked to commit, commit and push, craft a commit message, stage changes, or split work into multiple commits.

0
installs
▌
Spec Readiness · hburaktasyurek bundle
Check whether a named implementation specification is ready to hand to an implementer without forcing them to invent structural contracts. Use explicitly before implementation handoff to return READY or root-complete NOT READY blockers. Do not use as a runtime correctness or PR merge review.

0
installs
▌
Session Handoff · hburaktasyurek bundle
Use only when the user explicitly names session-handoff or explicitly asks to create a durable resume packet for a later agent session. Capture the exact live state, unresolved work, decisions, constraints, and next action needed to continue without re-deriving context; do not create a packet when there is no actionable state to transfer.

0
installs
▌
Task Groundwork · hburaktasyurek bundle
Use only when the user explicitly names task-groundwork to ground a vague or non-trivial software task before specification or implementation. Investigate the current repository, relevant roadmap context, history, and real-use constraints; resolve technical branches with evidence, expose only genuine human decisions, and return a concise decision-ready brief. Do not use for a narrow task that is already ready for direct execution.

0
installs
▌
Omp Task To Spec · hburaktasyurek bundle
Use only when the user explicitly names omp-task-to-spec. OMP parent spec gate under orchestrate: run the spec path until the same committed revision has adversarial PASS and readiness READY, then stop. Not the child skill to-spec (four-file author). Triggers: omp-task-to-spec; OMP spec gate; orchestrate until the spec is ready. Do not use to write spec files or to implement.

0
installs
▌
Codex Task To Spec · hburaktasyurek bundle
Use only when the user explicitly asks for the Codex task-to-spec gate. Produce and locally commit a grounded four-file spec, then run isolated adversarial and readiness reviews until the deterministic gate stops or needs an owner answer. Do not implement or push.

0
installs
▌
Senior Implementer · hburaktasyurek bundle
Use only when explicitly invoked as `/senior-implementer`, `use senior-implementer`, or equivalent to implement an approved spec or brief, a direct engineering task, a bug fix, or complete review findings end to end. Establish the governing outcome, close task-owned causes across every affected surface, reconcile task-owned contracts when evidence invalidates them, and prove the resulting artifact or state. Do not auto-trigger on bare implement, build, or fix requests.

0
installs
▌
Review Implementation · hburaktasyurek bundle
Review an implemented change against a named specification before opening a PR. Use when the user asks for spec-compliance, implementation-vs-spec, acceptance-criteria, or pre-PR implementation review. Produce an evidence-backed Ready for PR decision without editing project files. Do not use for an opened-PR merge gate.

0
installs
▌
Adversarial Diff Review · hburaktasyurek bundle
Hostile kill-test of an explicit branch/worktree/PR diff against its task definition; P0–P3 with file:line evidence. Use when explicitly requested, especially before a PR exists; the canonical opened-PR shipping gate is risk-calibrated-pr-review. Not named-spec Ready-for-PR or plans/specs. Triggers: adversarial-diff-review.

0
installs
▌
Adversarial Spec Review · hburaktasyurek bundle
Evidence-bounded red-team review that challenges a plan or spec without manufacturing findings. Returns a priority-sorted finding list (P0–P3) with an explicit PASS/FAIL verdict. Use for plans/specs; use risk-calibrated-pr-review for an opened implementation PR, or adversarial-diff-review for an explicitly requested branch/worktree diff.

0
installs
▌
Risk Calibrated Pr Review · hburaktasyurek bundle
Use only when explicitly invoked as `$risk-calibrated-pr-review` or equivalent to independently review a current implementation PR as a read-only hostile merge gate. Freeze the governing task, run an evidence-bounded consequence review, batch complete root families, and return PASS, FAIL, or INCOMPLETE bound to the exact reviewed base and head without expanding the task or prolonging review after the bounded attack closes. Use after a PR exists and for re-review after fixes; not for spec review, implementation, pre-PR compliance, commit-history process analysis, or general PR summaries.

0
installs

16 published skills