Northeastern-Electric-Racing / Northeastern-Electric-Racing/Argos
Evaluate `tdd` skill in real use
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5
- Forks
- 1
- Avg merge
- 4d 22h
- Merged PRs (30d)
- 26
Description
Follow-up from the Matt Pocock skills adoption PR (#646).
Trial the tdd skill on a real feature or bug fix and confirm the red-green-refactor loop genuinely helps rather than adding friction.
Acceptance
- Use
/tddend-to-end on at least one real change. - Note where the red-green-refactor enforcement helped vs. felt heavy.
- Tune
.claude/skills/tdd/SKILL.md(or leave a comment recommending no change) based on findings.
Tooling-evaluation follow-up; not blocking.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading .claude/skills/tdd/SKILL.md and identify a suitable real feature or bug fix in the repository. Run /tdd end-to-end, recording where the red-green-refactor enforcement helps or adds friction. Done means the skill is tuned based on those findings, or a comment explains why no change is recommended.
Written by the indexing model from the issue text.
Assessment
- Domain
- testing-qa, tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100