Submission: verify-before-stop hook + 5 Apify Actors
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 38/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- bash
- Domain
- content, documentation
Research direction
Start by checking the repository README's Tools & Utilities and Infrastructure sections and compare the proposed hook and five Apify Actors with the list's contribution format and inclusion criteria. The issue names no files or tests; if accepted, add formatted entries for the resources that fit. Done means the README entries are accurate and placed in the appropriate sections.
Written by the indexing model from the issue text.
Description
Submission: verify-before-stop + 5 Apify Actors for Claude Code reliability
Author: @ianymu
Open-source hook (MIT)
- verify-before-stop — https://github.com/ianymu/claude-verify-before-stop
A Stop-event hook (~30 lines bash) that fails the session unless the agent wrote a VERIFIED|<unix-ts> marker during the run. Catches Claude Code claiming "done" without running tests/curl/migrations.
5 Apify Actors (cloud, free tier, callable over HTTP)
- llms.txt Converter — https://apify.com/ianymu/llms-txt-converter
- CLAUDE.md Security Auditor — https://apify.com/ianymu/claudemd-security-auditor
- GitHub Issue → Claude Prompts — https://apify.com/ianymu/gh-issue-to-claude-prompts
- MCP Server Catalog — https://apify.com/ianymu/mcp-server-catalog
- CLAUDE.md Generator — https://apify.com/ianymu/claudemd-generator
Best fits for the README's Tools & Utilities + Infrastructure sections. Happy to convert to a PR with formatted markdown entries on request.
- Dominant language
- No language data
- Stars
- 530
- Forks
- 651
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from jqueryscript/awesome-claude-code
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
Difficulty 1/5 Under an hour Newbie friendliness 74/100
All issues in jqueryscript/awesome-claude-code
Similar issues
-
SwarmailOpenresource-submission validation-passed
Difficulty 1/5 Under an hour Newbie friendliness 65/100
hesreallyhim/awesome-claude-code#3350 · 1 comment ·
Maintainers usually reply within 1 day
-
www.fcportables.comOpenN: AdGuard Browser Extension P3: Medium T: Anti Adblock Script T: Incorrect Blocking
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
AdguardTeam/AdguardFilters#245742 · 2 comments ·
Maintainers usually reply within 1 day
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 78/100
lingdojo/kana-dojo#33337 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
BSData/age-of-sigmar-4th#1414 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
nodejs/nodejs.org#9248 ·
Maintainers usually reply within 2 days