Enforce repo standards with the coding-standards skill

Where this fits

You're working in a monorepo with strict CI gates. Your AI agent opens a PR that pushes directly to main, uses a deep import path, and includes a commit subject with a capital letter — the build fails. The coding-standards skill loads the repo's enforced rules into the agent's context before any code change, so it follows branch, lint, import, and commit conventions from the first keystroke.

Why agents benefit

• The agent loads repo rules automatically before touching code, so it never guesses conventions.
• It enforces a PR-only workflow: fetch, check stale branch, branch, commit, push, and open a PR — no human reminders needed.
• It never bypasses ESLint or TypeScript checks, and knows how to scope overrides in eslint.config.mjs with a reason comment.
• It structures imports and type imports correctly, matching CI expectations on the first attempt.
• It formats commits per commitlint rules, so release triggers (feat/fix/perf + BREAKING CHANGE) work as intended.

Practical scenarios

PR-only workflow enforcement

The agent runs git fetch origin, detects a stale branch, creates a fresh branch, commits, pushes, and opens a PR via gh pr create — waiting for approval instead of merging to main.

Import ordering and path privacy

When editing a UI component, the agent uses package entrypoints (@ajh/ui) instead of deep paths, groups imports in the required order (node:* → external → @ajh/* → @/* → relative), and uses import type for pure types. It also keeps all paths repo-relative, never leaking local usernames or home directories.

Commit message compliance

The agent writes lower-case, imperative commit subjects under 100 characters, keeps body lines under 200, and picks the correct type prefix — so pnpm commit hooks and CI pass without friction.

Add it to your agent workflow

Install the skill:

npx skills add saeedkolivand/ai-job-hunter-app --skill coding-standards

Then load it in your agent prompt: "Load coding-standards before any code change." The agent will apply the rules automatically, from branch creation to commit formatting.

Compare before adopting

Check quality signals: is the rule set specific to this repo or generic enough to reuse? Look at maintenance freshness — last commit date, open issues, CI status. Compare with alternatives like repo README instructions or other agent skills. Assess workflow fit: does your repo use pnpm, commitlint, and ESLint strict mode? If not, adapt the rules to your stack.

Why it is worth tracking

The skill has 48 stars and is maintained by saeedkolivand with a clear, CI-enforced rule set that maps directly to build gates. It's a strong reference for encoding repo conventions into agent context, and it's worth tracking if you're building coding agents that must respect existing quality checks. For more details, see the skill page at https://www.openagentskill.com/skills/saeedkolivand-coding-standards.