gitt510

@gitt510 source repo

19 skills
0 followers
4 hours ago last updated

▌
Ponytail Review · gitt510 bundle
Code review focused exclusively on over-engineering. Finds what to delete: reinvented standard library, unneeded dependencies, speculative abstractions, dead flexibility. One line per finding: location, what to cut, what replaces it. Use when the user says "review for over-engineering", "what can we delete", "is this over-engineered", "simplify review", or invokes /ponytail-review. Complements correctness-focused review, this one only hunts complexity.

0
installs
▌
Dads · gitt510 bundle
Reference knowledge for the Digital Agency Design System (DADS, デジタル庁デザインシステム): pinned design tokens, official dads-* component markup and porting rules, curated usage guidelines, and compliance policy. Use whenever output should look DADS-compliant — building a new page, artifact, or HTML document in DADS style, restyling an existing frontend to DADS (「DADS 風に」「デジタル庁デザインシステム準拠に」「デジタル庁っぽく」), auditing markup against official DADS components, or fetching DADS tokens/components from primary sources. This skill owns only the visual layer — colors, typography, components, usage rules, policy — and composes with whatever owns structure and medium (artifact-design, holy-grail-html, a React app, plain HTML edits). Triggers on "DADS", "デジタル庁デザインシステム", "dads-*", "digital-go-jp", "Japanese government design system".

0
installs
▌
Tmux · gitt510 bundle
Control tmux panes for interactive CLIs: capture pane output and send keys/text. Targets the current window by default.

0
installs
▌
Handover · gitt510
Record task- or topic-level progress into a single HANDOVER.md. Use when updating a handover, logging progress, or summarizing work to hand off.

0
installs
▌
Init Repo · gitt510
Initialize a brand-new GitHub repository and land in a ready-to-work checkout: create the remote with gh repo create, clone it under the ghq root, push a single empty "chore: init" commit as main's root, then cut a fixed `bootstrap` branch and stop there. Use when starting a repository from zero ("new repo", "repo 作って", "リポジトリ新規作成"). Init only — no README/LICENSE scaffolding, no PR, no CI or branch protection; those belong to later steps on the bootstrap branch.

0
installs
▌
Yt Digest · gitt510 bundle
Summarize a YouTube video from its transcript (subtitles) fetched with yt-dlp, without watching it; never downloads the video or audio. Use when a YouTube URL (youtube.com / youtu.be) is shared and the user wants the content, key points, or a transcript — including vague asks like "what's this about?" as long as the target is a YouTube video.

0
installs
▌
Publish Pr · gitt510
Publish the current local changes to GitHub in one shot — confirm scope, commit, push, and open a ready pull request. Use whenever the user wants to ship finished local work to a PR ("open a PR for this", "publish this", "commit, push, and PR", "ship it"), even when the ask is terse, as long as there are local changes meant to go up. This is git + PR mechanics only: it does NOT merge (stop at opening the PR) and does NOT run tests/build/lint (correctness is a separate concern — see the boundary notes below).

0
installs
▌
Build Readme · gitt510 bundle
Write a README from scratch or fully rebuild one. Collects observable facts from the system itself (code, terraform, actual behavior), composes sections from those facts, and writes one fact per bullet; decision rationale and internal how-it-works are left out. An existing README is broken down sentence by sentence and only facts verifiable against the implementation survive. Use when creating, rewriting, condensing, or restructuring a README. Not for a few added lines to an existing README — a normal edit covers that.

0
installs
▌
Create Issue · gitt510
File a GitHub issue with gh issue create, using a Conventional Commits prefix and a flat Problem / Impact / Notes skeleton. Create-only — no edit, close, or status lifecycle. Use when opening a new issue on a remote repository.

0
installs
▌
Mouse Doctor · gitt510
Diagnose and recover mouse clicks that suddenly stop working across macOS apps in setups using LinearMouse or Karabiner-Elements. Inspect system load and the relevant input processes before restarting anything, then restore them in priority order. Use when clicks stop responding app-wide and at least one of those tools is installed.

0
installs
▌
Weed Comment · gitt510
Remove context-leak prose from comments and docstrings in AI-agent-written code: edit-history narration, reviewer-directed self-justification, session references, redundant code restatement, and commented-out code. Preserve durable contract documentation, constraints, non-obvious rationale, business rules, TODO/FIXME, and tool directives. Use after an agent coding session, before committing agent-written changes, when a diff review flags comment noise, or when the user says "clean up the comments", "remove AI comments", "comment slop", "コメント整理して", "コメント抜いて", or invokes /weed-comment. Edit comments and docstrings only; never change executable code or perform a general simplify pass.

