AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

repo-standardizer

Polish any GitHub repository's surface — labels (emoji rating tiers, P0–P3 priority, impact severity), issue forms, PR template, CI workflows, CODEOWNERS, rulesets, docs. Repo meta & config only — no code logic touched. Use when creating a new repo or polishing an existing one.

Original source
github
License
MIT
Pinned revision
5269f7ea2d6c3a9bfda5ed878b6726cf509121fd

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read github--repo-standardizer at revision 5269f7ea2d6c3a9bfda5ed878b6726cf509121fd, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 12

templates/CONTRIBUTING.md

Contributing

Thanks for your interest in contributing! Please take a moment to read this guide so your contribution goes smoothly.

Getting started

  1. Fork the repository.
  2. Create a feature branch: git checkout -b feat/your-feature.
  3. Make your changes and commit them with a clear message.
  4. Push and open a pull request against the default branch (main for most repos).

Pull request checklist

  • [ ] The PR description explains what and why.
  • [ ] Tests pass locally (npm test / pytest / go test ...).
  • [ ] New behavior is covered by tests.
  • [ ] Documentation is updated if user-facing behavior changed.

Issue conventions

  • Use the issue forms: bug reports, feature requests, questions.
  • Label your issue with the matching bug / enhancement / P0–P3 label.

Commit style

Use conventional commits with a scope: type(scope): description

feat(labels): add tier labels
fix(ci): correct release workflow

Common types: feat fix docs chore refactor test ci perf. Scope = the area you touched (module, file, subsystem).

Examples:

feat(labels): add tier labels
fix(ci): correct release workflow
fix(docx): update README.md
docs(readme): explain installation
chore(ci): bump action version

Code style

Match the existing style of the project (linter configs are included). When in doubt, run the linter before pushing.

Questions?

Open a discussion or ask in a question issue. We're friendly!