-
Notifications
You must be signed in to change notification settings - Fork 59
chore: add AgentReady scaffolding for AI-assisted development #3415
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
ed1112c
b8dd6d4
9aa5f30
a62515f
e364866
a51648f
f373489
9abbc08
db897d8
ebe9a83
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,12 @@ | ||
| --- | ||
| paths: | ||
| - "acceptance/**" | ||
| --- | ||
|
|
||
| # Acceptance Test Rules | ||
|
|
||
| - Tests use Cucumber/Gherkin via Godog with Testcontainers for infrastructure | ||
| - Run single scenario: `make scenario_<name>` (replace spaces with underscores) | ||
| - Use `-persist` flag to keep test env for debugging, `-restore` to rerun | ||
| - Snapshot testing: update with `UPDATE_SNAPS=true make acceptance` | ||
| - macOS requires Podman machine — see `hack/macos/README.md` |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,15 @@ | ||
| { | ||
| "hooks": { | ||
| "PostToolUse": [ | ||
| { | ||
| "matcher": "Edit|Write", | ||
| "hooks": [ | ||
| { | ||
| "type": "command", | ||
| "command": "echo \"$CLAUDE_FILE_PATHS\" | while IFS= read -r f; do case \"$f\" in *.go) gofmt -w \"$f\" 2>/dev/null;; esac; done" | ||
| } | ||
| ] | ||
| } | ||
| ] | ||
| } | ||
| } |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,8 @@ | ||
| #### What: | ||
| <!--- What is this change doing? ---> | ||
|
|
||
| #### Why: | ||
| <!--- Please include the context and background for your change. ---> | ||
|
|
||
| #### Tickets: | ||
| <!--- Please link to any related Jira issue here. ---> |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -170,6 +170,17 @@ tags | |
| # Persistent undo | ||
| [._]*.un~ | ||
|
|
||
| # Go coverage output | ||
| cover.out | ||
| coverage.txt | ||
|
coderabbitai[bot] marked this conversation as resolved.
|
||
|
|
||
| # Vim swap files (explicit patterns for tooling detection) | ||
| *.swp | ||
| *.swo | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. [low] style/conventions The new .swp and .swo patterns are already covered by existing Vim template glob patterns ([._].s[a-v][a-z] and [._].sw[a-p]) at lines 155-160. Similarly, cover.out is matched by the existing *.out at line 148. These are technically redundant. Suggested fix: Consider removing the explicit .swp/.swo entries since they are already covered, or add a comment explaining why explicit patterns are needed alongside the glob-based ones.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Technically redundant with the glob patterns, but the explicit entries are harmless and make the intent immediately visible to contributors who do not read glob character classes. Leaving as-is. |
||
|
|
||
| # OS files | ||
| .DS_Store | ||
|
|
||
| # Last persisted acceptance test run information | ||
| acceptance/.persisted | ||
|
|
||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -11,6 +11,17 @@ such as: | |
| Consult the [documentation][docs] for available sub-commands, descriptions and | ||
| examples of use. | ||
|
|
||
| ## Installation | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. [low] documentation The new Installation section mentions "make build" for building from source. The existing Building section immediately below also opens with "Run make build", creating partial duplication. Suggested fix: Consider having the Installation section link to the Building section instead of repeating the make build instruction, or merge the two sections.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Intentional — the Installation section leads with pre-built binaries and mentions There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. [low] documentation The new Installation section documents
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Intentional — the Installation section leads with pre-built binaries and mentions |
||
|
|
||
| Install a pre-built binary from the [latest release](https://github.com/conforma/cli/releases), | ||
| or build from source: | ||
|
|
||
| ```bash | ||
| make build # builds dist/ec for your platform | ||
| ``` | ||
|
|
||
| See the [documentation][docs] for usage examples. | ||
|
|
||
| ## Building | ||
|
|
||
| Run `make build` from the root directory and use the `dist/ec` executable, or | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[low] style/conventions
The
cover.outpattern is already matched by the existing*.outglob on line 149. The*.swp/*.swopatterns partially overlap with the vim swap patterns on lines 155-160. Not harmful, but technically redundant.Suggested fix: Consider removing
cover.out(keepingcoverage.txtwhich is not otherwise matched) or adding a comment noting the intentional redundancy for clarity.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Technically redundant with the existing glob patterns, but the explicit entries are harmless and make the intent immediately visible to contributors who do not read glob character classes. Leaving as-is.