Proposal: Portable C++ Core Guidelines Agent Skill with rule-linked evaluations
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 35/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- cpp, github
- Área
- ai, documentation
Línea de trabajo
Start with the repository’s existing tool support and automatic processing, then review the C++ Core Guidelines source and the Agent Skills specification linked in the issue. The proposal needs a decision on whether the package belongs here or in a companion project, plus scope and maintenance expectations. Done would include an agreed pilot covering 10–20 rules and a plan for rule-linked evaluations, synchronization, and reporting.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Would the project be open to a portable Agent Skills package derived from the C++ Core Guidelines, accompanied by a vendor-neutral evaluation suite?
The goal would be to help coding agents apply and cite relevant guidelines during implementation and review across compatible development tools. This seems aligned with the project's existing emphasis on tool support and automatic processing.
Proposed approach
- Keep the existing guidelines as the authoritative source. Generate indexed reference material preserving rule IDs, explanations, exceptions, links, and license attribution, and record the source commit.
- Provide a concise
SKILL.mdthat guides an agent to inspect the project's C++ version and constraints, load relevant rules on demand, explain findings with rule references, and validate changes using available compiler checks, tests, and static analysis. - Document client compatibility and tool prerequisites. Reuse existing checks, including applicable
clang-tidychecks. - Distinguish reference coverage from evaluated coverage: making the whole document accessible would not imply that every rule can be automatically enforced or has been validated.
Shared evaluations
Publish evaluation cases and expected outcomes independently of any particular model or agent runner. Cases should cover:
- Genuine violations and correct rule attribution.
- Compliant code that should not be flagged or changed.
- Documented exceptions and project-specific constraints.
- Fixes that compile, pass relevant tests, and preserve intended behavior.
- Situations where additional context is needed before making a recommendation.
For example, ownership tests should distinguish a raw owning pointer from a legitimate non-owning raw pointer, rather than rewarding blanket replacement with smart pointers.
Compare the same agent with and without the skill, record model/tool versions, and report results per rule, including missed violations, false positives, and incorrect edits. Use held-out cases beyond the examples embedded in the guidelines, with compiler/test checks and human-reviewed expectations where applicable.
Initial scope and maintenance
A first pilot could evaluate 10–20 rules around resource management, ownership, and lifetime. Broader evaluation coverage could grow incrementally based on evidence and review.
Would this be appropriate for this repository, or better maintained as a linked companion project? Feedback on pilot scope, synchronization with upstream changes, and maintenance expectations would help establish a manageable contribution path.
- Lenguaje dominante
- CSS
- Estrellas
- 45.5k
- Forks
- 5.6k
- Merge medio
- 6 min
- PR fusionados (30 d)
- 1
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de isocpp/CppCoreGuidelines
-
Dificultad 1/5 1-3 horas Aptitud para principiantes 78/100
isocpp/CppCoreGuidelines#2345 ·
-
NL.16 is ambiguousAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
isocpp/CppCoreGuidelines#2344 · 3 comentarios ·
-
Use short #s-xxx as ref, not long like #sl-the-standard-library or #gsl-guidelines-support-libraryAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 64/100
isocpp/CppCoreGuidelines#2340 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
isocpp/CppCoreGuidelines#2205 · 8 comentarios ·
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 64/100
isocpp/CppCoreGuidelines#1649 · 3 comentarios ·
Todos los issues de isocpp/CppCoreGuidelines
Issues similares
-
agent good first issue
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
Viox-Development/Artificial-Logic-and-Intelligence-Computation-Engine#251 ·
Los mantenedores suelen responder en 1 día
-
Tier-3 full-echo merge: trailing prose on the ADDS_NEW_CLAIM line silently drops the observationAbiertobug building moscow:should
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Kromatic-Innovation/athenaeum#2739 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
feat: AgentOS option to drop past tool calls and results from the provider contextPosiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abiertoagentos enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
Los mantenedores suelen responder en 1 día
-
integration:hermes
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
vectorize-io/hindsight#6601 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
AnsahMohammad/shots-studio#211 ·