log-attempt

majiayu000's avatarfrom majiayu000

Log a coding problem attempt when user says "log <problem_id>" with time, tries, solved status, hints, or solution usage. Parses natural language like "log count_bits - 15 min, 3 tries, solved" and calls the log-attempt script.

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 5, 2026
[Coding Practice and Feedback]

When & Why to Use This Skill

This Claude skill streamlines the process of tracking coding practice by parsing natural language inputs to log problem-solving attempts. It automatically records essential metrics such as time taken, number of tries, and whether hints or solutions were used, helping developers maintain an organized history of their technical growth and performance.

Use Cases

  • Logging daily competitive programming attempts (e.g., LeetCode, Codeforces) using simple conversational commands like 'log parity - 10 min, 1 try'.
  • Maintaining a structured 'Coding Dojo' repository by automatically updating README files with progress statistics and problem-solving history.
  • Analyzing learning patterns by tracking how often external hints or solutions are required for specific types of algorithms.
  • Quantifying coding efficiency by recording the time spent and the number of submissions needed to reach an optimal solution.
namelog-attempt
descriptionLog a coding problem attempt when user says "log <problem_id>" with time, tries, solved status, hints, or solution usage. Parses natural language like "log count_bits - 15 min, 3 tries, solved" and calls the log-attempt script.

Log Problem Attempt

Parse the user's natural language input and call the log-attempt script.

Workflow

  1. Run the log-attempt script
  2. Run update_readme.py to regenerate README.md
~/.pyenv/versions/python-coding-dojo/bin/python scripts/log_attempt.py <problem_id> [OPTIONS]
~/.pyenv/versions/python-coding-dojo/bin/python scripts/update_readme.py

Options

Flag Description Default
--time MINUTES Time taken -
--submissions N Number of attempts 1 if solved
--solved / --no-solved Whether solved --solved
--used-hints / --no-used-hints Whether used hints --no-used-hints
--used-solution / --no-used-solution Whether looked at solution --no-used-solution
--optimal / --no-optimal Whether solution is optimal (correct complexity) --no-optimal
--notes "text" Optional notes -

Parsing Rules

User says Maps to
"tries", "attempts", "submissions" --submissions
"hint", "hints" --used-hints
"solution", "looked at solution" --used-solution
"didn't solve", "not solved", "gave up" --no-solved
"min", "minutes" --time
"optimal" --optimal

Examples

Input Command
"log count_bits - 15 min, 3 tries, used hints" ... log_attempt.py count_bits --time 15 --submissions 3 --used-hints
"log parity, didn't solve, looked at solution" ... log_attempt.py parity --no-solved --used-solution
"log swap_bits - first try, 8 minutes" ... log_attempt.py swap_bits --time 8 --submissions 1