Repository navigation
feat: add Claude Code agentic config and rewrite README - #8
hamishcrittenden wants to merge 1 commit into
Conversation
Add .claude/ directory with agent definitions, slash commands, and settings for AI-assisted development workflows. Update README with comprehensive architecture documentation, deployment prerequisites, CI/CD details, and known gaps.
|
❌ Your current sustainability score is 2. Sustainability scanner suggests 1 improvements to apply to your template. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 8c435476c2
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| - Terminate TLS at ALB and re-encrypt upstream where possible. | ||
| - Keep n8n and database credentials in AWS Secrets Manager; they are injected via ECS secrets. | ||
| - Database ingress is restricted to ECS task security groups only. | ||
| - ECS tasks and RDS run in private subnets; the ALB is the only internet-facing component. |
There was a problem hiding this comment.
This line states that ECS tasks run in private subnets, but the deploy workflow falls back to PublicSubnetIds when ECS_SUBNETS is unset (.github/workflows/deploy-aws-infra.yml, if [ -z "$ECS_SUBNETS" ] ... PublicSubnetIds). That mismatch can cause operators to assume a private-only runtime while the default deployment path is public-subnet based, so the documentation should be corrected (or the workflow default changed).
Useful? React with 👍 / 👎.
| - Answer the user's specific questions with concrete evidence | ||
|
|
||
| 5. **Gather metadata for the research document:** | ||
| - Run the `hack/spec_metadata.sh` script to generate all relevant metadata |
There was a problem hiding this comment.
The new /research_codebase instructions require running hack/spec_metadata.sh, but that script is not present in this repository, so the workflow fails at the metadata step for every invocation. Since this command was added in the same change, it should point to an existing script or provide inline commands so the documented process is executable.
Useful? React with 👍 / 👎.
1 participant
Summary
.claude/directory with 6 agent definitions, 27 slash commands, and settings for AI-assisted development workflows.gitignorefor local Claude Code settingsREADME.mdwith comprehensive architecture documentation, deployment prerequisites, CI/CD pipeline details, code coverage notes, and known incomplete/unused itemsTest plan
.claude/commands and agents load in Claude Code.gitignoreexcludes local settings as intended🤖 Generated with Claude Code