Review before applying
Compare actual behavior with the expected result. If a check fails, investigate it before applying more changes.
AI coding workspace
Minute-field schedule expansion
MinuteBramble is a Windows AI coding client for inspecting minute-field syntax. Bring a parser task into the project conversation and review the model’s proposed accepted forms before using the resulting values.
● ● ●MinuteBramble●
A concrete starting point · Minute-field schedule expansion ×
import re
def minute_values(field):
if type(field) is not str or not 1 <= len(field) <= 128:
raise ValueError("minute.input")
result = set()
for item in field.split(","):
match = re.fullmatch(r"(\*|[0-9]+(?:-[0-9]+)?)(?:/([0-9]+))?", item)
if match is None:
raise ValueError("minute.syntax")
base, step_text = match.groups()
step = int(step_text) if step_text else 1
if not 1 <= step <= 59 or (step_text and base != "*" and "-" not in base):
raise ValueError("minute.step")
bounds = [int(x) for x in base.split("-")] if base != "*" else [0, 59]
low, high = (bounds[0], bounds[-1])
if not 0 <= low <= high <= 59:
raise ValueError("minute.bounds")
result.update(range(low, high+1, step))
return sorted(result)
✳Minute-field schedule expansion
✓ ChangesReview before applying ↗
Illustrative workspace
Connection
Base URL, credentials and a reachable server.
Project
Test lists, inclusive ranges and steps on ranges or stars, rejecting reversed bounds, zero steps and unsupported syntax without scheduling a job.
A concrete starting point
import re
def minute_values(field):
if type(field) is not str or not 1 <= len(field) <= 128:
raise ValueError("minute.input")
result = set()
for item in field.split(","):
match = re.fullmatch(r"(\*|[0-9]+(?:-[0-9]+)?)(?:/([0-9]+))?", item)
if match is None:
raise ValueError("minute.syntax")
base, step_text = match.groups()
step = int(step_text) if step_text else 1
if not 1 <= step <= 59 or (step_text and base != "*" and "-" not in base):
raise ValueError("minute.step")
bounds = [int(x) for x in base.split("-")] if base != "*" else [0, 59]
low, high = (bounds[0], bounds[-1])
if not 0 <= low <= high <= 59:
raise ValueError("minute.bounds")
result.update(range(low, high+1, step))
return sorted(result)
Turn configuration syntax into predictable application behavior
MinuteBramble gives configuration work a Windows AI coding workspace. Bring the parser, the code reading its output and a few real configuration examples into the conversation. Ask the model to inspect what the application accepts today before requesting new syntax, so the change has a defined compatibility target.
A task involving minute_field.py might add tests around stepped minute ranges and rejected input. State the accepted field syntax and expected list of values, then inspect how the caller uses that list. This is a project parser example; evaluating a field is only one part of deciding how an application should schedule its work.
After reviewing the proposal, run accepted and rejected examples in your own environment. Check overlapping entries, range boundaries and invalid steps, with expected outputs written independently. If a change broadens accepted configuration, inspect the documentation and error messages that need to match it. A parser that accepts more text is not automatically easier to operate.
You can choose an abliterated AI model if one is offered through a supported OpenAI-compatible or Anthropic endpoint. Provide credentials when required, and check the service’s actual restrictions. Tool support and context capacity depend on the model and server; keep the accepted grammar and consumer expectations explicit whichever connection you use.
Before changing a configuration grammar
Does a minute field define a complete schedule?
No. It supplies one component under the parser’s accepted syntax. Other scheduling rules belong to the application using it. Include the consumer in the review and avoid treating a successful field expansion as evidence that an entire scheduling workflow is correct.
How should overlapping entries behave?
State whether duplicate values should be removed and what ordering the caller expects. Give a small overlapping example with its exact expected output. Inspect downstream code that may otherwise interpret repeated entries as repeated work or rely on stable ascending order.
Should spaces or unfamiliar forms be tolerated?
Define the grammar deliberately. A permissive cleanup can turn a typing error into unintended configuration. Review accepted and rejected forms together, and check that error messages explain the supported syntax without silently assigning meaning to inputs the application has never promised to accept.
What belongs in a request for a new syntax feature?
Include the new form, its expected expansion and its interaction with existing ranges and steps. Identify the code consuming the values and any documentation to update. Keep compatibility examples available so the proposed feature does not change established configuration behavior unintentionally.
MinuteBramble · Updated 2026-10-25