0
installs
▌
Coherence Map · gitt510
Map a codebase's implicit design decisions as questions and answers, and surface where the same question is answered differently in different places (forked error-handling shapes, competing data-fetching strategies, parallel helpers that diverge). Each question gets a state — unified / forked / documented-fork — and the map accumulates in the target repo's docs/coherence-map.md so later runs and reviews can check new code against recorded decisions. Use when the user wants to audit coherence, inventory design decisions, hunt slop debt, asks 「設計判断を棚卸しして」「coherence-map 作って/更新して」 "where is this codebase incoherent", or before letting an agent make broad changes to an unfamiliar repo. Detection and decision-demand only — it never applies fixes; over-engineering hunting belongs to ponytail-review, correctness to a normal review.

0
installs
▌
Build Justfile · gitt510 bundle
Create or fully restructure a justfile so its recipes follow the de-facto conventions of prominent open-source justfiles. Use when writing a new justfile, cleaning up or normalizing an existing one, or porting a Makefile to just. Not for adding a recipe or two to an existing justfile — a normal edit covers that.

0
installs
▌
Oss Bus Factor · gitt510 bundle
Estimate an open-source project's bus factor from public GitHub data alone, across three axes (org metadata, commit cadence, PR-merger distribution), and produce a governance / activity note for adoption decisions or PR comments. Use when assessing a project's continuity, maintenance health, or whether it is effectively dead, or comparing several projects on governance or maintainership. Triggers on "bus factor", "maintenance health", "is this OSS dead".

0
installs
▌
Add Google Task · gitt510
Add a single task to the default Google Tasks list with gog tasks add. Derives the title, due date, and notes from conversation context instead of interrogating the user, confirms a human-readable summary before writing, and never encodes account or list identifiers. Add-only — no list, update, complete, or delete. Use when the user asks to put something on their tasks or todo list, e.g. "add X to tomorrow's tasks", 「X を明日の task に追加しておいて」.

0
installs
▌
Holy Grail HTML · gitt510
Build a standalone, self-contained HTML document using the Holy Grail layout — a full-width masthead on top, then three columns: a sticky auto-generated contents-tree (TOC) that tracks scroll on the left, the body in the center, and a manual Related links rail on the right. Writes the result to {slug}.html in the directory the skill is invoked. Use whenever the user wants a navigable reference, guide, explainer, or spec as an HTML file that would benefit from in-page navigation. It owns the navigation structure; for visual direction it invokes frontend-design, and for up-to-date HTML/CSS practice it invokes modern-web-guidance. Triggers on "holy grail layout", "3-column reference html", "doc with a table of contents", "scroll-tracking TOC".

0
installs
▌
List Google Tasks · gitt510
List tasks from the default Google Tasks list with gog tasks list, read-only by mechanism (--readonly blocks mutating API calls at runtime). Derives filters — due window, completed or not — from conversation context, then presents the tasks human-readably and stops; it never completes, edits, or adds anything. Use when the user wants to see their tasks or plan around them, e.g. "what's on my tasks today?", 「google の task みれる？」「今日が期限のもの消化したい」 — even when the eventual goal is to work through tasks, fetching them starts here.

0
installs
▌
Build Pr Description · gitt510 bundle
Write a PR description from scratch or fully rebuild an existing one. Why is written as an argument — the claims that make the change necessary, each backed by verifiable facts — and What / Test / Notes carry only the facts a reviewer needs to read the diff. Claims and facts are gathered from the diff, commits, and conversation; an existing body is broken down sentence by sentence and only what survives verification is kept. Use when creating or rewriting a PR body, including when running gh pr create or gh pr edit. Not for a few added lines to an existing description — a normal edit covers that.

0
installs
▌
Github Pr Reply Guard · gitt510 bundle
Operational guard against replying to the wrong thread when responding to GitHub PR review comments. Use when replying to review comments, reporting fixes, or resolving threads — especially when a comment URL and comment ID are involved: confirm the ID from pulls/:pr/comments and verify in_reply_to_id after replying. Also covers the GraphQL fallback for when a pending review makes the REST reply API fail.

0
installs

19 published skills