-
Notifications
You must be signed in to change notification settings - Fork 10
Simplify project configuration and documentation #29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Remove excessive .gitignore entries and streamline CONTRIBUTING.md from 265 to 22 lines, keeping only essential project setup guidance.
Reviewer's GuideThis PR slims down the repository into a pure Markdown-based prompt library by removing legacy tooling, CI, and extensive docs, and replaces them with concise configuration and contribution guidelines. File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
📝 WalkthroughSummary by CodeRabbit
WalkthroughMass removal of CI/workflow configs, validators, safety tooling, tests, and extensive documentation; package metadata simplified and version/license updated; added a single lightweight agent template doc at Changes
Sequence Diagram(s)(omitted — changes are largely removals and documentation edits; no new control-flow to diagram) Estimated code review effort🎯 4 (Complex) | ⏱️ ~45 minutes Possibly related PRs
Suggested reviewers
Poem
Pre-merge checks and finishing touches❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✨ Finishing touches🧪 Generate unit tests
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This pull request dramatically simplifies the ccprompts project configuration and documentation by removing extensive testing infrastructure, validation systems, and documentation files. The changes reduce project complexity while maintaining the core functionality.
- Removed comprehensive testing framework including Jest test suites and validation systems
- Eliminated safety validation infrastructure using Dagger containers
- Simplified package.json by removing scripts, dependencies, and development tooling
Reviewed Changes
Copilot reviewed 71 out of 160 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| tests/validation.test.js | Removed comprehensive validation system tests |
| tests/structure-validator.test.js | Removed structure validation test suite |
| tests/setup.js | Removed Jest test configuration and utilities |
| tests/security-validator.test.js | Removed security validation test framework |
| tests/safety-validation.test.js | Removed Dagger safety validation tests |
| tests/quality-scorer.test.js | Removed quality scoring system tests |
| tests/performance-compatibility.test.js | Removed performance and compatibility tests |
| tests/modular-validators.test.js | Removed modular validator component tests |
| tests/main-validator.test.js | Removed main validator orchestration tests |
| tests/jest-teardown.js | Removed Jest global teardown configuration |
| tests/jest-env-setup.js | Removed Jest environment setup |
| tests/integration.test.js | Removed integration test suite |
| tests/file-utils.test.js | Removed file utilities test suite |
| tests/command-structure.test.js | Removed command structure validation tests |
| templates/SUBAGENT_TEMPLATE.md | Removed subagent template file |
| scripts/validators/structure-validator.js | Removed structure validation module |
| scripts/validators/security-validator.js | Removed security validation module |
| scripts/validators/quality-scorer.js | Removed quality scoring module |
| scripts/validators/main-validator.js | Removed main validator orchestrator |
| scripts/validators/index.js | Removed validators module index |
| scripts/validators/file-utils.js | Removed file utilities module |
| scripts/validation-config.json | Removed validation configuration |
| scripts/validate-commands.js | Removed command validation script |
| scripts/safety-validator.js | Removed Dagger safety validation system |
| scripts/safe-run.sh | Removed safe command execution wrapper |
| scripts/quick-safe.sh | Removed quick safety wrapper script |
| scripts/config/safety-patterns.js | Removed safety pattern configuration |
| package.json | Simplified to basic project metadata only |
| docs/WORKFLOW-GUIDE.md | Removed comprehensive workflow documentation |
| docs/USAGE-EXAMPLES.md | Removed usage examples and tutorials |
| docs/README.md | Removed documentation overview and navigation |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey there - I've reviewed your changes - here's some feedback:
- The agent-template-wizard instructions still refer to the now-removed .claude directory—please update those paths to match the new agents/ structure.
- Since this PR removes all CI and automation, consider adding a minimal manual QA or linting guideline to help maintain prompt structure and quality over time.
- You bumped package.json to version 1.0.0—consider adding a brief release/versioning section in the README so contributors know how to tag and track future updates.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- The agent-template-wizard instructions still refer to the now-removed .claude directory—please update those paths to match the new agents/ structure.
- Since this PR removes all CI and automation, consider adding a minimal manual QA or linting guideline to help maintain prompt structure and quality over time.
- You bumped package.json to version 1.0.0—consider adding a brief release/versioning section in the README so contributors know how to tag and track future updates.Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 5
📜 Review details
Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro
⛔ Files ignored due to path filters (2)
bun.lockis excluded by!**/*.lockdocs/assets/banner.svgis excluded by!**/*.svg
📒 Files selected for processing (73)
.bun-version(0 hunks).claude/README.md(0 hunks).claude/agents/agent-template-wizard.md(0 hunks).claude/settings.json(0 hunks).editorconfig(0 hunks).github/BRANCH_PROTECTION.md(0 hunks).github/CODEOWNERS(0 hunks).github/ISSUE_TEMPLATE/bug_report.yml(0 hunks).github/ISSUE_TEMPLATE/command_proposal.yml(0 hunks).github/ISSUE_TEMPLATE/feature_request.yml(0 hunks).github/actions/setup-node-env/action.yml(0 hunks).github/markdown-link-check.json(0 hunks).github/pull_request_template.md(0 hunks).github/test-harness/test-workflows.sh(0 hunks).github/workflow-config.yml(0 hunks).github/workflows/ci.yml(0 hunks).github/workflows/claude-code-review.yml(0 hunks).github/workflows/claude.yml(0 hunks).github/workflows/reusable/README.md(0 hunks).github/workflows/reusable/artifact-handling.yml(0 hunks).github/workflows/reusable/security-scan.yml(0 hunks).github/workflows/reusable/setup-node.yml(0 hunks).github/workflows/reusable/validate-prompts.yml(0 hunks).github/workflows/security-scan.yml(0 hunks).gitignore(1 hunks).markdownlint.json(0 hunks).pre-commit-config.yaml(0 hunks).yamllint.yml(0 hunks)AGENTS.md(0 hunks)CHANGELOG.md(0 hunks)CLAUDE.md(0 hunks)CONTRIBUTING.md(1 hunks)README.md(1 hunks)SAFETY.md(0 hunks)agents/agent-template-wizard.md(1 hunks)dagger.json(0 hunks)docs/API-REFERENCE.md(0 hunks)docs/CC-SDK.md(0 hunks)docs/CI-CD-ROLLBACK-PLAN.md(0 hunks)docs/COMMAND-REFERENCE.md(0 hunks)docs/DEVELOPER-GUIDE.md(0 hunks)docs/README.md(0 hunks)docs/USAGE-EXAMPLES.md(0 hunks)docs/WORKFLOW-GUIDE.md(0 hunks)jest.config.js(0 hunks)package.json(1 hunks)scripts/config/safety-patterns.js(0 hunks)scripts/quick-safe.sh(0 hunks)scripts/safe-run.sh(0 hunks)scripts/safety-validator.js(0 hunks)scripts/validate-commands.js(0 hunks)scripts/validation-config.json(0 hunks)scripts/validators/file-utils.js(0 hunks)scripts/validators/index.js(0 hunks)scripts/validators/main-validator.js(0 hunks)scripts/validators/quality-scorer.js(0 hunks)scripts/validators/security-validator.js(0 hunks)scripts/validators/structure-validator.js(0 hunks)templates/SUBAGENT_TEMPLATE.md(0 hunks)tests/command-structure.test.js(0 hunks)tests/file-utils.test.js(0 hunks)tests/integration.test.js(0 hunks)tests/jest-env-setup.js(0 hunks)tests/jest-teardown.js(0 hunks)tests/main-validator.test.js(0 hunks)tests/modular-validators.test.js(0 hunks)tests/performance-compatibility.test.js(0 hunks)tests/quality-scorer.test.js(0 hunks)tests/safety-validation.test.js(0 hunks)tests/security-validator.test.js(0 hunks)tests/setup.js(0 hunks)tests/structure-validator.test.js(0 hunks)tests/validation.test.js(0 hunks)
💤 Files with no reviewable changes (68)
- .github/workflows/security-scan.yml
- scripts/validators/structure-validator.js
- docs/API-REFERENCE.md
- .markdownlint.json
- .github/ISSUE_TEMPLATE/feature_request.yml
- .github/workflows/reusable/README.md
- docs/DEVELOPER-GUIDE.md
- tests/setup.js
- .github/BRANCH_PROTECTION.md
- .github/ISSUE_TEMPLATE/bug_report.yml
- .claude/agents/agent-template-wizard.md
- docs/CC-SDK.md
- tests/validation.test.js
- .github/workflows/ci.yml
- tests/jest-env-setup.js
- .github/markdown-link-check.json
- scripts/safe-run.sh
- .claude/settings.json
- tests/security-validator.test.js
- docs/USAGE-EXAMPLES.md
- tests/main-validator.test.js
- scripts/validators/quality-scorer.js
- .editorconfig
- jest.config.js
- .github/workflow-config.yml
- docs/COMMAND-REFERENCE.md
- templates/SUBAGENT_TEMPLATE.md
- .github/workflows/reusable/security-scan.yml
- scripts/config/safety-patterns.js
- tests/safety-validation.test.js
- scripts/validators/index.js
- SAFETY.md
- scripts/validators/file-utils.js
- tests/quality-scorer.test.js
- .github/CODEOWNERS
- dagger.json
- tests/file-utils.test.js
- docs/README.md
- .claude/README.md
- CLAUDE.md
- scripts/quick-safe.sh
- docs/CI-CD-ROLLBACK-PLAN.md
- docs/WORKFLOW-GUIDE.md
- tests/performance-compatibility.test.js
- tests/structure-validator.test.js
- .github/workflows/claude.yml
- .github/pull_request_template.md
- AGENTS.md
- CHANGELOG.md
- scripts/validators/main-validator.js
- tests/jest-teardown.js
- .github/workflows/reusable/artifact-handling.yml
- .github/workflows/claude-code-review.yml
- .yamllint.yml
- tests/modular-validators.test.js
- .github/ISSUE_TEMPLATE/command_proposal.yml
- scripts/validate-commands.js
- .github/test-harness/test-workflows.sh
- scripts/safety-validator.js
- .pre-commit-config.yaml
- tests/integration.test.js
- .bun-version
- tests/command-structure.test.js
- scripts/validators/security-validator.js
- .github/workflows/reusable/validate-prompts.yml
- scripts/validation-config.json
- .github/actions/setup-node-env/action.yml
- .github/workflows/reusable/setup-node.yml
🧰 Additional context used
📓 Path-based instructions (2)
package.json
📄 CodeRabbit inference engine (AGENTS.md)
Pin Bun via package.json "packageManager": "[email protected]"
package.json: Set engines.node to >= 18.0.0
Pin Dagger dependency to ^18.12
Use TypeScript ^5.0.0
Use Jest ^29.7.0 (note: known issues on Node 24+)
Files:
package.json
**/*.md
📄 CodeRabbit inference engine (AGENTS.md)
**/*.md: Limit Markdown line length to 120 characters
Use consistent heading levels in Markdown
Use proper language tags on Markdown code blocks
**/*.md: Run markdownlint on all documentation markdown files
Validate all Markdown links with markdown-link-check
Files:
README.mdagents/agent-template-wizard.mdCONTRIBUTING.md
🧠 Learnings (3)
📚 Learning: 2025-09-10T04:12:35.254Z
Learnt from: CR
PR: ursisterbtw/ccprompts#0
File: CLAUDE.md:0-0
Timestamp: 2025-09-10T04:12:35.254Z
Learning: Applies to .claude/commands/@(00-initial-workflow|01-project-setup|02-development|03-security|04-testing|05-deployment|06-collaboration|07-utilities|08-extras|09-agentic-capabilities|10-ai-native-development|11-enterprise-scale)/**/*.md : Organize command files within the 12 specified phase directories under .claude/commands
Applied to files:
README.md
📚 Learning: 2025-09-10T04:12:35.254Z
Learnt from: CR
PR: ursisterbtw/ccprompts#0
File: CLAUDE.md:0-0
Timestamp: 2025-09-10T04:12:35.254Z
Learning: Applies to .claude/commands/**/*.md : All command docs must follow the standard structure: usage examples with /command-name, comprehensive descriptions with auto-detection, safety measures and verification steps, and educational components
Applied to files:
README.mdCONTRIBUTING.md
📚 Learning: 2025-09-10T04:12:35.254Z
Learnt from: CR
PR: ursisterbtw/ccprompts#0
File: CLAUDE.md:0-0
Timestamp: 2025-09-10T04:12:35.254Z
Learning: Applies to templates/SUBAGENT_TEMPLATE.md : Create new agents using templates/SUBAGENT_TEMPLATE.md with wizard-filled placeholders and the 7-step methodology
Applied to files:
agents/agent-template-wizard.md
🪛 markdownlint-cli2 (0.18.1)
README.md
5-5: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
10-10: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
15-15: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
20-20: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
21-21: Files should end with a single newline character
(MD047, single-trailing-newline)
agents/agent-template-wizard.md
9-9: First line in a file should be a top-level heading
(MD041, first-line-heading, first-line-h1)
11-11: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
16-16: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
17-17: Fenced code blocks should be surrounded by blank lines
(MD031, blanks-around-fences)
52-52: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
60-60: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
65-65: Files should end with a single newline character
(MD047, single-trailing-newline)
CONTRIBUTING.md
5-5: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
11-11: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
17-17: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
22-22: Files should end with a single newline character
(MD047, single-trailing-newline)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: Sourcery review
- Add Python bytecode patterns to .gitignore (*.py[cod], *$py.class) - Add whitespace after section headers for better readability - Simplify agent template wizard by removing verbose workflow sections - Fix missing newlines in various files
Add Manual QA and Release/versioning sections to README with quality assurance steps and semantic versioning workflow. Update agent template wizard to use local ./agents/ instead of ./.claude/agents/ directory.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 4
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
agents/agent-template-wizard.md (1)
21-43: Close the base-template code fenceThe template’s fenced block is never closed, so the rest of the document renders inside it and markdownlint flags MD040/MD031. Add the terminating fence after the “Example invocation” heading.
Based on coding guidelines
## Example invocation +~~~
📜 Review details
Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro
📒 Files selected for processing (2)
README.md(1 hunks)agents/agent-template-wizard.md(1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
**/*.md
📄 CodeRabbit inference engine (AGENTS.md)
**/*.md: Limit Markdown line length to 120 characters
Use consistent heading levels in Markdown
Use proper language tags on Markdown code blocks
**/*.md: Run markdownlint on all documentation markdown files
Validate all Markdown links with markdown-link-check
Files:
README.mdagents/agent-template-wizard.md
🧠 Learnings (3)
📚 Learning: 2025-09-10T04:12:35.254Z
Learnt from: CR
PR: ursisterbtw/ccprompts#0
File: CLAUDE.md:0-0
Timestamp: 2025-09-10T04:12:35.254Z
Learning: Applies to .claude/commands/**/*.md : All command docs must follow the standard structure: usage examples with /command-name, comprehensive descriptions with auto-detection, safety measures and verification steps, and educational components
Applied to files:
README.md
📚 Learning: 2025-09-10T04:12:35.254Z
Learnt from: CR
PR: ursisterbtw/ccprompts#0
File: CLAUDE.md:0-0
Timestamp: 2025-09-10T04:12:35.254Z
Learning: Applies to .claude/commands/@(00-initial-workflow|01-project-setup|02-development|03-security|04-testing|05-deployment|06-collaboration|07-utilities|08-extras|09-agentic-capabilities|10-ai-native-development|11-enterprise-scale)/**/*.md : Organize command files within the 12 specified phase directories under .claude/commands
Applied to files:
README.md
📚 Learning: 2025-09-10T04:12:35.254Z
Learnt from: CR
PR: ursisterbtw/ccprompts#0
File: CLAUDE.md:0-0
Timestamp: 2025-09-10T04:12:35.254Z
Learning: Applies to templates/SUBAGENT_TEMPLATE.md : Create new agents using templates/SUBAGENT_TEMPLATE.md with wizard-filled placeholders and the 7-step methodology
Applied to files:
agents/agent-template-wizard.md
| @@ -0,0 +1,42 @@ | |||
| --- | |||
| name: agent-template-wizard | |||
| description: Drafts new Claude Code agents from the lean template included in this repository. Feed it a domain and it will deliver a ready-to-save Markdown file. | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🛠️ Refactor suggestion | 🟠 Major
Wrap the description to respect the 120-character limit
Line 3 blows past the 120-character ceiling defined in our Markdown guidelines. Break the description into a folded multi-line block so each rendered line stays within spec.
Based on coding guidelines
-description: Drafts new Claude Code agents from the lean template included in this repository. Feed it a domain and it will deliver a ready-to-save Markdown file.
+description: >
+ Drafts new Claude Code agents from the lean template included in this repository.
+ Feed it a domain and it will deliver a ready-to-save Markdown file.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| description: Drafts new Claude Code agents from the lean template included in this repository. Feed it a domain and it will deliver a ready-to-save Markdown file. | |
| description: > | |
| Drafts new Claude Code agents from the lean template included in this repository. | |
| Feed it a domain and it will deliver a ready-to-save Markdown file. |
🤖 Prompt for AI Agents
In agents/agent-template-wizard.md around line 3, the single-line description
exceeds the 120-character limit; replace it with a folded multi-line YAML block
(use the > indicator) and break the sentence into lines each no longer than 120
characters so the rendered description remains within the Markdown guidelines.
| # ccprompts | ||
|
|
||
| <div align="center"> | ||
| A trimmed-down Claude Code prompt library. Everything lives in plain Markdown so you can copy, remix, or drop commands straight into Claude without tooling overhead. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wrap long introductory sentence to meet 120-char limit
Line 3 exceeds the 120-character limit specified for Markdown files. Please wrap the copy so each line stays within the guideline. As per coding guidelines
Apply this diff to stay within the limit:
-A trimmed-down Claude Code prompt library. Everything lives in plain Markdown so you can copy, remix, or drop commands straight into Claude without tooling overhead.
+A trimmed-down Claude Code prompt library.
+Everything lives in plain Markdown so you can copy, remix, or drop commands straight into Claude without tooling overhead.Committable suggestion skipped: line range outside the PR's diff.
🤖 Prompt for AI Agents
In README.md around line 3, the introductory sentence exceeds the 120-character
Markdown line-length guideline; wrap the sentence into multiple lines under 120
characters each (preserve wording and punctuation) so the paragraph is
line-wrapped to stay within the limit while keeping the same content and
readability.
|
|
||
| **macOS:** | ||
| - Bump `package.json` when you make a noteworthy library change; use semantic versioning (patch for minor edits, minor for additions, major when structure changes). | ||
| - Tag the commit with the matching version (e.g., `git tag v1.0.1 && git push --tags`) so downstream consumers can pin to a release. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Break long bullet to satisfy Markdown line-length rule
This bullet line currently exceeds 120 characters. Please wrap it while preserving list formatting. As per coding guidelines
Apply this diff to keep the line within the limit:
-- Tag the commit with the matching version (e.g., `git tag v1.0.1 && git push --tags`) so downstream consumers can pin to a release.
+- Tag the commit with the matching version (e.g., `git tag v1.0.1 && git push --tags`)
+ so downstream consumers can pin to a release.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| - Tag the commit with the matching version (e.g., `git tag v1.0.1 && git push --tags`) so downstream consumers can pin to a release. | |
| - Tag the commit with the matching version (e.g., `git tag v1.0.1 && git push --tags`) | |
| so downstream consumers can pin to a release. |
🤖 Prompt for AI Agents
In README.md around line 33 the bullet exceeds 120 characters; break the long
bullet into two wrapped lines preserving the list formatting and Markdown syntax
(keep the leading dash/space and any backticks). Split the sentence at a logical
boundary (for example after the command) so it reads across two lines under the
same list item, ensuring no additional list markers or punctuation changes are
introduced and line lengths are under 120 characters.
| MIT. See [LICENSE](LICENSE) for details. | ||
|
|
||
| --- | ||
| The previous setup relied on custom validators, Dagger containers, and 70-command count checks. That overhead made maintenance harder than adding new prompts. The library is now intentionally simple: no build step, no dependencies, just Markdown you can read, edit, and share. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wrap concluding paragraph to obey 120-char markdown guideline
The closing paragraph is also over the 120-character limit. Please wrap it into shorter lines. As per coding guidelines
Apply this diff to respect the limit:
-The previous setup relied on custom validators, Dagger containers, and 70-command count checks. That overhead made maintenance harder than adding new prompts. The library is now intentionally simple: no build step, no dependencies, just Markdown you can read, edit, and share.
+The previous setup relied on custom validators, Dagger containers, and 70-command count checks.
+That overhead made maintenance harder than adding new prompts.
+The library is now intentionally simple: no build step, no dependencies, just Markdown you can read, edit, and share.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| The previous setup relied on custom validators, Dagger containers, and 70-command count checks. That overhead made maintenance harder than adding new prompts. The library is now intentionally simple: no build step, no dependencies, just Markdown you can read, edit, and share. | |
| The previous setup relied on custom validators, Dagger containers, and 70-command count checks. | |
| That overhead made maintenance harder than adding new prompts. | |
| The library is now intentionally simple: no build step, no dependencies, just Markdown you can read, edit, and share. |
🤖 Prompt for AI Agents
In README.md around line 38, the closing paragraph exceeds the
120-character-per-line Markdown guideline; reflow it so each line is <=120
chars. Edit the paragraph by inserting line breaks at sensible word boundaries
(preferably after clauses or commas) to produce multiple lines under the
120-char limit while preserving original wording and sentence structure.
Streamline project setup guidance by reducing the size of the documentation and configuration files, removing unnecessary entries and files to enhance clarity and maintainability.
Summary by Sourcery
Streamline the repository by dropping all custom tooling, tests, and CI, and refocusing on a simple Markdown prompt library; update documentation and configuration to reflect the new lightweight approach
New Features:
Enhancements:
CI:
Documentation:
Tests:
Chores: