Skip to content
Back to search

programming-best-practices

Agent skill that applies TDD, SOLID, static typing, docstrings, linting and logging.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/orenatobr--programming-best-practices/badge.svg)](/listings/orenatobr--programming-best-practices)

HTML

<a href="/listings/orenatobr--programming-best-practices"><img src="/api/listings/orenatobr--programming-best-practices/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

For Claude Code, copy the skill folders into your personal skills directory:

git clone https://github.com/orenatobr/programming-best-practices.git
mkdir -p ~/.claude/skills
cp -R programming-best-practices/skills/* ~/.claude/skills/

Start a new Claude Code session. Skills load from the `description` in each `SKILL.md`, so they trigger on their own and can also be called by name.

Other agents: each skill is a folder with a `SKILL.md` (YAML frontmatter plus Markdown). Tools that read the Agent Skills format can load `skills/` as it is. For the rest, paste the body of the `SKILL.md` into the agent's instruction file.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 45 lines
  1. # programming-best-practices
  2. Six rules for writing or reviewing code in any language: TDD, SOLID without speculative abstraction, complete static typing, Google Style docstrings, linting, and logging instead of `print`. Before finishing, the agent walks the six checks and reports each one as OK, FIXED or RISK.
  3. ## Install
  4. For Claude Code, copy the skill folders into your personal skills directory:
  5. ```bash
  6. git clone https://github.com/orenatobr/programming-best-practices.git
  7. mkdir -p ~/.claude/skills
  8. cp -R programming-best-practices/skills/* ~/.claude/skills/
  9. ```
  10. Start a new Claude Code session. Skills load from the `description` in each `SKILL.md`, so they trigger on their own and can also be called by name.
  11. Other agents: each skill is a folder with a `SKILL.md` (YAML frontmatter plus Markdown). Tools that read the Agent Skills format can load `skills/` as it is. For the rest, paste the body of the `SKILL.md` into the agent's instruction file.
  12. ## Usage
  13. Invoke `/programming-best-practices`, optionally with a file, diff or path to audit. It also triggers on "TDD", "typing", "lint" and "logging".
  14. ## Requirements
  15. Nothing beyond an agent that loads skills. The TDD rule defers to `tests-guidelines` and the logging rule points to `attack-protection`, so install [tests-guidelines](https://github.com/orenatobr/tests-guidelines) and [attack-protection](https://github.com/orenatobr/attack-protection) as well.
  16. ## Related skills
  17. `tests-guidelines`, `attack-protection`.
  18. ## What is in this repo
  19. | Path | Purpose |
  20. |------|---------|
  21. | `skills/programming-best-practices/` | The `programming-best-practices` skill. |
  22. | `CHANGELOG.md` | Notable changes, in Keep a Changelog format. |
  23. | `AGENTS.md` | Rules for AI agents that edit this repo. |
  24. ## Contributing
  25. `main` is protected: changes land through a pull request with one approval. See [AGENTS.md](AGENTS.md) for the conventions.
  26. ## License
  27. MIT, see [LICENSE](LICENSE).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.