<Devsly/>
NotebookLM Watermark Remover
Remove the NotebookLM watermark from PDF slide exports — free, unlimited, and 100% in your browser.
View
NotebookLM Video Watermark Remover
Remove the NotebookLM watermark from every frame of your MP4 and auto-trim the end card — free and unlimited.
View
Gemini Watermark Remover
Remove the Gemini (Veo) sparkle watermark from every frame of your AI-generated MP4 — free and unlimited.
View
MCP https://devsly.io/mcp MCP Tools Best Skills API Docs

Keyboard Shortcuts

Navigation

Quick Search
⌘ / Ctrl + K
Toggle Dark Mode
⌘ / Ctrl + D
Close Dialogs
Esc

Tool Actions

Execute / Process
⌘ / Ctrl + Enter
Clear Input
⌘ / Ctrl + Shift + C
Copy Output
⌘ / Ctrl + Shift + X

Editor

Select All
⌘ / Ctrl + A
Undo
⌘ / Ctrl + Z
Redo
⌘ / Ctrl + Shift + Z

Updated 1mo ago

by chipfighter

coding-discipline

Workflow-agnostic guardrails for AI coding agents: spec sync + risk-triggered engineering discipline for Claude Code and Codex.

Works with
  • Claude
  • Codex

25 GitHub stars (25)

+15 in 14 days

Stars gained per day · daily snapshots since Oct 2
Stars gained per day, Oct 2 to Oct 16: +15 in total; the busiest day was Oct 7 with +3 stars.Oct 3: 0 starsOct 4: 0 starsOct 5: +1 starsOct 6: +2 starsOct 7: +3 starsOct 8: +3 starsOct 9: +2 starsOct 10: +3 starsOct 11: 0 starsOct 12: +1 starsOct 13: 0 starsOct 14: 0 starsOct 15: 0 starsOct 16: 0 stars
Stars gained between daily snapshots
PeriodNew stars
Oct 30
Oct 40
Oct 5+1
Oct 6+2
Oct 7+3
Oct 8+3
Oct 9+2
Oct 10+3
Oct 110
Oct 12+1
Oct 130
Oct 140
Oct 150
Oct 160
  • 8 skills (8 skills found in its SKILL.md files)
  • 1 forks (1 forks)
  • 1mo ago last update (Last updated 1mo ago)

Install

Skills CLI

npx skills add chipfighter/coding-discipline

Asks which skills and agents to install. Just one: npx skills add chipfighter/coding-discipline --skill brainstorming — add -g for every project.

Claude Code

git clone https://github.com/chipfighter/coding-disciplinecp -r "coding-discipline/plugins/coding-discipline/skills/brainstorming" ~/.claude/skills/

Copies the brainstorming skill into ~/.claude/skills/ for every project (use .claude/skills/ for one project). Repeat for the other skills listed below.

Plugin

/plugin marketplace add chipfighter/coding-discipline

Run inside Claude Code if the repository ships a plugin marketplace, then pick plugins from /plugin.

Skills can run code on your machine — read the SKILL.md first.

What it does

In the author's own words, from each skill's SKILL.md.

  • brainstorming

    Use before coding when requirements have multiple reasonable interpretations, approaches require tradeoffs, or mistakes would be costly (permissions/payments/data migration/public APIs/data structures/hard-to-revert changes). Clarify requirements and design one question at a time, then get approval before implementation. Do not trigger for a focused small change with a clear goal and approach, or…

    plugins/coding-discipline/skills/brainstorming/SKILL.md on GitHub (opens in a new tab)
  • code-review

    Use when changes affect interactions across multiple modules, involve high-risk areas (authorization/authentication, payments/funds, data deletion/migration, public APIs/cross-service interfaces/security boundaries), or the user requests a review. Review in this order—correctness → requirements → security → simplicity → style. Verify feedback before acting; do not comply blindly or agree performa…

    plugins/coding-discipline/skills/code-review/SKILL.md on GitHub (opens in a new tab)
  • context-hygiene

    Use when starting a project, reading project documentation or history, or resolving conflicts between documents. For current state, read only the latest documents designated by the project; do not proactively read archives; do not duplicate the spec; use long-term memory only for environment, people, and preferences not recorded in the repository.

    plugins/coding-discipline/skills/context-hygiene/SKILL.md on GitHub (opens in a new tab)
  • git-flow

    Use when creating a branch, using worktrees for parallel work, committing, or wrapping up. Covers branch naming, conventional commits, short-lived branches, worktree isolation, and final merge/cleanup.

    plugins/coding-discipline/skills/git-flow/SKILL.md on GitHub (opens in a new tab)
  • spec-sync

    Use in cross-session work when user-confirmed outcomes, non-goals, hard constraints, or acceptance criteria have not been written back to the current source of truth (spec), or reality conflicts with it enough that following it would be wrong; also use during wrap-up or handoff when a source of truth should exist but does not. Edit only the affected original wording; do not keep separate old and…

    plugins/coding-discipline/skills/spec-sync/SKILL.md on GitHub (opens in a new tab)
  • systematic-debugging

    Use before proposing a permanent fix for bugs, test failures, or unexpected behavior with an unknown root cause—mandatory when symptoms are far from the cause, a prior fix failed, or the issue crosses components. Reproduce, trace backward to the root cause, fix once at the source, and add a regression test. Do not trigger for obvious errors whose message identifies the cause (syntax/typo/missing…

    plugins/coding-discipline/skills/systematic-debugging/SKILL.md on GitHub (opens in a new tab)
  • tdd

    Use before implementation when behavior can be verified by automated tests and regression coverage has clear value. For bugs with an unknown root cause, use systematic-debugging first, then return for red-green. Follow red-green-refactor—write a failing test first, add only enough code to pass it, then refactor. Do not trigger for documentation, configuration, copy-only, or styling changes with n…

    plugins/coding-discipline/skills/tdd/SKILL.md on GitHub (opens in a new tab)
  • verify-before-done

    Use before claiming "done", "fixed", "tested", or "it runs", and before committing or opening a PR or MR—no task is exempt. Accept only evidence gathered after the last relevant change and just sufficient to prove the claim; do not over-verify small changes.

    plugins/coding-discipline/skills/verify-before-done/SKILL.md on GitHub (opens in a new tab)

Review before you install

A skill is a set of instructions and scripts your agent will follow, and it can run code on your machine. Read the SKILL.md and any scripts first — this listing is not a security review.