ayrisdev/app-store-optimization
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore: remove MAINTENANCE.md, walkthrough.md and .agent/rules

Browse Source
This commit is contained in:
sck_0
2026-01-16 18:12:49 +01:00
parent d8b9ac19b2
commit 59a349075e
3 changed files with 0 additions and 121 deletions
Download Patch File Download Diff File Expand all files Collapse all files

57
MAINTENANCE.md
View File

@@ -1,57 +0,0 @@
# Repository Maintenance Protocol
To ensure consistency and quality, the following steps MUST be performed for **every single change** involving skills or documentation.
## 1. Skill Creation & Modification
- [ ] **Check Duplicates**: Before adding a skill, check `skills_index.json` or `ls skills/` to ensure it doesn't exist.
- [ ] **Folder Structure**: Each skill must have its own folder in `skills/<skill-name>`.
- [ ] **SKILL.md**: Every skill directory MUST contain a `SKILL.md` file with valid frontmatter:
```markdown
---
name: Skill Name
description: Brief description.
---
```
## 2. Validation & Indexing (CRITICAL)
Running the scripts is **MANDATORY** after any change to `skills/`.
- [ ] **Validate Skills**: Run the validation script to check for formatting errors.
```bash
python3 scripts/validate_skills.py
```
- [ ] **Generate Index**: Update `skills_index.json`. This is the source of truth for the agent.
```bash
python3 scripts/generate_index.py
```
## 3. Documentation Updates
The `README.md` does not auto-update. You must manually sync it with the index.
- [ ] **About / Introduction**: Update the total count in the opening paragraph and blockquote.
- `> **The Ultimate Collection of [X]+ Agentic Skills...`
- `...library of **[X] high-performance skills**...`
- [ ] **Features & Categories Table**: If the new skill fits a category, update the table in `# Features & Categories`.
- [ ] **Full Skill Registry Table**: Add the new skill to the main table.
- Format: `| **[Name]** | [Description] | [Path] |`
- Verify alphabetical order.
- [ ] **Credits & Sources**: If the skill was imported from a community repo, add a credit link in `# Credits & Sources`.
- Example: `- **[repo-name](url)**: Source for [skill-name].`
## 4. Git Operations
- [ ] **Check Status**: `git status` to see what changed.
- [ ] **Add All Files**: Ensure new skill folders are added (`git add skills/`).
- [ ] **Commit**: Use a descriptive Conventional Commit message (e.g., `feat: add new security skills`, `docs: update readme count`).
- [ ] **Push**: `git push` to origin. **NEVER FORGET THIS.**
## 5. Agent Artifacts (Internal)
- [ ] **Walkthrough**: Update `walkthrough.md` in the brain/artifact directory to reflect the session's achievements.