Skip to content
Skills Library
Programming · Building & coding

programming

/programming

USE FOR: Programming/debugging: Bash, Python/Jupyter quality, Nix package workflow, Terraform with Checkov, Markdown, TDD/Tidy First, and root-cause isolation. DO NOT USE FOR: agent harness, data-platform, diagramming, or GitHub workflow work.

Author
i9wa4 ↗
Repository
dotfiles ↗
Licence
MIT
Last repository change
26.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
13
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

USE FOR: Programming/debugging: Bash, Python/Jupyter quality, Nix package workflow, Terraform with Checkov, Markdown, TDD/Tidy First, and root-cause isolation. DO NOT USE FOR: agent harness, data-platform, diagramming, or GitHub workflow work.

Original author description

USE FOR: Programming/debugging: Bash, Python/Jupyter quality, Nix package workflow, Terraform with Checkov, Markdown, TDD/Tidy First, and root-cause isolation. DO NOT USE FOR: agent harness, data-platform, diagramming, or GitHub workflow work.

How it works

  1. 1. Scope
  2. 2. Workflow
  3. 3. References
Original SKILL.md headings · 47 lines, 210 words
SKILL.md preview
---
name: programming
license: MIT
metadata:
  version: "1.0.0"
description: |
  USE FOR: Programming/debugging: Bash, Python/Jupyter quality, Nix package workflow, Terraform with Checkov, Markdown, TDD/Tidy First, and root-cause isolation. DO NOT USE FOR: agent harness, data-platform, diagramming, or GitHub workflow work.
---

# Programming

Owns repo-local implementation guidance and debugging. Prefer a narrower domain
skill when one exists.

## 1. Scope

- Bash scripts and shell command design.
- Python utility edits, local execution, and general Python quality:
  type hints, pytest, uv/ruff/pyright tooling, Jupyter notebooks.
- Nix package workflow, especially fetcher hash acquisition.
- Terraform infrastructure code development, plan review, and Checkov
  security/compliance scanning.
- Markdown authoring and formatting rules.
- Red-Green-Refactor and Tidy First implementation loops.
- Systematic debugging: reproducers, working-pattern comparison, root cause.

Out of scope:

- Agent harness runtime, Home Manager agent config, hooks, postman routing, or
  installed agent outputs; use `dotfiles`.
- GitHub issue, PR, review, or public-surface mechanics; use
  `dev-platform-workflow`.
- Data-platform or diagramming workflows; use their target skills.

## 2. Workflow

1. Inspect relevant files, repo conventions, and `git status`.
2. Select the focused reference below before changing files.
3. Keep structural and behavioral edits separate when practical.
4. Run the fastest focused check during iteration, then the nearest repo
   validation surface before reporting success.
5. Report changed files, verification, residual Waza findings, and remaining
   risk.

## 3. References

- [Bash Scripting](references/bash-scripting.md)
- [Python Development](references/python-development.md)
- [Python Quality](references/python-quality.md)
- [Nix Package Workflow](references/nix-package-workflow.md)
- [Terraform Development](references/terraform-development.md)
- [Markdown Authoring](references/markdown-authoring.md)
- [TDD And Tidy First](references/tdd-tidy-first.md)
- [Systematic Debugging](references/systematic-debugging.md)
Files in this package (13)
  • SKILL.md 2 KB
  • evals/eval.yaml 1 KB
  • evals/tasks/negative-trigger-1.yaml 1 KB
  • evals/tasks/positive-trigger-1.yaml 1 KB
  • evals/tasks/positive-trigger-2.yaml 1 KB
  • references/bash-scripting.md 1 KB
  • references/markdown-authoring.md 1 KB
  • references/nix-package-workflow.md 1 KB
  • references/python-development.md 1 KB
  • references/python-quality.md 2 KB
  • references/systematic-debugging.md 3 KB
  • references/tdd-tidy-first.md 1 KB
  • references/terraform-development.md 5 KB

Versions

RepositoryScoreLicence
This page · i9wa4/dotfiles90MIT
soneta/soneta-erp-skills100MIT
gnarea/sdlc100MIT
wesleyegberto/software-engineering-skills100MIT

Database snapshot: 13.11.2026 · package version 56bbd5102b11 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 96nix
    Write and review Nix code. Use when a task touches a `.nix` file.
  • 100pair-programming
    AI-assisted pair programming with multiple modes (driver/navigator/switch), real-time verification, quality monitoring, and comprehensive testing. Supports TDD, debugging, refactoring, and learning sessions. Features automatic role switching, continuous code review, security…
  • 90iac-security-workflow
    Performs offline Infrastructure-as-Code review with Trivy and Checkov over authorized local Terraform, CloudFormation, Kubernetes, Helm, Dockerfile, ARM, Bicep, and CI configuration. Use for IaC, Terraform, Checkov, misconfiguration, 基础设施即代码, 配置审计, or 云配置代码.
  • 90nix-tool-policy
    Use when installing or choosing CLI tools in a Nix flake repo, editing flake.nix or home-manager config, or when tempted to pip/pipx/uv/brew/npm install anything. Tools come from the dev shell or nix shell — never ad-hoc package managers.
  • 90triage-issue
    Triage a bug or issue by exploring the codebase to find root cause, then create a GitHub issue with a TDD-based fix plan. Use when user reports a bug, wants to file an issue, mentions "triage", or wants to investigate and plan a fix for a problem.
  • 100tdd-fix
    Use when fixing a bug test-first: write a failing test to reproduce it, find the root cause, fix, and add a regression test.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.