dogkeeper886
- 15 skills
- 0 followers
- 1 week ago last updated
- ▌ Reviewing Artifacts · dogkeeper886Gates the tooling an agent reads — skills, commands, rules, CLAUDE.md — asking whether the file has one clear job, delivers it end to end, leaves the choices the project owns to the project, matches the repo as it actually is, and can be followed without guessing. Returns PASS, REVISE or CUT. CUT is the verdict nothing else makes: this artifact duplicates another or does nothing, and should be removed.
- ▌ Reviewing Typography · dogkeeper886Reviews how a human-read document looks — a README, prose and tables in docs/, an HTML page — and returns PASS or REVISE. Works the way a UI designer does: group the content, space the groups so the inner gap is smaller than the outer one, emphasize by dimming what is not the point rather than shouting what is, hold the level count low, and judge the page whole rather than section by section. Judges the look; the words are a separate review.
- ▌ Review Readme · dogkeeper886Gates a README before a person reads it, on three counts: it delivers for a newcomer, it is true to the code, and it reads and looks right. Derives the key points from the code and checks the README leads with them and ships a diagram for each, verifies every command, path, env var and link against the source, and re-renders each diagram to catch one that has drifted from what it is drawn from. Gates what gen-readme wrote, and any README edited by hand.
- ▌ Remove Stale Files · dogkeeper886 bundleFinds and removes what this plugin's earlier versions wrote into a project: forked commands and skills that shadow the placed units, rules and story files nothing reads any more, and the sections this plugin wrote into `project-profile.md`. Shows every file before touching one, and deletes only on a yes. It never adds: every edit it makes is a removal.
- ▌ Reporting Outcomes · dogkeeper886Reports work in two lines and a question — the verdict, the one next step, and whether the reader wants it run or wants the detail. Findings, what was checked, risks and decisions are prepared and held; the reader acts on the next step or asks. Only a blocked or failed next step brings its blocker up with it. Replaces the reply that mixes progress, findings, reasoning and status into a narrative the reader has to mine.
- ▌ Reviewing Phrasing · dogkeeper886 bundleReviews the words of a document a person will read, and returns PASS or REVISE. Starts by establishing what the file actually is and who reads it, because a markdown file carries no contract the way a source file does, and the same wording is correct in a talk track and wrong in a test case. Then runs check-prose.sh to locate the mechanical tells by grep rather than by impression, and judges what a pattern cannot reach.
- ▌ Gen Readme · dogkeeper886Writes a project's README from the code: researches current README convention on the web, studies the repo from its ground truth rather than its existing docs, finds the key points a newcomer needs first, draws every one of them as an SVG rendered to PNG, and writes the file. Produces the README only — it does not open a PR, and review-readme gates what it wrote.
- ▌ Take Issue · dogkeeper886Picks up a tracked issue of any kind and claims it: resolves which one, reads it whole along with the log it links, judges whether it can actually be started, and refuses it back when it cannot. Assigns it, moves the state label, cuts a branch where a diff is coming, and stops before any work begins — so a misreading is catchable while it is still cheap. The read half of an issue; something else does the work.
- ▌ Review Work · dogkeeper886Judges what state finished work is actually in, and routes it there. Checks the acceptance line against the work rather than against the claim about it, sweeps what the change left behind, and sends the result onward, back for more, back to the issue, or up for splitting. Only one of its five outcomes reaches a change request, which is the point of having it.
- ▌ Land Pr · dogkeeper886Merges an approved change request and cleans up after it: the code lands in the default branch, the branch is gone, the issue closes, the labels clear. Asks a person outright whether the change was reviewed and tested at this exact head, records that answer, and pins the merge to that SHA so a head that moved cannot slip through. Refuses to merge without the answer.
- ▌ Open Pr · dogkeeper886Pushes a committed branch and opens the change request that carries it to a human, linked to its issue so the issue closes on merge rather than by hand. Moves the commits onto a branch first when they landed on the default one, gets the closure keyword right, and stops for review. It does not merge, and it does not judge whether the work is good; something before it did that.
- ▌ Plan Work · dogkeeper886Splits work too large for one issue into issues that can each be delivered on their own, and groups them with whatever the project already uses to group things — a milestone, a project board, an epic. Decides first whether splitting is warranted at all, since most work is not, and never invents a grouping the platform already provides.
- ▌ File Issue · dogkeeper886 bundleTurns something said in a session into a tracked issue that a cold agent can act on, and copies the session log beside it wherever one can be had — always attempted, never a reason to withhold the issue. Decides first whether the thing needs tracking at all, searches for an existing issue before creating a second one, quotes the request in the words it was made in rather than paraphrasing it, and states an acceptance test someone else can check. Creates the portal every later step resolves back to.
- ▌ Writing Agent Skills · dogkeeper886Author, review, and refactor Agent Skills — SKILL.md frontmatter, description wording for reliable triggering, progressive disclosure across bundled files, workflow checklists, validator feedback loops, and evaluation-driven iteration. Use whenever the user is writing a new skill, editing or splitting an existing SKILL.md, migrating slash commands or prompts into skills, packaging skills into a plugin, debugging a skill that fails to trigger or triggers too often, or asking how skills should be structured — including when they describe the work as "turn this into a skill" or "make this reusable" without saying the word skill.
- ▌ Do Task · dogkeeper886Does the work a claimed issue describes — writes and commits the change, or performs the act and captures the evidence that it happened. Holds the scope the issue set, records why in the commit message rather than only what, and ends by stating what state the work is actually in rather than declaring it done. The write half of an issue; something else judges whether it finished.