timmo001
@timmo001
Public Skills
chill
by timmo001
Stop overengineering and reinventing the wheel. Use ONLY when the user explicitly invokes /chill or asks to simplify an approach that has become unnecessarily complex.
gh-stack
by timmo001
Manage stacked branches and pull requests with GitHub's gh stack extension. Use when work involves stacked PRs, dependent branches, stack creation, navigation, submission, synchronisation, rebasing, restructuring, linking, or merging.
release-oxlint-rules
by timmo001
Create and publish a major, minor, or patch release of @timmo001/oxlint-rules. Use when asked to create, cut, prepare, or publish an oxlint-rules release, including its version bump and npm and JSR publication.
agentic-workflows
by timmo001
Design, create, update, debug, audit, or upgrade GitHub Agentic Workflows with the gh aw extension. Use when work involves workflow Markdown, compiled .lock.yml files, agent engines, MCP tools, safe outputs, or gh aw commands.
add-oxlint-rule
by timmo001
Create or revise a centrally maintained rule in @timmo001/oxlint-rules. Use for requests to add an Oxlint anti-slop rule, change an existing central rule, or promote a repository-specific lint preference into the shared package.
to-questionnaire
by timmo001
Turn a decision the user cannot answer alone into a channel-aware questionnaire draft for one other person. Use when missing knowledge belongs to a colleague, maintainer, or domain expert and the user needs questions for GitHub, Slack, Discord, or a document.
show-me
by timmo001
Explain the current topic with a concise visual such as a tree, diagram, diff, or focused HTML artefact. Use ONLY when the user explicitly asks to see, visualise, diagram, sketch, or be shown the preceding explanation.
ask-questions-if-underspecified
by timmo001
Ask minimal clarifying questions only when ambiguity materially changes implementation. Use for routine underspecification; do not use for user-requested light or full grilling, plan stress-testing, or broad design interviews.
bro
by timmo001
Re-pitch the immediately preceding response with enough context to follow, using plain, concise, unambiguous language. Use ONLY when the user explicitly invokes /bro or says the previous response did not land.