You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
Ship a /contribute command (and/or a contributing skill) in .nikcli/, so the agent running in this repo knows the contribution rules before it acts. The repo already carries .nikcli/command/{commit,issues,bug-issues}.md and .nikcli/skill/*/SKILL.md, so the machinery exists — there is just nothing covering how to land a change.
The gap is not theoretical. Filing seven issues and three PRs here last week, I hit these in order:
Issues must use a template or they die.gh issue create does not apply one, so a body written as prose gets needs:compliance and compliance-close.yml closes it 2 hours later. Five of my issues were closed that way. Worse, the check only runs on issues.opened, so editing the flagged issue does not clear the label — you have to catch it inside the window or reopen after the close.
AGENTS.md says the default branch is nikoemme-main. It is live-main. An agent that trusts AGENTS.md branches from a ref that does not exist.
bun typecheck is turbo-cached per package, so a cached pass hides a real break. A hono bump of mine typechecked clean locally and arrived red in CI.
None of that is in CONTRIBUTING.md or AGENTS.md. A command that states it — templates, branch, verification, what is already red — turns each of these from a lost issue into a non-event.
I have been running a local version of exactly this and it is what stopped me repeating the mistakes. Happy to open a PR porting it to .nikcli/command/contribute.md if you want it; wanted the design conversation first, per CONTRIBUTING.
Feature hasn't been suggested before.
Describe the enhancement you want to request
Ship a
/contributecommand (and/or acontributingskill) in.nikcli/, so the agent running in this repo knows the contribution rules before it acts. The repo already carries.nikcli/command/{commit,issues,bug-issues}.mdand.nikcli/skill/*/SKILL.md, so the machinery exists — there is just nothing covering how to land a change.The gap is not theoretical. Filing seven issues and three PRs here last week, I hit these in order:
gh issue createdoes not apply one, so a body written as prose getsneeds:complianceandcompliance-close.ymlcloses it 2 hours later. Five of my issues were closed that way. Worse, the check only runs onissues.opened, so editing the flagged issue does not clear the label — you have to catch it inside the window or reopen after the close.AGENTS.mdsays the default branch isnikoemme-main. It islive-main. An agent that trustsAGENTS.mdbranches from a ref that does not exist.bun typecheckis turbo-cached per package, so a cached pass hides a real break. A hono bump of mine typechecked clean locally and arrived red in CI.pre-pushcannot pass on a Windows checkout (pre-push hook fails on a clean checkout: identity worker types are out of date #169, 74 tracked symlinks break typecheck and web assets on a Windows checkout #174), so pushing means--no-verify, which looks like rule-breaking unless you know why./autofixdoes not run on fork PRs, and several CI jobs are already red onlive-main(processor-retry.test.ts leaks module mocks and fails ~100 later tests #168), so a contributor cannot tell their regression from the baseline.None of that is in
CONTRIBUTING.mdorAGENTS.md. A command that states it — templates, branch, verification, what is already red — turns each of these from a lost issue into a non-event.I have been running a local version of exactly this and it is what stopped me repeating the mistakes. Happy to open a PR porting it to
.nikcli/command/contribute.mdif you want it; wanted the design conversation first, per CONTRIBUTING.