Repository navigation
Releases
v1.6.0 · Build Local removed
Removed
build-local. Ask your coding agent for a browser preview of the current changes, and it starts the project's development server and checks the page without a skill.executestill opens a preview of viewable changes when it finishes.
Updating existing repositories
npx skills update leaves the removed skill installed and reports it as failed. To remove it, run:
npx skills remove build-localAdd -g if you installed the skills globally.
v1.5.6 · Reliable tracker reads and fresh subagents
Fixed
- The GitHub tracker template that
setup-snappedly-skillswrites reads an issue as JSON with its title, state, body, labels, and comments. Outside a terminal,gh issue view --commentsprints only the comments, so agents missed the issue's title, body, and labels. To close an issue, the template posts the comment first and then closes it, becausegh issue close --commentdrops the comment on an issue that is already closed. setup-snappedly-skillscreates the triage and category labels its mappings name when the tracker lacks them, so applying a triage state no longer fails on a missing label. The code host template asks for a change-request read that returns the title and body as well as the comments.- When
diagnosing-bugsortddforces a failing test by mutating code or a fixture, it diffs the file against a pristine copy to prove the mutation landed before it trusts the failure. A mutation command can exit successfully and change nothing.
Changed
execute,code-review,codebase-design,improve-codebase-architecture,research, andgrillstart each subagent they launch with a fresh context window, not a fork of the conversation. Some harnesses fork by default, which gives a subagent the context it exists to avoid.help-snappedlyapplies the same rule to delegated work, andwriting-for-agentstells skill authors to state it.code-reviewsearches the repository for its standards sources instead of relying on documents already read. An existingCODING_STANDARDS.mdorCONTRIBUTING.mdis always a source.grillwords each question so that "yes" accepts its recommended answer.- When
tddasks which seams to test, it notes for each proposed seam what a test there catches and what it misses. executestates the title of a named issue before it continues, and asks when the reference matches no item or more than one.help-snappedlyreads a skill'sSKILL.mdbefore it states what the skill does or recommends skipping one of its steps.- The GitHub tracker template notes that
gh2.94 and later handles sub-issues and blocking relationships natively, and that reading an issue's blockers also lists closed ones.
Updating existing repositories
Rerun setup-snappedly-skills to replace the issue read and close operations in docs/agents/issue-tracker.md and to create any missing triage and category labels. Setup also replaces a change-request read in docs/agents/code-host.md that relies on --comments.
v1.5.5 · Quick approval for retro recommendations
Changed
retroends its report with a horizontal rule and a Recommended changes section. It numbers the proposed changes in the same order as the findings, with one plain-language line per change that says what to change and where. You can reply "fix all" or name the numbers to apply, andretromakes those changes. When your original request already askedretroto make the changes, it applies them without the list.
v1.5.4 · Triage before execute
Changed
executetriages a named issue in theneeds-triagestate before carrying it out. It applies thetriageprocess for a specific issue. When the issue is ready for an agent,triageposts its brief and updates its category and state roles on the tracker beforeexecutebuilds the plan. Planning specs receive the roles without an executable brief. When triage recommends another state, such asneeds-infoorwontfix,executestops with the recommendation, applies only the outcome you choose, and continues only when the issue reachesready-for-agent. On a planning spec,executealso triages every open ticket in theneeds-triagestate, including blocked ones. A ticket that reachesready-for-agentjoins the plan once its blockers have closed; any other ticket stays out, and the report gives triage's recommendation for it. Withouttriageinstalled,executestops and reports which issues need triage.triagenow supports model invocation in Claude Code and Codex soexecutecan load it as a dependency from thesnappedly/skillspackage.
v1.5.3 · Clear status for follow-up reports
Fixed
- After
clean-uporcodebase-cleanup, when you ask the agent to act on the Decisions needed and Gaps to check items, it reports each item under its current status: Done, Handed off (with where it is tracked), Accepted, or Still open. Each item starts with its outcome. Previously, the follow-up report could reuse "Decisions" and "Gaps" headings, so fixed items looked open. An item counts as done only once its decision is applied or what it named is verified. A gap left for someone else to verify is listed as handed off.
v1.5.2 · Decisions and gaps before you deploy
Changed
clean-upandcodebase-cleanupend their report with a horizontal rule and a Check before you submit or deploy section, so open items are not lost in the longer report. It has two numbered lists in plain language. Decisions needed gives each choice left to you, with its options and a recommendation. Gaps to check gives each thing left unverified, such as a failing or skipped check or an uninspected area, with its risk, the ways to close it when there is more than one, and a recommendation. An empty list says "None". Open findings appear only in that section, rather than also in the body of the report.
v1.5.1 · Execute dependency provenance
Security
executestates that its dependencies,code-cleanup,code-review, andtdd, come from the samesnappedly/skillspackage asexecuteitself.
v1.5.0 · Specs and tickets for agents
Changed
grillgives theready-for-agentstate to every ticket it publishes, including blocked ones, unless you say otherwise. Without configured triage roles, it applies aready-for-agentlabel and creates the label when the tracker lacks it. The state means a ticket is fully specified, not that its blockers have closed.executeon a spec still runs only the tickets whose blockers have closed.grillrecords blockers through the native blocking operations configured inissue-tracker.md, such as GitHub issue dependencies. Without those operations, it writes a## Blocked bysection.executereads native links when configured and any existing## Blocked bysections, so older tickets keep their dependencies.grillalso gives theready-for-agentstate to a spec it creates. On a spec, the state means/executeon the spec can carry out its unblocked tickets, and the spec stays non-executable.triageapplies the state to a spec without an agent brief, since a brief marks an item executable.- When
grillstarts from an existing tracker issue, that issue becomes the parent. Each ticket becomes its child, andgrillposts the spec as a comment on it instead of creating a separate spec.grillnever edits or closes that issue.
Added
grilllooks for refactors that make a slice easier to build. Each refactor goes at the start of the first slice that needs it. The ticket requires behavior to stay unchanged and the relevant checks to pass before the slice adds new behavior. A refactor gets its own ticket ahead of the tracer bullet only when every approach needs it and it is too large to review inside the tracer bullet.grillsplits a wide refactor, such as renaming a column used across the codebase, into expand, migrate, and contract tickets: add the new form, move the callers over in batches that each pass the checks, then remove the old form.
Updating existing repositories
Rerun setup-snappedly-skills to add the Blocking relationships section to docs/agents/issue-tracker.md and to let its planning spec mapping accept a spec comment and the ready-for-agent state. Until then, grill writes blockers as ## Blocked by sections.
v1.4.5 · Isolated checks and resumable validation
Fixed
executeworkers can run focused checks and prerequisite builds in parallel when their resources are isolated. Required full suites and final builds run on the combined change, unless repository policy requires them earlier.code-cleanupprefers supported resource isolation or shared locks. Resource acquisition defaults to a five-minute timeout. Deferred checks retain their check record and resume once their resume condition is met. Test execution keeps its own timeout.code-reviewreports deferred checks as unverified with their resume condition.execute,clean-up,submit, anddeploypreserve those records and resume the checks once the resume condition is met.submitanddeploystop before delivery and continue from their preparation step when run again. Required deferred checks prevent delivery until verified.setup-snappedly-skillsrecords shared resources, isolation or locking commands, and configured resource-acquisition timeouts. Unknown resource scope stays unverified.
Updating existing repositories
Rerun setup-snappedly-skills to refresh Concurrent runs in docs/agents/workflow.md. Setup preserves team requirements and corrects entries that classify worktree-local output as shared.
v1.4.4 · Concurrent check runs
Added
setup-snappedly-skillsrecords which checks two worktrees on one machine cannot run at the same time, in a new Concurrent runs section ofdocs/agents/workflow.md. Each entry names the shared resource the check holds or removes, such as a fixed port, a container name, or a cleanup of every container carrying a label.
Changed
code-cleanupchecks for another worktree's run before starting a check listed under Concurrent runs. When a check fails because a port or other resource is taken, or another run removed what the check created, it finds that run, leaves it running, and reruns once after it exits. A repeated collision is recorded as blocked, naming the other run and the resource, rather than as a failure of the change, and is reported as a gap the repository can close by making the check safe to run concurrently.executeworkers run only focused checks. Full suites, builds, and the checks listed under Concurrent runs run once on the combined result, since the workers share one machine.
Updating existing repositories
Rerun setup-snappedly-skills to add the Concurrent runs section to docs/agents/workflow.md. Setup fills it from each check's configuration and moves any port or resource note already recorded for a check into it.