Repository navigation
Conversation
New-tool requests were free-form, so the checks CLAUDE.md already demands (placement, headless safety, end-state verification) got re-derived or skipped per issue. A template makes the sections explicit and gives a filler tool fixed headings to write into. Markdown template rather than a YAML issue form: forms only apply in the web UI, while fixed `##` headings are plain text that can be filled through the API or `gh` by section. Sections: what / why / how / verify. `verify` is its own section, not a line in `how`, because it is an acceptance criterion: a passing switch does not prove a binary landed on the login PATH (#32). The baseline is always present; tool-specific checks are added where they exist, and unverifiable items are listed rather than left blank. Specific changes: - .github/ISSUE_TEMPLATE/new-tool.md: template with `new-tool` label - blank issues stay allowed (no config.yml), so backlog issues are unaffected Co-Authored-By: Claude Sonnet 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_014ctTM9ShmZvCpEmMKEdHvP
Contributor
⊕ Entity-level changes.github/ISSUE_TEMPLATE/new-tool.md
Summary: 5 added across 1 file functions and classes, not lines · sem |
6 of 9 tasks
Filling the template in for superfile (#199) turned up three prompts that were missing or too vague. Changes: - what: ask for the binary name when it differs from the project name. superfile installs `superfile` while its docs say `spf`, so a `verify` that trusted the project name would have checked the wrong command. The verify baseline now says <binary> rather than <tool>. - how/source: compare three points, not "master if stale": the locked rev, nixos-unstable head and master. The result picks the fix. Locked behind with unstable current is a stale lock (`nix flake update`); unstable and master both behind is nixpkgs lagging (vendor input or pin-forward). superfile was the first kind; weave and crush are the second, and the two cases are different PRs. - how/constraints: add a checkbox for network calls at startup or exit (update checks, telemetry). superfile checks for updates on exit by default, and nothing in the template would have asked. Co-Authored-By: Claude Sonnet 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_014ctTM9ShmZvCpEmMKEdHvP
alycda
added this pull request to stack #200
October 3, 2026 09:07
Owner
Author
|
see #162 description |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds
.github/ISSUE_TEMPLATE/new-tool.md, a template for requesting a new tool, with four sections:what,why,how,verify.New-tool requests were free-form, so the checks CLAUDE.md already demands (placement, headless safety, end-state verification) were re-derived or skipped per issue. The template makes them explicit and gives a filler tool fixed headings to write into.
Decisions
##headings are plain text that can be filled through the API orghby section.verifyis its own section, not a line inhow. It is an acceptance criterion: a passing switch does not prove a binary landed on the login PATH (Install lazydiff via official script on work profile #32). The baseline check is always present, tool-specific checks are added where they exist, and anything unverifiable is listed rather than left blank.howprompts encode CLAUDE.md placement rules (core-packages.nixvs profile vs module vs cask) and the headless-container constraints. If that is too heavy per issue,howcan shrink to placement and source.config.yml, so blank issues stay allowed and the existing backlog is unaffected.Before merge
new-toollabel must exist in the repo, or GitHub drops it silently.Test plan
new-toollabel is applied🤖 Generated with Claude Code
https://claude.ai/code/session_014ctTM9ShmZvCpEmMKEdHvP
Generated by Claude Code