Logging and Error Reporting for Warp
warpdotdev/warp
Guides log level choices and when to raise a structured Sentry event instead of a plain log line in the Warp Rust codebase, keeping secrets out of logs.
Keep a running implementation-notes.md during a build, logging every deviation from the plan and every discovered edge case.
MITAuto-check passed
Install Implementation Notes
$ npx skills add Neeeophytee/finding-unknowns-skills --skill implementation-notes -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Neeeophytee/finding-unknowns-skills implementation-notes --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Neeeophytee/finding-unknowns-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/implementation-notes .claude/skills/implementation-notes && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "implementation-notes" agent skill from https://github.com/Neeeophytee/finding-unknowns-skills/tree/main/skills/implementation-notes into .claude/skills/implementation-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implementation-notes", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Neeeophytee/finding-unknowns-skills/tree/main/skills/implementation-notesType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Neeeophytee/finding-unknowns-skills --skill implementation-notes -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Neeeophytee/finding-unknowns-skills implementation-notes --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Neeeophytee/finding-unknowns-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/implementation-notes .agents/skills/implementation-notes && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "implementation-notes" agent skill from https://github.com/Neeeophytee/finding-unknowns-skills/tree/main/skills/implementation-notes into .agents/skills/implementation-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implementation-notes", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Neeeophytee/finding-unknowns-skills --skill implementation-notes -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Neeeophytee/finding-unknowns-skills implementation-notes --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Neeeophytee/finding-unknowns-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/implementation-notes .cursor/skills/implementation-notes && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "implementation-notes" agent skill from https://github.com/Neeeophytee/finding-unknowns-skills/tree/main/skills/implementation-notes into .cursor/skills/implementation-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implementation-notes", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Neeeophytee/finding-unknowns-skills.git --path skills/implementation-notes--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Neeeophytee/finding-unknowns-skills --skill implementation-notes -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Neeeophytee/finding-unknowns-skills implementation-notes --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Neeeophytee/finding-unknowns-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/implementation-notes .gemini/skills/implementation-notes && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "implementation-notes" agent skill from https://github.com/Neeeophytee/finding-unknowns-skills/tree/main/skills/implementation-notes into .gemini/skills/implementation-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implementation-notes", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Neeeophytee/finding-unknowns-skills implementation-notesInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Neeeophytee/finding-unknowns-skills --skill implementation-notes -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Neeeophytee/finding-unknowns-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/implementation-notes .github/skills/implementation-notes && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "implementation-notes" agent skill from https://github.com/Neeeophytee/finding-unknowns-skills/tree/main/skills/implementation-notes into .github/skills/implementation-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implementation-notes", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Neeeophytee/finding-unknowns-skills --skill implementation-notes -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Neeeophytee/finding-unknowns-skills implementation-notes --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Neeeophytee/finding-unknowns-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/implementation-notes .opencode/skills/implementation-notes && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "implementation-notes" agent skill from https://github.com/Neeeophytee/finding-unknowns-skills/tree/main/skills/implementation-notes into .opencode/skills/implementation-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implementation-notes", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
implementation-notes- GitHub stars
- 343
- Token cost
- ~474 tokens
- SKILL.md length
- 252 words
- Files
- 1
- Skills in repo
- 14
- Repo updated
- First seen
- Licence
- MIT
At a glance
Keep a running implementation-notes.md during a build, logging every deviation from the plan and every discovered edge case.
- Works in 5 steps: At the start of the build, create… → Whenever reality forces a choice the… → Log edge cases as they're found, even… → …
- Implementing against an agreed plan
- SKILL.md covers Steps and Guardrails
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Implementation Notes is an agent skill from Neeeophytee/finding-unknowns-skills. Keep a running implementation-notes.md during a build, logging every deviation from the plan and every discovered edge case. Use whenever implementing against an agreed plan or spec, especially in long autonomous sessions.
Its SKILL.md is about 470 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: 14 installable skills for Claude Code, OpenAI Codex, and Hermes: find unknowns, clarify requirements, manage context, test assumptions, and verify bug fixes with regression… The licence is MIT.
When your agent uses it
- Implementing against an agreed plan
- Especially in long autonomous sessions
Example prompts
- “/implementation-notes”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- At the start of the build, create implementation-notes.md with three headings: Deviations, Discovered edge cases, Questions for review.
- Whenever reality forces a choice the plan didn't cover
- Log edge cases as they're found, even ones handled cleanly — they are exactly the unknowns the next plan should account for.
- Anything irreversible or scope-changing goes under Questions for review AND stops the work at a safe checkpoint. Deviating conservatively…
- At the end, append a five-line summary: deviations count, the one most likely to be revisited, edge cases found, and what the next session…
What it can do on your machine
Read from SKILL.md and the folder at commit ca5696a. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Implementation Notes loads about 474 tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 252 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Neeeophytee/finding-unknowns-skills at commit ca5696a, republished under its MIT licence (© Neeeophytee). 252 words, ~474 tokens.
Download SKILL.mdSave it as
.claude/skills/implementation-notes/SKILL.md (or your agent's skills folder).- name
- implementation-notes
- description
- Keep a running implementation-notes.md during a build, logging every deviation from the plan and every discovered edge case. Use whenever implementing against an agreed plan or spec, especially in long autonomous sessions.
Implementation notes
No amount of planning removes every unknown; some only appear once the code is open. When the territory disagrees with the plan, don't stop and don't silently improvise — take the conservative option, write it down, and keep going. The notes file is how the next attempt learns from this one.
Steps
- At the start of the build, create
implementation-notes.mdwith three headings: Deviations, Discovered edge cases, Questions for review. - Whenever reality forces a choice the plan didn't cover:
- pick the conservative option (the one that's easiest to reverse),
- log it under Deviations: what the plan said, what was done instead, why, and what it would take to revisit,
- continue working. Do not block on the user for reversible decisions.
- Log edge cases as they're found, even ones handled cleanly — they are exactly the unknowns the next plan should account for.
- Anything irreversible or scope-changing goes under Questions for review AND stops the work at a safe checkpoint. Deviating conservatively is fine; deviating expensively needs a human.
- At the end, append a five-line summary: deviations count, the one most likely to be revisited, edge cases found, and what the next session should read first. Reference the file in the handoff or PR.
Guardrails
- The notes file is temporary working memory, not documentation. Keep entries to 2-3 lines each.
- Never let the notes drift from reality — an unlogged deviation is worse than no notes at all, because the file claims completeness.
- "Conservative" means reversible, not necessarily simple.
© Neeeophytee, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/implementation-notes of Neeeophytee/finding-unknowns-skills.
Open the folder on GitHubat commit ca5696a
Compare with similar skills
Implementation Notes next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Implementation Notes this skillNeeeophytee/finding-unknowns-skills | 343 | — | ~474 | Automated safety check: Pass | MIT | |
| Logging and Error Reporting for Warpwarpdotdev/warp | 65k | 1 repos | ~5.6k | Automated safety check: Pass | AGPL-3.0 | |
| Growth Logaffaan-m/ECC | 275k | 1 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Clickhouse Logs Queriessupabase/supabase | 111k | — | ~2.4k | Automated safety check: Pass | Apache-2.0 | |
| Investigating LogsPostHog/posthog | 40k | — | ~2.1k | Automated safety check: Pass | Custom licence | |
| Analyze Logsactivepieces/activepieces | 25k | 1 repos | ~1.6k | Automated safety check: Pass | MIT |
Similar skills
Growth Log
affaan-m/ECC
Write growth log entries that extract reusable patterns from completed work — root cause, transferable rule, and a recognizable signal — instead of diary-style event narration, with a 4-8 sentence…
- Official
Clickhouse Logs Queries
supabase/supabase
Write, review, and migrate Supabase logs queries against the ClickHouse-backed logs table (the logs.all.otel analytics endpoint).
- Official
Investigating Logs
PostHog/posthog
Investigate logs in a PostHog project: verify a service or deployment is healthy, explain an error spike, triage an incident, or understand what a log stream is saying.
Analyze Logs
activepieces/activepieces
Analyze application logs from the .evlog/logs/ directory. An agent skill from activepieces/activepieces.
KubeSphere WizTelemetry Logging
kubesphere/kubesphere
Installs and configures WizTelemetry Logging for KubeSphere, with container log and optional disk log collection, dependency checks and the log query API.
More from Neeeophytee/finding-unknowns-skills
All 14 skills in this repoAgent Interface Design
Neeeophytee/finding-unknowns-skills
Design tools, scripts, and CLIs that an agent will call, so the interface teaches its own use instead of a wall of prose and examples.
Assumption Test
Neeeophytee/finding-unknowns-skills
Test a consequential technical assumption with a small, falsifiable experiment before committing to an approach.
Blindspot Pass
Neeeophytee/finding-unknowns-skills
Surface the user's unknown unknowns before work starts. An agent skill from Neeeophytee/finding-unknowns-skills.
Brainstorm Prototypes
Neeeophytee/finding-unknowns-skills
Generate several genuinely different throwaway variations (designs, approaches, drafts) for the user to react to.
Change Quiz
Neeeophytee/finding-unknowns-skills
After a working session, produce a report on what changed plus a quiz the user must pass before merging.
Context Audit
Neeeophytee/finding-unknowns-skills
Audit the instructions an agent already carries — CLAUDE.md, AGENTS.md, skills, tool descriptions — for contradictions, over-constraint, and duplication, then propose a cut list.
Questions about Implementation Notes
What does Implementation Notes do?
Keep a running implementation-notes.md during a build, logging every deviation from the plan and every discovered edge case. Implementation Notes is an agent skill from Neeeophytee/finding-unknowns-skills.md during a build, logging every deviation from the plan and every discovered edge case.
When should I use Implementation Notes?
Implementation Notes fits situations like: implementing against an agreed plan; especially in long autonomous sessions.
How do I install Implementation Notes in Claude Code?
Run `npx skills add Neeeophytee/finding-unknowns-skills --skill implementation-notes -a claude-code`. Or copy the skill folder (skills/implementation-notes in Neeeophytee/finding-unknowns-skills) into .claude/skills/implementation-notes in your project. Claude Code loads it when a task matches its description.
How do I install Implementation Notes in Codex?
Run `npx skills add Neeeophytee/finding-unknowns-skills --skill implementation-notes -a codex`. Or copy the skill folder (skills/implementation-notes in Neeeophytee/finding-unknowns-skills) into .agents/skills/implementation-notes in your project. Codex loads it when a task matches its description.
Can I use Implementation Notes in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Neeeophytee/finding-unknowns-skills --skill implementation-notes -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/implementation-notes, .gemini/skills/implementation-notes, .github/skills/implementation-notes and .opencode/skills/implementation-notes in your project.
What does Implementation Notes need to run?
SKILL.md names no scripts, command-line tools or credentials: Implementation Notes is instructions for the agent only.
Does Implementation Notes access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Implementation Notes safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Implementation Notes use?
Implementation Notes is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Implementation Notes use?
About 474 tokens (SKILL.md is roughly 1.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Implementation Notes?
Skills that share tags, products or a category with Implementation Notes: Logging and Error Reporting for Warp (warpdotdev/warp, 65k stars), Growth Log (affaan-m/ECC, 275k stars), Clickhouse Logs Queries (supabase/supabase, 111k stars) and Investigating Logs (PostHog/posthog, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Implementation Notes?
Neeeophytee (a GitHub user) maintains it in Neeeophytee/finding-unknowns-skills, which has 343 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on September 28, 2026.
Source: Neeeophytee/finding-unknowns-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.