Updated 2mo ago
by Far-200
think-before-code
Socratic Agent Skills for learning problem-solving and software-engineering judgment — one question at a time.
20 GitHub stars (20)
+6 in 30 days
| Period | New stars |
|---|---|
| Oct 1 | 0 |
| Oct 2 | 0 |
| Oct 3 | 0 |
| Oct 4 | +1 |
| Oct 5 | 0 |
| Oct 6 | 0 |
| Oct 7 | 0 |
| Oct 8 | 0 |
| Oct 9 | 0 |
| Oct 10 | 0 |
| Oct 11 | 0 |
| Oct 12 | 0 |
| Oct 13 | 0 |
| Oct 14 | 0 |
| Oct 15 | 0 |
| Oct 16 | 0 |
| Oct 17 | +2 |
| Oct 18 | 0 |
| Oct 19 | 0 |
| Oct 20 | +1 |
| Oct 21 | 0 |
| Oct 22 | 0 |
| Oct 23 | 0 |
| Oct 24 | 0 |
| Oct 25 | 0 |
| Oct 26 | 0 |
| Oct 27 | 0 |
| Oct 28 | 0 |
| Oct 29 | +1 |
| Oct 30 | 0 |
| Oct 31 | 0 |
| Nov 1 | 0 |
| Nov 2 | 0 |
| Nov 3 | 0 |
| Nov 4 | +1 |
| Nov 5 | 0 |
| Nov 6 | 0 |
| Nov 7 | 0 |
| Nov 8 | 0 |
| Nov 9 | 0 |
| Nov 10 | +1 |
| Nov 11 | 0 |
- 11 skills (11 skills found in its SKILL.md files)
- 4 forks (4 forks)
- 2mo ago last update (Last updated 2mo ago)
Install
Skills CLI
npx skills add Far-200/think-before-code
Asks which skills and agents to install. Just one: npx skills add Far-200/think-before-code --skill code-review-coach — add -g for every project.
Claude Code
git clone https://github.com/Far-200/think-before-codecp -r "think-before-code/skills/code-review-coach" ~/.claude/skills/
Copies the code-review-coach skill into ~/.claude/skills/ for every project (use .claude/skills/ for one project). Repeat for the other skills listed below.
Plugin
/plugin marketplace add Far-200/think-before-code
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.
-
code-review-coach
Use when the learner wants to practise reviewing existing code, a diff, or a pull request through guided questioning — discovering and justifying findings one concern at a time instead of receiving a dumped list or a rewrite. The first non-DSA skill in this suite. Not for chasing an already-observed concrete failure (debug-coach), not for designing a systematic test suite (test-case-coach), not f…
skills/code-review-coach/ on GitHub (opens in a new tab)SKILL.md -
complexity-coach
Use when the learner has a working approach or code and wants to determine or justify its time and space complexity. Focuses purely on Big-O derivation — nested-loop counting, recurrences, amortized cost — not on designing or debugging the algorithm itself. A standalone drill, and a deeper version of the single complexity question dsa-tutor asks during verification.
skills/complexity-coach/ on GitHub (opens in a new tab)SKILL.md -
concept-coach
Use when the learner wants to build understanding of a general programming, software-engineering, systems, or architecture concept — references, recursion, closures, coupling, dependency injection, caching, concurrency, queues, consistency, and similar — through Socratic coaching from their current mental model, with no concrete task behind the question. Not for an unsolved DSA problem (dsa-tutor…
skills/concept-coach/ on GitHub (opens in a new tab)SKILL.md -
debug-coach
Use when the learner already has written code or pseudocode, knows what it should do, and it isn't doing that — and they want the bug isolated without receiving a rewritten solution. Not for choosing an approach (use dsa-tutor), not for tracing an approach that has no code yet (use dry-run-coach), and not for plain syntax questions with no observed failure.
skills/debug-coach/ on GitHub (opens in a new tab)SKILL.md -
dry-run-coach
Use when the learner already has an approach or algorithm in mind and needs to manually trace it, step by step, on a concrete input to verify or debug their mental model. Not for choosing an approach or writing code — use dsa-tutor for those. Teaches the actual mechanics of tracing, which dsa-tutor only names as a single stage.
skills/dry-run-coach/ on GitHub (opens in a new tab)SKILL.md -
dsa-tutor
Use when the user is working through a DSA or LeetCode-style problem and wants to build real problem-solving ability instead of receiving a finished solution. Guides through questions, withholds solutions until genuine struggle has happened, and logs mistakes with root causes instead of surface symptoms.
skills/dsa-tutor/ on GitHub (opens in a new tab)SKILL.md -
mock-interviewer
Use when the learner explicitly wants a timed, realistic technical-interview simulation for a DSA problem rather than incremental learning support. Minimizes proactive hints during the attempt and gives structured rubric feedback only at the end. This is the opposite interaction mode from dsa-tutor — do not blend the two in one session.
skills/mock-interviewer/ on GitHub (opens in a new tab)SKILL.md -
pattern-transfer-coach
Use after the learner has solved or substantially completed a DSA problem and wants to turn it into transferable knowledge — abstracting the structure away from the story, naming signals that suggest or rule out the pattern, and adapting it to exactly one cousin problem. Not for solving the original problem (dsa-tutor), not for generic data-structure or pattern definitions with no solved problem…
skills/pattern-transfer-coach/ on GitHub (opens in a new tab)SKILL.md -
problem-decoder
Use when the learner has a raw DSA or LeetCode-style problem statement and needs to pin down exactly what is being asked — inputs, outputs, constraints, and edge cases — before any solving begins. Not for hints, approach design, or debugging; hand off to dsa-tutor once the problem is fully understood.
skills/problem-decoder/ on GitHub (opens in a new tab)SKILL.md -
specification-coach
Use when the learner has a vague feature request, issue, change request, or agent task and wants to turn it into an implementation-ready specification through guided questioning — clarifying observable behaviour, scope, non-goals, constraints, failure behaviour, acceptance criteria, and the smallest verifiable slice, without the model inventing requirements or writing the implementation. Not for…
skills/specification-coach/ on GitHub (opens in a new tab)SKILL.md -
test-case-coach
Use when the learner already has an approach or implementation and wants help designing a compact, justified test suite — finding missing cases, boundary values, or adversarial inputs that stress the algorithm's assumptions. Not for decoding a raw problem statement's implied edge cases (problem-decoder), not for tracing one chosen input step by step (dry-run-coach), not for chasing an already-obs…
skills/test-case-coach/ on GitHub (opens in a new tab)SKILL.md
No skill matches that filter.
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.